Ruling — Ticket to Ride: Märklin

← Ticket to Ride: Märklin

You asked

How do I play?

Answered counted as answered

Asked with: Ticket to Ride: Märklinbg-21348-en-1e

**Setup**

1. Each player takes 45 Colored Train Cars, matching Passengers, and a Scoring Marker.[1]

2. Each player places their Scoring Marker on "Start" on the Scoring Track.[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 Card deck near the board and turn the top five cards face-up.[1]

5. Place the Most Completed Tickets Bonus Tile face up next to the board.[1]

6. Separate the Destination Ticket decks into a stack of short routes (Blue) and long routes (Brown) and place them next to the board.[1]

7. Each player draws four Tickets, announcing the combination of types being drawn.[1]

8. Each player decides which Tickets to keep (must keep at least two, but may keep three or all four) and returns unwanted tickets to their stacks.[1]

9. Reshuffle the two Destination Ticket stacks and place them next to the board.[1]

**The Game Turn**

1. The player with the best collection of Märklin trains or the youngest player goes first.[2]

2. Play proceeds clockwise, with each player taking one turn at a time until the game ends.[2]

3. On a turn, a player must perform one of the following four actions:

* **Draw Cards:** Draw 2 cards by taking any one face-up card or the top card from the deck (blind draw).[2] If a face-up card is taken, a replacement is turned face-up.[2] If a Locomotive Card is drawn from the face-up cards, the player may only draw one card instead of two.[3]

* **Claim a Route:** Play a set of Train Car Cards that match the color and quantity of the spaces in a route.[4] The player places one of their colored trains on each space of the route.[2][4] The player then moves their Scoring Marker along the Scoring Track based on the Route Scoring Table.[2][4] When claiming a route, a player may also place one Passenger in either city of that route, though only one Passenger is allowed per city.[2] All cards used to claim the route are discarded.[4]

* **Draw Destination Tickets:** Draw 4 Destination Tickets from the top of the decks.[2][5] The player must keep at least one, but may keep up to four.[2][5] Returned cards are placed at the bottom of their respective decks.[2]

* **Move Passengers:** Move one Passenger already on the board from their current city along any or all of the player's continuous routes.[2] The Passenger picks up one Merchandise Token from each city they move through, excluding the starting city.[2] The player cannot backtrack over the same route in a single turn.[2] At the end of the turn, the moved Passenger is removed from the game.[2]

**Ending the Game**

1. When a player's stock of colored train cars reaches zero (with 1 or 2 trains left at the end of their turn), every player receives one final turn.[5]

2. After the final turns, the game ends and players calculate final scores.[5]

**Scoring**

1. Points are earned by claiming routes, successfully completing paths on Destination Tickets, moving Passengers, and completing the most Destination Tickets.[1]

2. For Destination Tickets, add the value if the cities are connected, or subtract the value if they are not.[6][5]

3. The player with the most completed Destination Tickets receives the Most Completed Tickets Bonus Tile, adding 10 points to their score.[6]

4. The player with the highest total points wins.[6]

5. In the event of a tie for most points, the winner is the player among those tied who completed the most Destination Tickets.[6]

6. If still tied, the player with the highest total of Merchandise Tokens wins.[6]

[1] RULEBOOK Ticket to Ride: Märklin — Rulebook · p.3 · SETTING UP THE GAME · OBJECT OF THE GAME

[2] RULEBOOK Ticket to Ride: Märklin — Rulebook · p.3 · THE GAME TURN

[3] RULEBOOK Ticket to Ride: Märklin — Rulebook · p.4 · TRAIN CAR AND PASSENGER CARDS · Train cards · Locomotive cards · Locomotive + 4+ Cards · Passenger Cards

[4] RULEBOOK Ticket to Ride: Märklin — Rulebook · p.5 · CLAIMING ROUTES · IMPORTANT NOTE

[5] RULEBOOK Ticket to Ride: Märklin — Rulebook · p.6 · DRAWING DESTINATION TICKET CARDS · GAME END

[6] RULEBOOK Ticket to Ride: Märklin — Rulebook · p.6 · Calculating Scores

🔧 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 93 ms · ask 5641 ms · total 5735 ms
single-flight (PR-5): queued 0 ms · generation 5735 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 3, "score": 0.04918, "snippet": "The player who has the best collection of Märklin trains or is the youngest player goes first. Play then proceeds clockwise around the table, each player taking one turn at a time until the game ends. On his turn, a player must perform one (and only one) of the following four actions: 1. Draw Cards ", "headingPath": "THE GAME TURN", "sharpsignalDocId": 537}, {"page": 7, "score": 0.047371, "snippet": "Learn more at www.daysofwonder.com A ll aboard this computer game version of the famous award-winning board game : Ticket to Ride! Play against the game on the classic US and European maps, and discover the exclusive map of Switzerland. Play online against tens of thousand of other players all over ", "headingPath": "Mac OSX and PC Windows", "sharpsignalDocId": 537}, {"page": 5, "score": 0.047123, "snippet": "A route is a set of continuous colored spaces (in some instances, gray spaces) between two adjacent cities on the map. To claim a route, a player must play a set of Train Cards whose color and quantity match the color and number of spaces of the chosen route. A set of cards must be of the same type.", "headingPath": "CLAIMING ROUTES · IMPORTANT NOTE", "sharpsignalDocId": 537}, {"page": 8, "score": 0.046154, "snippet": "Here is your Days of Wonder Online Access Number: To use it, simply visit: www.ticket2ridegame.com and click on the New Player Sign-up button on the Home Page. Then just follow the instructions to discover variants, additional maps, discussion forums and join our community of players in online versi", "headingPath": "ONLINE PLAY · Game design by Alan R. Moon Illustrations by Julien Delval Photos by Märklin", "sharpsignalDocId": 537}, {"page": 3, "score": 0.032258, "snippet": "Each player takes a set of 45 Colored Train Cars along with the matching Passengers and Scoring Marker ❸ . Each player places his Scoring Marker on Start ❹ on the Scoring Track running along the map's border. Throughout the game, each time a player scores points, he will advance his marker according", "headingPath": "SETTING UP THE GAME · OBJECT OF THE GAME", "sharpsignalDocId": 537}, {"page": 4, "score": 0.030622, "snippet": "A player may have any number of cards in his hand at one time. When the deck is exhausted, the discards are reshuffled into a new draw pile deck. The cards should be shuffled thoroughly, since all the cards have been discarded in sets. In the unlikely event that there are no cards left in the deck a", "headingPath": "TRAIN CAR AND PASSENGER CARDS · Train cards · Locomotive cards · Locomotive + 4+ Cards · Passenger Cards", "sharpsignalDocId": 537}, {"page": 6, "score": 0.030303, "snippet": "A player can use his turn to draw more Destination Ticket Cards. To do so, he draws 4 new cards from the top of the two Destination Ticket Decks. A player may draw any combination of the two types of Tickets, but he must first announce what combination of Tickets he is drawing. If there are less tha", "headingPath": "DRAWING DESTINATION TICKET CARDS · GAME END", "sharpsignalDocId": 537}, {"page": 6, "score": 0.029851, "snippet": "Players should have already accounted for the points earned as they completed different routes and collected various Merchandise tokens. To make sure no mistakes were made, you may want to re-count the points for each player's routes and Merchandise tokens collected by Passengers. Players should the", "headingPath": "Calculating Scores", "sharpsignalDocId": 537}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 3, "quote": null, "headingPath": "SETTING UP THE GAME · OBJECT OF THE GAME", "sharpsignalDocId": 537}, {"page": 3, "quote": null, "headingPath": "THE GAME TURN", "sharpsignalDocId": 537}, {"page": 4, "quote": null, "headingPath": "TRAIN CAR AND PASSENGER CARDS · Train cards · Locomotive cards · Locomotive + 4+ Cards · Passenger Cards", "sharpsignalDocId": 537}, {"page": 5, "quote": null, "headingPath": "CLAIMING ROUTES · IMPORTANT NOTE", "sharpsignalDocId": 537}, {"page": 6, "quote": null, "headingPath": "DRAWING DESTINATION TICKET CARDS · GAME END", "sharpsignalDocId": 537}, {"page": 6, "quote": null, "headingPath": "Calculating Scores", "sharpsignalDocId": 537}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 537 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 537 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.90315 of 2922 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 15, 2026 12:22

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: Märklin — Rulebook (corpus doc 537)	THE GAME TURN	p.3	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	Mac OSX and PC Windows	p.7	0.047371 (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: Märklin — Rulebook (corpus doc 537)	CLAIMING ROUTES · IMPORTANT NOTE	p.5	0.047123 (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: Märklin — Rulebook (corpus doc 537)	ONLINE PLAY · Game design by Alan R. Moon Illustrations by Julien Delval Photos by Märklin	p.8	0.046154 (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: Märklin — Rulebook (corpus doc 537)	SETTING UP THE GAME · OBJECT OF THE GAME	p.3	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: Märklin — Rulebook (corpus doc 537)	TRAIN CAR AND PASSENGER CARDS · Train cards · Locomotive cards · Locomotive + 4+ Cards · Passenger Cards	p.4	0.030622 (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: Märklin — Rulebook (corpus doc 537)	DRAWING DESTINATION TICKET CARDS · GAME END	p.6	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: Märklin — Rulebook (corpus doc 537)	Calculating Scores	p.6	0.029851 (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 10 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: Märklin — Rulebook (corpus doc 537)	THE GAME TURN	p.3	#1	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	CLAIMING ROUTES · IMPORTANT NOTE	p.5	#3	0.047123 (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
#3	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	Calculating Scores	p.6	#8	0.029851 (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: Märklin — Rulebook (corpus doc 537)	Mac OSX and PC Windows	p.7	#2	0.047371 (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
#5	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	TRAIN CAR AND PASSENGER CARDS · Train cards · Locomotive cards · Locomotive + 4+ Cards · Passenger Cards	p.4	#6	0.030622 (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 re-ranker chose it
#6	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	ONLINE PLAY · Game design by Alan R. Moon Illustrations by Julien Delval Photos by Märklin	p.8	#4	0.046154 (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: Märklin — Rulebook (corpus doc 537)	DRAWING DESTINATION TICKET CARDS · GAME END	p.6	#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
#8	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	SETTING UP THE GAME · OBJECT OF THE GAME	p.3	#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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	SETTING UP THE GAME · OBJECT OF THE GAME	p.3	no quote on the wire
[2]	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	THE GAME TURN	p.3	no quote on the wire
[3]	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	TRAIN CAR AND PASSENGER CARDS · Train cards · Locomotive cards · Locomotive + 4+ Cards · Passenger Cards	p.4	no quote on the wire
[4]	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	CLAIMING ROUTES · IMPORTANT NOTE	p.5	no quote on the wire
[5]	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	DRAWING DESTINATION TICKET CARDS · GAME END	p.6	no quote on the wire
[6]	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	Calculating Scores	p.6	no quote on the wire

generation — timing and the path taken

timing split: retrieval 93 ms · first delta 1569 ms · total 5735 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 93 ms · ask 5641 ms · gateway work 5735 ms · total 5735 ms
tokens in (the prompt the answerer read): 2932
tokens out (what the answerer generated): 852
tok/sec: 206.6 tok/sec — 852 output tokens in 4.124 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 25s ago)
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 469), 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.