Subway Builder

Subway Builder’s commuter does not simply board the first train that appears. The developer’s simulation explanation says the route search evaluates departures within a thirty-minute window. Its example compares a local leaving in two minutes with an express leaving in ten: the later departure can offer the better journey.

That gives a timetable a role beyond putting more trains on a drawn line. The documented search includes walking to and from stations and between nearby transfer stations. A connection is therefore one part of the trip the model evaluates, rather than the whole answer to whether someone will use it.

The account also distinguishes time spent riding, walking, waiting on a platform and departing later than planned. Those receive different perceived-time weights. An earlier departure is not automatically the lowest-cost journey in the game’s decision model. This describes the developer’s rules; it does not validate the weights as a prediction for a particular real commuter.

The official site adds another operational consequence: too many trains on a line or an overcrowded station can cause delays. Frequency and a faster journey are therefore related decisions, not synonyms. No optimal headway follows from the documentation alone.

The attraction is watching a proposed service become a complete modeled trip. Before adding another train, consider what it changes for the person going from home to destination: the departure they choose, the walk, the transfer and the arrival. The later express is a useful reminder that a map connection can be available without being the journey the simulation prefers.