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.

Enter the casefile Read the evidence rules
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

Continue through the baseball collection

More scoreless games and pitcher matchups

Explore the 25-inning scoreless-duel history toolReview Sandy Alcantara’s scoreless-innings streakCompare MLB Sunday pitcher matchupsOpen the Sale versus Cole Cy Young matchup

State Transitions in the 1891 Casefile Engine

Read the explanation

The casefile engine tracks historical reconstruction across four phased rounds, unlocking progression and calculating scores through strict evidence rules. Selecting an incorrect filing creates a correction debt, clamping down a barrier that blocks all other items until resolved. A verified first-try decision unlocks the debt and expands the score bar by 134 points. Once all four puzzles are resolved and optional derived calculations are configured, activating Finalize unlocks the casefile for export in Markdown or JSON.

Historical Evidence & Mechanics in the 1891 Casefile Engine

How does the casefile engine model evidence triage, chronology, and scoring across the July 18, 1891 25-inning scoreless tie?

This interactive application simulates archival reconstruction of the July 18, 1891 baseball game between the Fargo Red Stockings and Grand Forks Black Stockings in Devils Lake, North Dakota. The game engine enforces four sequential deduction phases—evidence triage, timeline reconstruction, source matching, and record wording. Historical facts are evaluated against primary editorial accounts, while user interface actions update an internal state machine that tallies assignment-weighted scores and records correction debts when assertions contradict verified sources.

The game applies synthetic point weights (e.g., 400 points for triage, 280 for wording) and internal deduction debt rules designed for instructional gamification rather than historical baseball scoring. While historical accounts confirm total game duration (4 hours 10 minutes) and pitcher-outs (75 outs per pitcher), pitch-by-pitch sequence, pitch counts, and individual half-inning durations are unrecorded in 1891 primary documentation and are omitted from the factual record.

Try a worked example

In the default 'Reporter deadline' assignment, locate Round 1 ('Evidence triage') and the first claim: 'Fargo and Grand Forks finished 0-0 after 25 innings on July 18, 1891.' Click 'File as supported'. The feedback box immediately updates to 'The filing for c2 is now verified and stored in canonical player state.', the score increments from 0 to 133, and the item status changes from 'Unresolved.' to 'Resolved through player action and source evidence.'

Sourced Historical Record vs. Common Retellings

On July 18, 1891, the Fargo Red Stockings and Grand Forks Black Stockings played what Major League Baseball recognizes as believed to be the longest scoreless tie in professional baseball history. Starters George Raymer and William Gibbs both pitched all 25 complete innings without allowing a run. North Dakota was home to longest scoreless tie in baseball history

Because the game concluded in a 0–0 tie when players had to catch evening trains at 8:10 p.m., neither pitcher was credited with an individual shutout victory under baseball scoring conventions, leaving Cack Henley's 24-inning performance in 1909 as the longest individual complete-game shutout. North Dakota Nothing: The longest scoreless game in history | Sporting News

Doubleheader Context and League Aftermath

The marathon contest was the second game of a doubleheader, bringing the two clubs' combined action to 34 innings in a single day at the North Dakota State Militia Training Grounds in Devils Lake. North Dakota Nothing: The longest scoreless game in history | Sporting News

Facing financial difficulties, Grand Forks played just one additional game before disbanding, after which owner Tom Hill sold the wooden grandstand for lumber to settle player payroll and debts. North Dakota was home to longest scoreless tie in baseball history

Sources and further reading
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.