Rebuild the -Inning Record

Trace the July 18, 1891 scoreless tie through claims, chronology, wording, and provenance. The final casefile reflects every decision you make.

0–0

Evidence before inference

Reconstruct one careful record from three named accounts.

Each round tests a different historical skill. A rejected filing creates a correction you must resolve before the record can move forward.

Event identity, pitching lines, duration, baseballs used, train ending, and aftermath.

Read MLB’s North Dakota history

Four-round reconstruction

Decide, correct, order, and finalize.

No correction is pending.

Evidence triage

Active

File each unresolved claim using the source boundary above.

Claim to verify: Fargo and Grand Forks finished 0-0 after 25 innings on July 18, 1891.

Unresolved.

Claim to verify: the marathon game occurred during the 1966 season.

Unresolved.

Claim to verify: play stopped at 8:10 p.m. because the clubs needed to catch trains.

Unresolved.

Record wording

Locked

Choose language precise enough for a public historical record.

Record qualifier

Unresolved.

Outcome type

Unresolved.

Ending reason

Unresolved.

Source match

Locked

Match each distinctive detail to the account that identifies it most directly.

Raymer and Gibbs hit, walk, and strikeout lines.

Unresolved.

Thirty-four total innings across the doubleheader.

Unresolved.

All 18 starters remained, with a defensive position swap after a first-base error.

Unresolved.

Timeline reconstruction

Locked

Use the paired controls to create any legal order, then submit. A rejected order remains editable.

  1. Play stops at 8:10 p.m. so the clubs can catch trains.

  2. The July 18 doubleheader begins; the marathon is game two.

  3. Grand Forks plays once more and then disbands.

  4. Tom Hill relocates the series to neutral Devils Lake grounds.

  5. Raymer and Gibbs trade zeroes for 25 innings.

Multiple orders are reachable; submit when the sequence is ready.

Artifact calculations

These canonical options add transparent arithmetic to the export. Some assignments require selections before finalization.

Casefile result

Locked: resolve and finalize all four rounds.

Casefile output remains locked until all four rounds are resolved and finalized.
Exports are locked until the casefile is finalized.

Reading the record

Confidence comes from provenance, not volume.

MLB supplies the event identity, qualified record wording, pitching lines, duration, train ending, and much of the aftermath.

1 of 3

The record stays inspectable

Every earned artifact keeps its citations.

These are the same three accounts used by the game, accessed August 25, 2026.

MLB event and pitching accountSporting News historical accountDickinson Press regional history

Twenty-five innings, no runs: rebuilding a record from the sources

A one-minute painted explainer of how this casefile game works, followed by the historical context and where to read more.

Read the narration

On July eighteenth, eighteen ninety-one, Fargo and Grand Forks played twenty-five innings of baseball, and nobody scored. This casefile game asks you to rebuild that record from three published accounts. Round one is evidence triage. File each claim as supported or unsupported. A zero to zero tie after twenty-five innings: supported. A retelling that puts it in nineteen sixty-six: unsupported. File one wrong, and the casefile locks. A correction appears, and you must fix that same item before anything else can move. That item also earns no points. Next, put five events in order: the move to neutral grounds at Devils Lake, the doubleheader, the duel itself, play stopping at eight ten p.m. so the clubs could catch their trains, and the aftermath. Then match each detail to the account that reports it, and choose careful wording: believed to be the record, and a scoreless tie, not a double shutout victory. Each assignment weights the rounds differently, out of a thousand points. Try Museum exhibit or Research review, then finalize your casefile and export it with its sources.

How the game scores, and the wider record

Only first attempts score

In the Reporter deadline assignment, triage is worth 400 points, wording 280, and timeline and source matching 160 each, for 1,000 in all. A wrong first filing creates a correction that must be fixed, and that item scores zero.

Careful wording matters

The game's sources describe the game as believed to be the longest scoreless tie in professional baseball. Box scores from 1891 regional leagues are thin, so a qualified claim is more defensible than 'undisputed'.

The arithmetic in the export

Optional calculations: 250 minutes is 4 hours 10 minutes; 25 innings is about 2.78 regulation nine-inning games; and two teams × 25 innings × 3 outs is 150 outs recorded.

Longer games, with runs

The longest Major League game by innings went 26, a 1–1 tie between Brooklyn and Boston on May 1, 1920. The longest professional game, Pawtucket vs. Rochester in the minors, went 33 innings in 1981.

