Railways: track and operating lines

The one-minute explanation

This is the single most common railway mistake: laying expensive track, watching nothing happen, and concluding the railway does not work.

Track without a line is a corridor nobody uses. The railway list flags it directly, counting the segments no service runs over.

Building track

Choose a grade—standard or high-speed—and a track count, then pick endpoints. The path is shaped exactly as roads are, with route options and draggable anchors (Roads covers that in detail).

The quote adds something roads do not have: station costs at each endpoint, listed separately, and shown as free where a station of that grade already exists. Extending from an existing station is therefore dramatically cheaper than starting fresh—and a standard station does not satisfy a high-speed line's needs, so upgrading a corridor to high speed means paying for new stations.

Track count is what determines how many train paths per day the corridor can host. That number, not tonnage, is a railway's real capacity ceiling; exact figures are in Transport mode parameters.

Opening an operating line

The line editor sits behind a tab at the top of the rail build panel, and carries your currently selected endpoints across. Its fields, in the order they appear:

1. Service type and train length. Passenger or cargo, then the number of cars. Switching type resets the car count to that type's default, so set the type first.
2. Endpoints. Only settlements with a station appear.
3. Path options. Each candidate shows its station chain, distance, travel time, and—most usefully—the maximum daily round trips it can support and which link is the bottleneck. A path whose bottleneck has no remaining capacity is offered but disabled.
4. Stop pattern. One checkbox per station on the chosen path. The first and last are locked. Skipping intermediate stops makes the service faster for through passengers and useless for the settlements you skipped.
5. Round trips per day, bounded by the path's bottleneck.
6. Pricing stance: public service, balanced or commercial, each labelled with its fare band. See Tolls, fares and traveller choices.

A live preview shows monthly capacity, the rolling-stock cost, the resulting fare, estimated revenue, subsidy, operating cost and fund contribution before you commit.

Three conditions a line can be in

Two states are yours to set; the third happens to you.

Active

Publishes capacity, carries demand, earns fares, pays the full monthly operating cost.

Suspended

Carries nothing and costs nothing in operating expense. It keeps its definition and its rolling stock, occupies no train paths—and still blocks demolition of the track beneath it.

Interrupted

Not a setting but a diagnosis: the stored path no longer matches the network, usually because a link was demolished, split or replaced. The line carries nothing and earns nothing while still displaying its active label, and the track underneath keeps costing money. Both rail lists show an Interrupted operating lines section at the top with a jump to each one.

Interruption is the failure mode to watch for after any track surgery. Rebuilding a link is not enough—the line must be edited back onto a valid path.

Managing a line

The management view reports carried volume and utilization separately for each direction, alongside fares, revenue, operating cost, profit, subsidy and fund contribution. A line at 60% average utilization may be full outbound and near-empty inbound; only the directional figures reveal it.

Beside them sits the policy comparison: all three pricing stances evaluated for this line, each showing quarterly fare revenue, forecast subsidy, operating cost, predicted utilization and—unusually—the change in service score the stance would produce. Each card is a genuine re-run of pricing, demand assignment and economics, not a rule of thumb. Applying a stance takes effect at the next quarter.

Deleting a line removes the service and keeps the infrastructure. The confirmation says so explicitly, because the two layers are easy to conflate.

Fixing an overloaded or underused line

Railways do not slow down when crowded. Excess demand is simply not carried—it diverts to another mode or goes unserved—so the symptom of overload is a capacity shortfall, not congestion.

When a line is full, in ascending order of cost:

1. Add cars. No capital charge on an existing line; operating cost rises with train length. This is almost always the first move.
2. Add round trips, up to the bottleneck link's remaining daily paths—the editor names that link for you.
3. Expand the bottleneck: more tracks, or an upgrade to high speed.
4. Open a second line, on the same corridor or an alternative path.

Note the order carefully: do not reach for a cheaper pricing stance on a full line. Lower fares on a service that cannot carry more demand only enlarge the unserved queue while shrinking the revenue.

When a line is underused or losing money: reduce cars or frequency (the fixed monthly management cost remains either way), reconsider the stance—commercial for wealthy well-served corridors, public service where the connection is genuinely irreplaceable—or suspend it, which stops the operating cost while preserving the line for later.

Common misconceptions

“I built the railway but nothing uses it”

Track is a corridor. Until an operating line runs over it with stops at the settlements you care about, it carries nobody and contributes nothing to service scores.

“My line stops at every station on the route”

Only where you ticked the box. Stations on the path without a stop are passed through—they gain no service from the line at all.

“Adding cars costs another trainset”

Only when opening a line. Changing the car count afterwards is free in capital, costing only the higher monthly operating expense.

“Deleting the line removes the railway”

It removes the service. The track, its maintenance and its depreciation remain until you demolish the links—and demolition is blocked while any line, even a suspended one, still claims them.

Continue the collection