Ruling — Ticket to Ride: Märklin

You asked

How do I setup the game?

Answered counted as answered

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

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

2. Create stacks of Tokens with the highest number on top and the lowest number on the bottom, consisting of one stack of black Tokens (7, 6, 5 & 4), six stacks of red Tokens (4, 3 & 2), twelve stacks of Yellow Tokens (3, 2 & 1), and sixteen independent white Tokens (2).[1]

3. Place the different stacks on the corresponding cities, matching the color of the city to the color of the Token stack.[1]

4. Each player takes a set of 45 Colored Train Cars along with the matching Passengers and Scoring Marker.[2]

5. Each player places his Scoring Marker on Start on the Scoring Track running along the map's border.[2]

6. Shuffle the Train Car Cards and deal a starting hand of 4 cards to each player, then place the remaining deck of Train Car Cards near the board and turn the top five cards from the deck face-up.[2]

7. Place the Most Completed Tickets Bonus Tile face up next to the board.[2]

8. Separate the deck of Destination Tickets into one stack of short routes (Blue background) and a second stack of long routes (Brown background), and place each of them next to the board.[2]

9. At the beginning of the game, each player draws four Tickets, announcing the combination of the two types of Tickets being drawn.[2]

10. Each player looks at his Destination Tickets and decides which ones he wishes to keep, keeping at least two but potentially three or all four.[2]

11. Place unwanted tickets back into their respective stacks.[2]

12. Reshuffle the two stacks and place the two separate decks of short and long Destination Tickets next to the board.[2]

13. Players keep their Destination Tickets secret until the end of the game.[2]

[1] RULEBOOK Ticket to Ride: Märklin — Rulebook · p.2 · COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME

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

The sage rests. The game continues.

🔧 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 216 ms · ask 2904 ms · total 3125 ms
single-flight (PR-5): queued 0 ms · generation 3125 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 3, "score": 0.04918, "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": 3, "score": 0.048131, "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": 5, "score": 0.047371, "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": 2, "score": 0.046898, "snippet": "◆ 1 Board map of Germany with train routes ◆ 240 Colored Train Cars (45 each in White, Red, Purple, Yellow and Black, plus 3 extra \"replacement\" cars in each color) ◆ 165 Illustrated cards: 118 Train Car cards - 11 each of Blue, Red, Green, Yellow, Black, Purple, White and Orange 14 Locomotives 6 Lo", "headingPath": "COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME", "sharpsignalDocId": 537}, {"page": 6, "score": 0.03125, "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.030303, "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}, {"page": 7, "score": 0.029851, "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": 8, "score": 0.029412, "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}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 2, "quote": null, "headingPath": "COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME", "sharpsignalDocId": 537}, {"page": 3, "quote": null, "headingPath": "SETTING UP THE GAME · OBJECT OF THE GAME", "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.90857 of 1389 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Sep 30, 2026 18:46 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: Märklin — Rulebook (corpus doc 537)	SETTING UP THE GAME · OBJECT OF THE GAME	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)	THE GAME TURN	p.3	0.048131 (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.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
#4	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME	p.2	0.046898 (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)	DRAWING DESTINATION TICKET CARDS · GAME END	p.6	0.03125 (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)	Calculating Scores	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
#7	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	Mac OSX and PC Windows	p.7	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
#8	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.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 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)	SETTING UP THE GAME · OBJECT OF THE GAME	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)	COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME	p.2	#4	0.046898 (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)	ONLINE PLAY · Game design by Alan R. Moon Illustrations by Julien Delval Photos by Märklin	p.8	#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
#4	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	CLAIMING ROUTES · IMPORTANT NOTE	p.5	#3	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)	Mac OSX and PC Windows	p.7	#7	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
#6	RULEBOOK Ticket to Ride: Märklin — Rulebook (corpus doc 537)	Calculating Scores	p.6	#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))	vector + 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	#5	0.03125 (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)	THE GAME TURN	p.3	#2	0.048131 (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: Märklin — Rulebook (corpus doc 537)	COMPONENTS · IMPORTANT NOTE · SETTING UP THE GAME	p.2	no quote on the wire
[2]	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

generation — timing and the path taken

timing split: retrieval 216 ms · first delta 979 ms · total 3125 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 216 ms · ask 2904 ms · gateway work 3125 ms · total 3125 ms
tokens in (the prompt the answerer read): 2924
tokens out (what the answerer generated): 408
tok/sec: 200.2 tok/sec — 408 output tokens in 2.038 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 52s ago)
answerer host (measured by rulesage): reachable (for 48h, checked 8s 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: NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
pattern that matched: SETUP — "setup" / "set up"
matched words (in the normalized question): setup

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.