Ruling — Ticket to Ride: Germany

You asked

How do I play?

Answered counted as answered

Asked with: Ticket to Ride: Germanybg-225244-en-1e

Setup

1. Place the board map in the center of the table.[1]

2. Shuffle 60 Passenger Meeples in a cloth bag and draw them randomly to place them on the board according to the diagram.[1]

3. Shuffle the Train Car cards and deal a starting hand of 4 cards to each player.[1]

4. Place the remaining Train Car deck near the board and turn the top five cards face up.[1]

5. Each player takes 45 Colored Train Cars of their color and a matching Scoring Marker, placing the marker near the Scoring Track on the board.[1]

6. Place the Globetrotter Bonus Card face up next to the board.[1]

7. Separate Destination Tickets into a Short Ticket deck (Blue backs) and a Long Ticket deck (Brown backs), then shuffle both.[1]

8. Each player draws four Tickets, announces their chosen combination, and decides which to keep (must keep at least two, but may keep more).[1]

9. Place unwanted Tickets back into their respective decks and reshuffle those decks.[1]

Gameplay

The oldest player goes first, and play proceeds clockwise.[2] On a turn, a player must perform one (and only one) of the following three actions:

Draw Train Car Cards

* The player may draw two Train Car cards.[2]

* He may take one face-up card or draw the top card from the deck (a blind draw).[2]

* If a face-up card is taken, a replacement is turned face up.[2]

* The player then draws a second card from either the face-up cards or the top of the deck.[2]

* Note: If a face-up Locomotive is picked, it must be the only card picked that turn.[3] If a Locomotive is drawn from the top of the deck in a blind draw, it counts as a single card and the player may still draw a second card.[3]

Claim a Route & Collect Passenger Meeples

* A player may claim any open route on the board.[4]

* To claim a route, the player plays a set of cards equal to the number of spaces in the route; the cards must be matching (along with any Locomotives) and most routes require a specific color.[4]

* The player places one of his plastic trains in each of the spaces of the route.[4]

* All cards used to claim the route are discarded.[4]

* The player immediately scores points based on the route length using the Route Scoring Table.[5][2]

* The player collects one Passenger Meeple from each of the two cities (or country spaces) that were just connected; if a city has no passengers, none is taken.[4][2]

* A player may claim a maximum of one route on his turn.[4]

* A player cannot claim more than one of a Double or Triple Route during the game.[4]

Draw Destination Tickets

* The player draws four new cards from the top of either of the two Destination Ticket Decks.[5]

* The player must first announce what combination of Tickets they are drawing.[5]

* If fewer than four tickets remain in the decks, the player draws the available cards.[5]

* The player must keep at least one card, but may keep up to all four.[5]

* Returned cards are placed at the bottom of their corresponding deck.[5]

Game End and Scoring

1. The game ends when any player's stock of colored plastic trains reaches 0, 1, or 2 at the end of their turn, at which point each player receives one final turn.[5]

2. Players calculate final scores by adding points from:

* Claimed routes.[2]

* Successfully completed Destination Ticket routes (points are deducted for uncompleted routes).[5][2]

* The Globetrotter Bonus Card (15 points) awarded to the player who completed the most Destination Tickets.[6]

* Passenger Meeples: 20 points for leading in a color, and 10 points for having the second most passengers in a color.[6]

3. The player with the most points wins.[6]

4. Tie-breaking: If tied, the player who completed the most Destination Tickets wins; if still tied, the player with the most Passenger Meeples wins; if still tied, players share the victory.[6]

[1] RULEBOOK Ticket to Ride: Germany — Rulebook · p.2 · Components · 110 Train Car cards: 12 of each , plus 14 Locomotives · Setting up the game

[2] RULEBOOK Ticket to Ride: Germany — Rulebook · p.3 · Object of the game · The Game Turn · Drawing Train Car Cards

[3] RULEBOOK Ticket to Ride: Germany — Rulebook · p.3 · Locomotives

