Ticket to Ride: Germany cover
2017BGG rank #1,561

Ticket to Ride: Germany

by Alan R. Moon · Days of Wonder

Browsing is free. Ask BoardGameBrain about this game when rules coverage is ready.

Players2–5
Time30–60m
ComplexityLight
Age8+

About the game

What is Ticket to Ride: Germany?

Ticket to Ride: Germany is a standalone game in the Ticket to Ride series. Over the course of the game, players collect cards in order to then claim routes on the game board between two cities. Ideally the players create a network of routes that connect the cities showing on their secret ticket cards. Players score points both for claiming routes and for completing tickets, with incomplete tickets counting against a player's score. In addition to scoring points for tickets, whenever a player places a route on the board, they claim a passenger from the two cities that form the endpoints for that route (assuming that the passengers have not already been claimed). At the end of the game, whoever has the most passengers of each of the six colors scores 20 points for that color; whoever has the secondmost passengers in a color scores 10 points. Whoever has the most points at the end of the game wins. Ticket to Ride: Germany combines most of Zug um Zug: Deutschland and the Deutschland 1902 expansion in one box. Zug um Zug: Deutschland, published solely for the German and Austrian market, consisted of the same map as Ticket to Ride: Märklin, but ZuZ:D didn't include the passenger mechanism from Märklin in which players scored additional points by moving passengers from city to city. The Deutschland 1902 expansion introduced a different method of scoring passengers, and that method is now present in this collection.

How it plays

Mechanics

Hand ManagementNetwork and Route BuildingOpen DraftingSet Collection

On the shelf

Categories

TrainsTransportation

Questions players ask

Questions to bring to BoardGameBrain

  • How do setup and the first turn work in Ticket to Ride: Germany?
  • When does scoring happen and what ends the game?
  • How should the table resolve an unusual timing or rules interaction?