Fukuoka SoftBank defeated Yokohama DeNA 2–1 in ten innings in Game 3 of the 2026 Japan Series. For someone opening a Japanese scoreboard for the first time, however, the final numbers are only the beginning. Inning columns, team totals, pitching decisions and a small “x” can make a compact page look more complicated than the game summary suggests.
This guide starts with the official result and then offers an original, practical method for reading a line score. It does not claim attendance at the game or analysis of a complete replay. Research was completed on 27 October UTC, already 28 October in Japan and Bangladesh. Fictional exercises are identified separately from the confirmed match information.
What the official records confirm
The [NPB Game 3 record](https://npb.jp/scores/2026/1027/h-db-03/) identifies the 27 October meeting at Mizuho PayPay Dome as a completed game. DeNA scored in the fifth inning; SoftBank answered in the ninth and won in the tenth. The official totals are seven hits for DeNA and ten for SoftBank, with no errors recorded for either side. Tomoya Masaki's tenth-inning solo home run supplied the winning run. Kazuki Sugiyama received the pitching win and J. Ruiz the loss.
The [SoftBank scoreboard](https://www.softbankhawks.co.jp/gamelive/result/2026102701/) independently presents the same final result and finishing home run. The [DeNA result page](https://sp.baystars.co.jp/game/result/) also displays the completed game and matching inning totals at the time checked. The latter is a changing results page, so readers visiting later should confirm the date before comparing it with this article.
On the [NPB series overview](https://npb.jp/nippons/2026/), SoftBank led three games to none after this result. Game 4 was listed for 28 October at 18:00 in Fukuoka. That was a scheduled fixture when researched, not a result or a declaration that the series had ended. Later games listed on a schedule should always be checked against the series' actual progress.
Start with the teams, date and completion status
Before interpreting statistics, establish which game the page describes. A club may publish a live feed, a schedule, a completed box score and a preview at different addresses. Search results can retain an earlier “before the game” description even after another page carries the final outcome. The page itself is therefore more useful than an isolated search snippet.
Read the opponent names and fixture date together. If the same clubs meet on consecutive days, a correct score from the wrong day is still the wrong answer. The venue adds another useful check. This is particularly important in a series, where readers can otherwise mistake a preview of the next game for the report of the previous one.
Look for an explicit completed-game label before calling a number final. A live score may be accurate at the instant it appears and change moments later. Save a note of the retrieval time if you are comparing records. That small habit helps explain why two screenshots can differ without either one necessarily being fabricated or careless.
Read across an inning row before reading down the totals
A line score arranges a team's runs by inning. Work from the first inning towards the last, keeping your place in the same row. Then compare the sum with the team's run total at the right. This gives you a compact picture of when scoring occurred, even when you cannot yet read every player's name.
Here is an invented example: the visitors' first five entries are zero, two, zero, one and zero. Their running total after five innings is three. If the home team's corresponding entries are one, zero, zero, zero and one, its total is two. The visitors lead by one at that point. These numbers are a teaching exercise, not additional events from the Japan Series game.
Now add a sixth inning in which the visitors score zero and the home side scores two. The home side moves ahead, four to three. Notice that the final sixth-inning entries alone do not tell the whole story; the earlier runs still count. Reading a row as a running total prevents a late scoring burst from being confused with the entire game score.
Runs, hits and errors answer different questions
The run column determines the score. The hit column records a different category, so it should not be added to the run total. Errors are another distinct entry. A newcomer who sees three numbers together can easily mistake them for separate sets or periods, particularly when moving from another sport's scoreboard conventions.
[MLB's run glossary](https://www.mlb.com/glossary/standard-stats/run) defines a run through a player scoring at home, regardless of how that player originally reached base. That short definition is background terminology, not a substitute for NPB's competition rules. It explains why getting on base and completing a scoring journey are separate events.
In a fictional practice sheet, Team A has eight hits and two runs while Team B has six hits and three runs. Team B wins on runs. The totals alone do not explain how the scoring opportunities developed or disappeared. To answer that question, examine the sequence of plate appearances and baserunners rather than inventing a conversion percentage from incomplete information.
Treat the finishing mark as context, not another run
An “x” beside a home team's final inning entry is a signal to pay attention to how the game finished. In this match, the official record pairs the final home entry with the winning home run. Do not read “1x” as a multiplication instruction or add a separate value for the letter. The numerical run total remains the relevant score.
More broadly, an inning cell is not always a simple completed block of identical length. A home team can finish a game by going ahead in its final turn at bat. The scoreboard is recording the outcome of that turn, not promising that every inning cell represents the same number of pitches, batters or minutes.
When teaching someone else, ask them first to identify the final score without interpreting the letter. Then ask which side was batting when the deciding event occurred. Finally, open the play-by-play to find the event itself. This sequence reduces the temptation to infer an entire final play from one unfamiliar symbol.
Keep the game result separate from the series position
A game score and a series tally use similar-looking numbers but describe different units. One counts runs within a game. The other counts games won across the series. Write the unit beside the number in a personal note, especially when discussing the event in a language different from the source page.
For an invented example, a club might win a particular game five to four while trailing a series two games to one. Neither pair of numbers contradicts the other. The first describes that day's contest; the second describes the accumulated series position. A headline that drops the unit can be confusing even when its arithmetic is correct.
Avoid converting a strong series position into a future result. A scheduled game has not been won merely because one team has momentum or a statistical advantage. Readers looking for the next fixture need the confirmed date and starting time, followed by a fresh check near the event. They do not need an invented certainty presented as a completed outcome.
Pitching decisions are not a complete performance ranking
The names beside the win and loss describe official pitching decisions. They do not, on their own, provide a complete comparison of all pitchers used. A reader assessing performance should also look at the actual innings, batters faced and events in context. Without those details, it is easy to give one label more explanatory power than it has.
The [MLB innings-pitched glossary](https://www.mlb.com/glossary/standard-stats/innings-pitched) explains that each recorded out represents one-third of an inning pitched. This helps a beginner avoid treating baseball's innings notation like an ordinary decimal. The glossary is used here only for that limited concept; the article does not import another league's postseason procedures into Japan's competition.
For a simple original arithmetic exercise, eighteen recorded outs equal six complete innings. Nineteen outs equal six and one-third. Twenty equal six and two-thirds. Counting outs first can be clearer than calculating from a display string. No pitcher in this article is assigned those invented workloads, and the exercise is not a reconstruction of Game 3's pitching changes.
Use the play-by-play for sequence, not imagined drama
The line score compresses a game. A play-by-play expands it by showing individual events. Use the two together: the line score identifies an inning worth examining, and the detailed record can explain how runners reached base, advanced or were put out. If the detailed page is unavailable, preserve that limitation instead of filling the gap with a plausible story.
A good question is specific: how did the tying run reach base, or which event immediately preceded the winning run? A vague question such as “who wanted it more?” cannot be answered by a scoreboard. It may express a fan's feeling, but it should not be presented as a verified explanation of the result.
The same caution applies to pitch descriptions. Do not call a pitch a fastball, assign a speed or describe its location unless the source actually supplies that information. A home-run entry confirms a scoring event. It does not automatically establish the pitcher's intention, the batter's private expectation or the atmosphere throughout the stadium.
Translate names and labels without changing identities
Japanese club pages may abbreviate a player's name in one table and provide the fuller name on a linked profile. Keep the original spelling in your notes until you have verified the identity. Two similar-looking abbreviations should not be merged merely because an automatic translation produces the same English word or surname.
Use a small personal key for recurring labels: date, opponent, completed status, innings and totals. That is often more reliable than translating a whole page and trusting every column heading without checking its position. Navigation menus can also dominate copied text, so make sure the figures you are reading belong to the match table rather than a nearby season summary.
If you share a translated summary, include the original official link. Readers who know the language can then inspect the source, while readers who do not can still verify the date and score visually. A translation should make the record easier to understand without pretending to replace the official record itself.
Make a compact scorekeeping worksheet
Start a page with the fixture identity and three short boxes: final game score, series position and next scheduled game. Underneath, reserve one row for the scoring innings. This structure keeps the most commonly confused information separate and leaves room for a source link and retrieval date.
Add a second section labelled “questions requiring detail.” Put unresolved matters there: a particular baserunning decision, a pitching change or a disputed scoring attribution. This makes the limits of your current knowledge visible. It also gives a future replay a purpose, because you already know which sequence you want to inspect.
Finally, write a two-sentence summary using only the verified entries. Read it back against the worksheet. Check that you have not swapped the home and visiting teams, changed a scheduled fixture into a completed one, or treated hits as runs. This short review catches mistakes that can survive a much longer but less organised discussion.
Conclusion
The official result resolves the immediate SoftBank–DeNA question, while the inning table explains the broad scoring order. A careful reader can go further by keeping runs, hits, pitching decisions and series wins in their proper categories. Start with the fixture identity, verify completion, and use detailed records only for the claims they actually support. That turns a crowded scoreboard into a useful account without inventing the missing parts of the game.
Sources and research note
NPB's dated Game 3 record and series overview, plus the two clubs' result pages, provide the match evidence linked above. MLB glossary links supply only the two brief terminology explanations, not Japanese series regulations. Google Trends Japan showed “ソフトバンク 対 dena” first in the selected past-24-hours list sorted by search volume, at 200K+ and active, during research at about 18:16 UTC on 27 October 2026. Original numerical examples are fictional. The accompanying conceptual illustration is not a match photograph or a team endorsement.