Satisfactory Train Station Design and Signals: A Practical Guide

Almost every train problem in Satisfactory comes back to two mechanics. Trains take the shortest route to their destination and never reconsider it, and a signal decides who is allowed into the track ahead. Once those two are clear, station layouts and deadlocks stop being mysterious. This guide covers both, then applies them to the station designs that actually keep a main line moving.

How train pathfinding really works

The locomotive, not the signal network, calculates the route. It picks the shortest distance to the destination, and that calculation ignores whether the track is occupied. A train does not re-route around congestion; if the shortest way is jammed, it queues.

One number matters more than any other here: a train station adds a 100 m distance penalty to any route that passes through it. That penalty is the reason a branch station works. Through traffic sees the branch as longer track plus a 100 m fee, so it stays on the main line without you having to do anything clever.

The practical consequence is uncomfortable but useful: you cannot fix congestion by adding an alternative route and hoping trains balance across it. They will not. You change which route is shortest, or you change nothing.

Blocks and signals

A block is the stretch of track between two signals. If any part of a train sits in it, the block is occupied. Every block needs at least one entry signal and one exit signal.

• Block signals reserve the whole block. While a train is inside, every block signal leading in shows red.
• Path signals subdivide a block into individual routes through it, so two trains whose paths do not cross can be inside at the same time. They also look ahead to the next block signal, which stops a train from parking in the middle of an intersection.

There is one hard rule that catches almost everyone: all entry signals for a block must be the same type. Mix a block signal and a path signal on entries to the same block and the signals show an error, and automated trains refuse to enter at all. Exits can be mixed; entries cannot.

Two more rules worth memorising. Do not use block signals where tracks merge, because a merge needs the per-route reservation that only path signals give. And a station cannot sit inside a path signal block.

Station design that keeps the main line free

Branch, do not sit inline

Put the station on a siding off the main, with the turnout guarded by a path signal at each merge back onto the main. Through traffic then routes past it, helped by the 100 m station penalty. An inline station puts every passing train through your loading bay, and one slow unload stalls the whole line.

Parallel platforms for a busy destination

When several trains serve the same destination, run two or more platforms off one siding and put path signals at the split. Trains reserve whichever route is free rather than queueing for a single platform. Keep each platform its own block so a loading train does not hold the others.

Why most bypasses do not work

This is the most common mistake, and it follows directly from pathfinding. A bypass does not attract traffic because the platform is busy, because the pathfinder cannot see that the platform is busy. It only compares distance. If your bypass is longer than the route through the platform, trains will keep queueing for the platform while the bypass sits empty. Make the bypass physically shorter, and remember the station’s own 100 m penalty counts in your favour.

Give each platform room to clear

Place a signal after the platform, not just before it, so a departing train releases its block as soon as it is clear rather than holding the approach all the way to the next junction. Short blocks near stations and junctions, longer blocks on open track, is the pattern that scales.

Deadlocks and how to unpick them

A deadlock is a set of trains each waiting for a block another one holds. The usual causes:

• Block signals at a merge. Two trains get a green at the same moment and meet in the junction. Path signals at every merge entry.
• A junction with no room to exit. A train enters an intersection it cannot leave because the far side is full. Path signals look ahead for exactly this, so make sure the intersection is guarded by them and that a block signal sits just beyond it.
• A manually driven train. Drive a train into a path signal block yourself and the whole block counts as occupied, freezing every automated route through it.
• Bidirectional track. Single track shared in both directions invites head-on standoffs. Signal both sides of the joint, and convert the busy sections to one-way pairs when you can.

To unpick one, find the first train in the chain that is waiting rather than the last, and look at what its next signal is protecting. Manually driving one train clear of a junction usually restarts the whole network, and then you fix the signalling that allowed it.

Quick troubleshooting

Scaling the network

• Standardise train length so that every siding, platform and block on the network fits any train you build.
• Short blocks near junctions, long blocks on open track. Blocks that are too long make trains wait for track they will never touch.
• One-way pairs for the main line. It costs more foundations and removes an entire class of failure.
• Group destinations by material so a district’s unload stations sit together and belts, not the rail network, handle the last stretch.

The mechanics above are from the official Satisfactory wiki signal documentation, which is worth reading in full when you start building junctions with more than two entries.