[4] RULEBOOK Ticket to Ride: Germany — Rulebook · p.3 · Claiming Routes · Example 1 · Collecting Passenger Meeples

[5] RULEBOOK Ticket to Ride: Germany — Rulebook · p.4 · Route Scoring Table · Drawing Destination Ticket Cards · Game End

[6] RULEBOOK Ticket to Ride: Germany — Rulebook · p.4 · Calculating Scores · Days of Wonder Online · Credits

One rule clearer, zero feelings hurt.

🔧 debug — where this ruling came from

outcome: ANSWERED — Answered
corpus profile: live,vps
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 192 ms · ask 5741 ms · total 5935 ms
single-flight (PR-5): queued 0 ms · generation 5935 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 3, "score": 0.048916, "snippet": "The object of the game is to score the highest number of total points. Points can be scored by: ♦ Claiming a Route on the map; ♦ Successfully completing a Continuous Path of routes between two cities (or a city and one of Germany's neighboring countries) listed on your Destination Ticket(s); ♦ Compl", "headingPath": "Object of the game · The Game Turn · Drawing Train Car Cards", "sharpsignalDocId": 1259}, {"page": 3, "score": 0.047643, "snippet": "A route is a set of continuous colored spaces (in some instances, gray spaces) between two adjacent cities on the map or between a city and one of Germany's neighboring countries. To claim a route, a player must play a set of cards equal to the number of spaces in the route. The set of cards must al", "headingPath": "Claiming Routes · Example 1 · Collecting Passenger Meeples", "sharpsignalDocId": 1259}, {"page": 4, "score": 0.047619, "snippet": "Players should have already accounted for the points earned as they completed different routes. To make sure no mistakes were made, you may want to re-count the points for each player's routes. Players should then reveal all their Destination Tickets and add (or subtract) the value of their Destinat", "headingPath": "Calculating Scores · Days of Wonder Online · Credits", "sharpsignalDocId": 1259}, {"page": 4, "score": 0.045476, "snippet": "Graphic Design Cyrille Daujean A special thanks from Alan and DoW to all those who helped play test the game: Phil Alberg, Buzz Aldrich, Dave & Jenn Bernazzani, Pitt Crandlemire, Terry Egan, Brian Fealy, Dave Fontes, Matt Horn, Craig Massey, Janet Moon, Mark Noseworthy, Mike Schloth, Eric Schultz, S", "headingPath": "Illustrations Julien Delval", "sharpsignalDocId": 1259}, {"page": 4, "score": 0.032258, "snippet": "When a player claims a route, he immediately scores the number of points indicated on the Route Scoring Table for the length of the route he just claimed. A player can use his turn to draw more Destination Ticket Cards. To do so, he draws four new cards from the top of either of the two Destination ", "headingPath": "Route Scoring Table · Drawing Destination Ticket Cards · Game End", "sharpsignalDocId": 1259}, {"page": 2, "score": 0.030769, "snippet": "♦ 1 Board map of the German empire at the turn of the century ♦ Colored Train Cars (45 each in White, Red, Purple, Yellow and Black, plus some extra replacement cars in each color) ♦ 200 Illustrated cards including: 55 Short Tickets 34 Long Tickets (Value of 3 to 11) 1 Globetrotter Bonus Card (value", "headingPath": "Components · 110 Train Car cards: 12 of each , plus 14 Locomotives · Setting up the game", "sharpsignalDocId": 1259}, {"page": 3, "score": 0.030303, "snippet": "Locomotives are multi-colored and act as wild cards that can be part of any set of cards when claiming a route. If a faceup Locomotive card is picked during a card draw, it must be the only card picked that turn. If a Locomotive is turned over as a replacement for a fi rst card draw during the turn,", "headingPath": "Locomotives", "sharpsignalDocId": 1259}, {"page": 1, "score": 0.029412, "snippet": "T urn of the century Germany... Through a fi ne autumn rain, a plume of smoke announces the arrival of the 4:15 train from Nuremberg in the Munich Central Station. The din of the massive engine grows more intense, culminating with a prolonged hiss as the locomotive halts at the platform, steam erupt", "headingPath": "", "sharpsignalDocId": 1259}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 2, "quote": null, "headingPath": "Components · 110 Train Car cards: 12 of each , plus 14 Locomotives · Setting up the game", "sharpsignalDocId": 1259}, {"page": 3, "quote": null, "headingPath": "Object of the game · The Game Turn · Drawing Train Car Cards", "sharpsignalDocId": 1259}, {"page": 3, "quote": null, "headingPath": "Locomotives", "sharpsignalDocId": 1259}, {"page": 3, "quote": null, "headingPath": "Claiming Routes · Example 1 · Collecting Passenger Meeples", "sharpsignalDocId": 1259}, {"page": 4, "quote": null, "headingPath": "Route Scoring Table · Drawing Destination Ticket Cards · Game End", "sharpsignalDocId": 1259}, {"page": 4, "quote": null, "headingPath": "Calculating Scores · Days of Wonder Online · Credits", "sharpsignalDocId": 1259}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 1259 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1259 boosted
answered-before recall: this ruling was answered, so past rulings were not offered
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
answer fence: passed — letter density 0.90670 of 3119 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Sep 6, 2026 14:27 UTC

