Loading map…
Eighteen corridors and five subway extensions. Your own sequence of decisions.
Download the save file, or copy this text into a .json file. Import it to resume in another browser using this game version.
Look up a rule when you need it. The interactive introduction is always available from How to play.
New chapters use creative rules: optional challenges, funding assistance, and free recovery in Network. Major checkpoints are at least five years apart. Temporary weather closures and replacement buses last one recovery year, then reopen automatically. Older chapters keep their original rules until you choose a separate creative copy.
Headway: minutes between departures. Interchange: a place to change service. Capital: money for building and equipment. Operating budget: the yearly cost of running and maintaining service.
New chapters include fourteen fictional residents across six Toronto areas. Use the area selector to switch freely during play. Use People to inspect their stop-to-stop trips, Build to compare investments, and Journal to reflect on results. Journey calculations use a small, versioned scenario network, not current TTC timetables. The People tab explains all assumptions. Opening-day reveals compare actual model outcomes before and after service begins.
Capital is a hypothetical fund in constant 2026 Canadian dollars. Your annual allocation adds to it as years pass. A project's full chosen estimate is reserved upfront. The annual operating allowance must cover every committed project, including those still being built. This allowance covers your hypothetical programme, not the existing TTC operating budget. Unused operating allowance does not become capital.
Game durations: one year of study, one year of approval, then 1 year for bus priority, 2 for BRT, 5 for LRT or 9 for metro construction. Study spends 10% of the commitment; approval reaches 20%; construction spends the remainder. Cancellation before construction returns the unspent amount. These stages simulate a process; they do not confer actual permission.
Every operating project reaches a renewal review after 15 years. Renewal costs 8% of its original commitment and resets the review clock. An overdue review stays visible. New chapters include fictional checkpoints for construction, weather, flood readiness, junctions, peak strain and maintenance. These are deterministic stress tests, not observed incidents or a passenger-demand model. Older chapters keep their original rules until you choose to continue in a separate upgraded copy. Service adjustments change assumed vehicle and operating requirements; reduced service gives no capital refund.
Important checkpoints open automatically and pause time until you choose a response. You may inspect the map and return using “Decision waiting.” Every response shows its capital, annual cost and consequence before confirmation. A no-extra-capital option is always available, but it can delay opening or leave service strain.
Service condition starts at 100. Unresolved scenario penalties reduce it; the illustrative journey time increases by that same fraction. This is a game index, not punctuality, ridership or a risk probability. Use Network recovery actions to address a deferred problem. Citywide chapters add 4 weather or 6 flood damage points per unresolved year. At condition 20 or below, the player-built service is suspended until repaired. The Scores menu tracks these effects. Construction disruption is also a game index, not measured traffic delay.
The 18 corridor concepts follow representative TTC bus paths from the August 27, 2026 snapshot, with service-calendar dates in September–October 2026. They are not engineered rail alignments. Broad focus areas are curated portfolios; named neighbourhood matches mean at least one source stop lies inside its polygon. No walking access, capacity need or ridership follows from that match.
The first six concepts retain their detailed evidence in the evidence atlas. Added corridors need environmental, terrain and engineering screening. That missing evidence never means clearance. The baseline here is held at its sourced snapshot; Regional buses, GO journeys and future land-use changes remain incomplete. Two public projects open automatically in the game; other real extension corridors are explicit player-controlled alternatives.
Ranking weights are game rules: your selected area is prioritized, then the chosen goal balances stop-neighbourhood reach, listed connection hints, assumed time savings and costs. Budget approach selects the lower or upper estimate for commitments. Real regional travel totals and GDP do not determine route demand or public funding.
Within each corridor, compare the preferred modes plus a bus fallback. Recommend the highest-scoring option that fits both allowances, or show a deferred option if none fits. Your focus area sorts first, then affordability, then the score.
Score: 10 for a focus match; 0.30 per source-stop neighbourhood for the access goal (0.08 otherwise); assumed relative journey saving × 8 for speed (× 2 otherwise); up to four listed connection hints × 0.25; subtract capital in billions × 3 for value (× 0.5 otherwise), and annual operations in millions × 0.005. Connection hints are not verified walking interchanges. These weights are game design choices, not measured demand.
A frequency or stopping-pattern change may change costs and service without changing the top corridors. The project review shows those effects. No population, regional travel or environmental measurement is secretly substituted for missing corridor evidence.
All future events, costs, speeds, renewal cycles and timing are illustrative. Nextstop is not a calibrated transport model, forecast or official plan.
Corridor provenance and transformation · TTC source and licence · Census provenance
Contains information licensed under the Open Government Licence – Toronto. Census inputs adapted from Statistics Canada, 2021 Census, weighted 25% sample estimates. No agency endorsement.