Try it in the tool

  1. In Evidence triage, file the 1966-season claim as supported on purpose and watch the correction lock the casefile until you fix it.
  2. In Timeline reconstruction, use Earlier and Later to order the five events, then press Submit timeline.
  3. Switch to Museum exhibit or Research review, and tick the Artifact calculations an assignment requires before you finalize.

Sources and further reading

  1. North Dakota was home to longest scoreless tie in baseball history · MLB.com

    The game's main event account, used by the tool.

  2. North Dakota Nothing: the longest scoreless game in history · Sporting News

    Corroborates the neutral site, the doubleheader and the train ending.

  3. The longest scoreless professional baseball game took place in North Dakota · The Dickinson Press (InForum)

    Regional account used by the tool.

  4. Extra innings · Wikipedia

    Background on extra-inning rules and the longest games.

  5. Longest professional baseball game · Wikipedia

    The 33-inning Pawtucket–Rochester game of 1981.

Game details in the video come from the three accounts the tool cites; 1891 records are sparse, so treat specifics as those sources' reporting.

Separate historical evidence from a game score

What does completing the casefile establish, and what still needs source review?

This tool is a four-round fact-checking exercise. Its assignment, answer key and score are authored teaching rules. Completing the game records your choices; it does not discover archival documents, run a baseball simulation or independently authenticate a historical record.

Read the source claim carefully

MLB describes the contest as believed to be the longest professional scoreless tie. Read MLB’s qualified historical account

Keep that qualification when evaluating a record claim. Distinguish a modern retrospective from a contemporaneous scorecard or newspaper. The tool links editorial accounts and preserves its cached access dates; those dates are not automatic proof that a link was checked today. A regional republication does not automatically become an independent witness. Inspect what each source actually supports and what it attributes to earlier reporting.

Try a scoring example

The Reporter assignment gives claim triage 400 points across three items: 134, 133 and 133. An incorrect first answer on c1 loses its 134 points even after the required correction, leaving a possible maximum of 866 if everything else is correct. A corrected casefile can therefore be complete without scoring 1000. The score describes performance against the game’s rubric, not a confidence percentage for the historical claims.

Museum and Research use different weights and round orders. All assignment weights total 1000. A wrong timeline submission similarly loses its assigned points, while legal moves and correction remain available. A correct first attempt earns the allotted points; finishing the puzzle unlocks the next round.

Understand corrections and export locks

A wrong choice creates a correction debt on that exact item. The game disables other choices until it is corrected; this is a learning sequence, not an external verification service. In the chronology round, Earlier and Later reorder the same five events and Submit evaluates the arrangement.

The final puzzle becoming resolved does not itself unlock exports. Finalize is an explicit step. Reporter requires no selected calculation, Museum requires at least one, and Research requires at least two. Missing that requirement leaves the artifacts locked and permits retry. The optional calculations do not add score points.

Keep derived arithmetic separate from observed detail

The duration option converts 4 hours 10 minutes into 250 minutes. It does not assign a duration to any inning. The length option computes 25 ÷ 9 ≈ 2.78 regulation lengths, without creating additional games. The outs option uses 2 × 25 × 3 = 150 pitcher-outs under the complete-inning assumption. These are transparent arithmetic operations on the retained inputs, not recovered play-by-play.

Do not infer pitch counts, batter sequences, weather, pitch types or individual inning events from aggregate totals. An export should distinguish a sourced statement, a derived number and an interpretation. A plausible reconstruction is not a newly discovered record.

Read what the downloaded casefile contains

JSON includes the assignment, score, decisions, ordered chronology, selected calculation text, corrections, action history and sources. Markdown organizes the same work for the selected role. Neither export contains a complete archival box score or a saved browser project that this page can import.

The browser’s state hash summarizes the exercise state. It does not certify source authenticity, authorship or a third-party audit. Replay restores the selected assignment’s initial state and locks exports again; switching assignments starts a fresh sequence. Reload also starts the default assignment because this engine has no saved local workspace.

The existing explainer media is retained, but its narration has not been verified in this review. Use the inspected controls, source documents and downloaded artifacts to assess the exercise.

Super generates helpful tools and automates fact-checking across the internet proactively. If you enjoyed this tool, build your own with Super and share it with a friend.