retrieval — what the passage search returned

what this block IS: the PASSAGE SEARCH's own results — the same search that fills this page's closest-passages list — and NOT the passages the answerer read. Answering runs its OWN retrieval: a far wider candidate pool, re-ranked down to a final handful, plus floors this search never applies — the base rulebook, surviving errata corrections, and one slot per book on a multi-book read. Each of those armed only if THIS ask sent what it needs: the boost block names the ids it forwarded, and the scope line names the books it read. A document the answer CITES that no row here names is therefore EXPECTED, not a defect: two searches, two candidate pools, two orders. The answerer's own final rows are shown in their own block below, beside these and never mixed into them.

score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. This ruling ran the THREE-ARM fuse (full-text + vector + the doc-priority boost arm, which carried the base rulebook and/or the errata corrections this query matched), whose arithmetic ceiling is 0.04918 — all three arms ranking the same chunk #1 (ceiling = arms/(k+1) at k=60). The measured healthy band 0.016–0.033 was measured on TWO-arm asks and does not bound this one: its high end is the two-arm ceiling, and a third arm has room above it. A chunk only one arm ranked highly lands near 0.016 (that one arm's #1 vote), so 0.03 here is an excellent hit, not a 3% match.

per-arm ranks (the rank each search arm gave a chunk): NOT DISCLOSED by the gateway. Fusion happens gateway-side and only the FUSED score crosses the wire, so rulesage cannot show them without a gateway change. The rank column below is the FUSED rank (position in the returned list), which is real.

token count per chunk: NOT DISCLOSED — chunk token counts are not reported on the ask path. The character counts below are of the bounded snippet/quote rulesage actually received — a real measurement of what we hold, never an estimate of the chunk.

fused rank	document	heading	page	fused RRF score	snippet chars
#1	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Object of the game · The Game Turn · Drawing Train Car Cards	p.3	0.048916 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#2	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Claiming Routes · Example 1 · Collecting Passenger Meeples	p.3	0.047643 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#3	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Calculating Scores · Days of Wonder Online · Credits	p.4	0.047619 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#4	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Illustrations Julien Delval	p.4	0.045476 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#5	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Route Scoring Table · Drawing Destination Ticket Cards · Game End	p.4	0.032258 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#6	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Components · 110 Train Car cards: 12 of each , plus 14 Locomotives · Setting up the game	p.2	0.030769 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#7	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Locomotives	p.3	0.030303 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#8	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)		p.1	0.029412 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300

what the answerer read — the passages it actually had in front of it

what this block IS: the passages the ANSWERING read put in front of the answerer, in the order it read them — the other half of the two reads described above, and the one that decides what the answer could possibly say. Each row names the book it came from and where in that book it sits, what it scored when the search arms were fused, which arm carried it there, and whether the re-ranker chose it or a floor guaranteed it a slot. A row here that no passage-search row names is EXPECTED: a far wider pool, re-ranked, with floors the passage search never applies.

candidate pool: the answering read scored 8 passages, out of a ceiling of 80 set gateway-side. Both figures are reported by the gateway for THIS ask — measurements of what actually happened, not constants read out of anyone's source and printed here on faith.

floors armed for this ask: the base rulebook — armed · surviving errata corrections — not armed · one slot per book on a multi-book read — not armed. Every floor is stated on every ask, armed or not, so a floor that did not apply here is never mistaken for one this app does not know about.

arms fused for this ask: vector + full-text + the doc-priority boost arm. Stated separately from the rows because an arm that ran and carried nothing is a different fact from an arm that never ran.

read at	document	heading	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Claiming Routes · Example 1 · Collecting Passenger Meeples	p.3	#2	0.047643 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Route Scoring Table · Drawing Destination Ticket Cards · Game End	p.4	#5	0.032258 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Components · 110 Train Car cards: 12 of each , plus 14 Locomotives · Setting up the game	p.2	#6	0.030769 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Locomotives	p.3	#7	0.030303 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)		p.1	#8	0.029412 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + the doc-priority boost arm	the re-ranker chose it
#6	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Illustrations Julien Delval	p.4	#4	0.045476 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Calculating Scores · Days of Wonder Online · Credits	p.4	#3	0.047619 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#8	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Object of the game · The Game Turn · Drawing Train Car Cards	p.3	#1	0.048916 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text + the doc-priority boost arm	the re-ranker chose it

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Components · 110 Train Car cards: 12 of each , plus 14 Locomotives · Setting up the game	p.2	no quote on the wire
[2]	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Object of the game · The Game Turn · Drawing Train Car Cards	p.3	no quote on the wire
[3]	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Locomotives	p.3	no quote on the wire
[4]	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Claiming Routes · Example 1 · Collecting Passenger Meeples	p.3	no quote on the wire
[5]	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Route Scoring Table · Drawing Destination Ticket Cards · Game End	p.4	no quote on the wire
[6]	RULEBOOK Ticket to Ride: Germany — Rulebook (corpus doc 1259)	Calculating Scores · Days of Wonder Online · Credits	p.4	no quote on the wire

generation — timing and the path taken

timing split: retrieval 192 ms · first delta 1039 ms · total 5935 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 0 ms · retrieval 192 ms · ask 5741 ms · gateway work 5935 ms · total 5935 ms
tokens in (the prompt the answerer read): 3175
tokens out (what the answerer generated): 947
tok/sec: 197.4 tok/sec — 947 output tokens in 4.798 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 22s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 2s ago)
answerer node (the seat proxy's own header — this probe, not this ask): node1
stream path: streamed — the gateway pushed at least one accumulated draft
watchdog: first-token watchdog: 30s per arming window (rulesage.table.first-token-watchdog-seconds), re-armed once by the passages frame — so the worst case before a reader falls back to polling is 60s. Whether it actually fired is a BROWSER-side decision that never reaches the server, so it is not recorded here. The stream path above is the server's half of that story: whether a delta was emitted at all.
num_ctx · think posture: both are the CHILD's settings, not rulesage's, and no ask reply carries them — an answer never states which context window or think posture produced it. The live-seat line above reads them from the running child instead, where the gateway can answer for itself; it describes the child NOW, not this ask.

disposition

outcome: ANSWERED — Answered
abstain rationale (n/a — this ruling answered): answered — no abstain rationale applies

setup-shape — why the checklist band did or didn't render

decision: NOT_SETUP_SHAPED — no setup-shape pattern matched this question

errata registry — what the gate above had to match against

this game registers NO errata cards (edition 1189), so "no registered errata card matched" above could never have matched one

Errata scope: the gate above matched this ruling's own edition only. When an ask also reads an expansion, that expansion's own registered errata cards stay outside the match — a stated phase-1 limitation, not a failed lookup.