Satisfactory Train Guide: Building an Efficient Rail Network

Trains show up in Tier 6 and they change how your whole factory moves stuff. Belts are fine for short hops, but dragging them a kilometer across the map eats materials, looks rough, and caps you at belt speed. One rail line does the same job for a one-time build cost, hauls thousands of items per trip, and the track itself doubles as a power line for free.

Rails come with their own rules, though. Signals only face one way, stations only stop trains arriving from one direction, and a badly signalled junction can deadlock a whole network. None of it is hard once it's laid out plainly.

Track signals and block sections explained

Both signal types unlock at Tier 6 under Railway Signalling. A Block Signal and a Path Signal each cost 2 Steel Pipe and 1 Computer, so once computers are flowing they're cheap to place everywhere.

What a block actually is

A block is just the stretch of track between two signals. If any part of a train is inside that stretch, the block counts as occupied and every signal leading into it goes red. An empty block reads green. That's the whole system.

You can watch this happen while placing a signal, because each block gets highlighted in its own color. That's the single best debugging tool in the game. If two separate tracks glow the same color, they're secretly one block, and that's usually why a signal is throwing an error at you.

Signals are directional, and a train will never move against one. The arrow on the hologram shows the forward direction, and pressing R flips between left-side and right-side placement. Signals snap to track joints, or you can drop one anywhere on a segment as long as it's at least 12 meters from the end. Put two signals on the same joint facing opposite ways and you've got yourself a bi-directional track.

Block Signals: the simple ones

So which one do you actually need most of the time? Usually the Block Signal. It locks the entire block for whichever train got there first, and that's all a straight double track or a station approach requires. Drop one every so often along a shared stretch so a following train can creep along behind the leader instead of waiting at the far end of one giant block.

Path Signals: for junctions

Path Signals do something smarter. Instead of locking the whole block, an arriving train reserves one specific path through it. Two trains can be inside the same block at once as long as their paths don't cross. The signal also checks that the train can get back out before letting it in, which keeps trains from stopping dead in the middle of an intersection and gumming up the works.

The phrase you'll see all over the community is "path in, block out." Every signal entering a block has to be the same type, so junctions get Path Signals on the entrances and Block Signals on the exits. Path blocks also can't contain a Train Station, and there's a long-standing bug where path blocks on a slope can let trains collide, so keep those ones level.

A few known gotchas are worth memorizing. Block Signals have a bug at merges where two trains can enter the same block anyway, so use Path Signals anywhere tracks come together. And rails that run too close together, or clip at a curve, count as one block even when they never connect, which produces confusing "signal loops into itself" errors. Leave at least one block of space between parallel lines.

Reading the lights

Green means a Block Signal sees a clear block, or a Path Signal has approved a path. Red means occupied, or, for a Path Signal, still waiting on a reservation (those sit red by default, which is normal). Any signal showing the error warning is treated as red. Common causes: a block with no exit signal, mixed entry signal types, a station inside a path block, or a signal at a dead end.

Last thing, and it explains most mysterious traffic jams: trains never re-route. The path is picked by shortest distance, and if that path is blocked, the train just waits. Automated trains start braking 250 meters before a red signal, but they won't pick a different track to get around a stalled train. One train parked on a single-track line stops everything behind it.

Station design for loading and unloading freight cars

Build order matters here. A Train Station comes with its own piece of track built in, so place the station first and connect rails to it afterward. Dropping a station onto an existing rail leaves it sitting there unconnected, and the same goes for platforms.

Platforms snap onto the back of the station in one continuous straight line. You can't put a rail piece between the station and a platform, though. If you try, the platform stops working. Stations are directional too: the round end of the roof and the arrows mark the front, and autopilot only stops a train arriving from that direction. Coming the other way, the train rolls straight through without touching anything.

Costs and specs

A Train Station costs 10 Encased Industrial Beams, 50 Plastic, 50 Concrete, and 200 Wire, and it burns a flat 50 MW whether anything is docked or not. A Freight Platform runs 5 Motors, 10 Encased Industrial Beams, 25 Plastic, 50 Concrete, and 100 Wire. Each platform has 2 conveyor inputs and 2 outputs, holds 48 stacks, and pulls 50 MW only while it's actively transferring. Parked, it idles at 0.1 MW, which is basically nothing.

The fluid version swaps belts for 2 pipe inputs and 2 outputs and holds 3,200 m³, which is 1.5 times the 2,400 m³ a fluid Freight Car carries. Its outputs give free head lift, 10 meters on the bottom port and 14 on the top one. Same deal on the way in: feed the lower inlet first, and add the upper one only if a single pipe can't keep up.

The 27-second pause

Every load or unload cycle takes 27.08 seconds, and during that window all belts and pipes into the platform freeze. Nothing moves in or out at all. Kind of a pain, but it's the reason train stations are the one place buffers earn their keep. An Industrial Storage Container next to a platform has matching dual inputs and outputs, so it keeps your machines fed while the platform is locked out.

Partial transfers have a quirk as well. The receiving side needs one completely empty slot before anything moves, so a platform that's full except for half a stack of room won't take a single item.

Lining cars up with platforms

Each platform lines up with one car behind the locomotive. Use Empty Platforms as spacers when a car should skip a position, say you grab steel in the first car at one stop and quartz in the second car at another. Recoloring cars helps you keep track of what's riding where when you're staring at a timetable at 2am.

How much one car can move

The hard ceiling is your two input belts. What you actually get depends on round-trip time, because of that 27-second pause on every pass. Here are the wiki's solved numbers with a pair of Mk.6 belts feeding the platform:

| Stack size | Round trip for max throughput | Items per car, per minute | | --- | --- | --- | | 50 (Computers) | 67.08 s | 1,431 | | 100 | 102.08 s | 1,793 | | 200 | 187.08 s | 2,052 | | 500 (Quickwire) | 427.08 s | 2,247 |

If your round trip runs longer than the fill time, the car just sits full part of the day and your real number drops. Fluid cars land somewhere around 1,000 to 2,000 m³ a minute depending on piping and round trip. Nitrogen gas is the odd one out: package it before shipping, since packaging squeezes it 4 to 1 and moving it unpackaged wastes the car.

One practical note before you build. The whole station line has to sit on flat ground, and a station with five platforms plus spacers can stretch past 100 meters, give or take. Scout the spot before you commit to it.

Timetables and multi-stop train routes

Every train gets its schedule in the Timetable. Open the locomotive and you can drag stations off the map into the route list, or hover a station and hit the plus button. Rename your stations first so the list reads like a route instead of a pile of defaults.

Then hit save. That sounds obvious, but timetable changes don't take effect until you save, and stop settings need saving separately on top of that. More than a few players have rebuilt a route twice because of it.

Stop settings

Each stop on each train has its own settings, behind the gear icon. A train can load and unload everything, handle only specific items, or do nothing at all, plus a wait timer in seconds before it departs. Per-train settings are what make shared stations work: four trains can hit the same hub and each pull only its own item off the platform.

Wait timers are handy when you want a train to top off a partially loaded car instead of leaving the moment it's able. Twenty or thirty seconds usually covers it. Leaving them at zero sends trains out as soon as they finish, which is what you want on most freight runs. Mostly your call based on how the line's running.

Reading your round trip

Grab a stopwatch and time one full loop, from the departure horn at a station all the way around to the next one. That's your round-trip duration, and it's the number that decides throughput. The table in the station section tells you the round trip each stack size wants. Quickwire at 500 per stack wants a route a hair over seven minutes long, so a short hop leaves that car badly underused.

Multi-stop routes change the math a bit. It's usually easier to size the drop-off platforms than to predict what each train contributes, since cars fill at different rates at different stops. If a destination needs 1,400 computers a minute and one train can't carry that, add a second train to the same loop before you start adding cars.

Routing quirks

Stations add a 100 meter penalty to any train that passes through without stopping. That means trains route around a station sitting on a main line whenever there's any way around it, which is usually what you wanted anyway.

The bigger quirk is that pathfinding never re-routes around traffic. The shortest route is locked in, occupied or not, so a train parked mid-line holds up everything behind it. A train you're driving yourself is worse: it makes an entire path block read as occupied to every automated train nearby. Park your hand-driven trains off the main line, or just don't leave them out there.

Bi-directional trains and train length

A single track with locomotives on both ends works fine and skips the end-of-line loop. The rules are simple enough. Only locomotives at the ends of a train can run autopilot, and they have to face away from the cars. Extra locomotives anywhere in the train still add pulling force, even facing the wrong way, so a mid-train loco is doing something for you on hills.

Don't mix bi-directional lines with loops in the same network, though. A loop lets the train flip its car order, and suddenly car one unloads where car two should be. As a network grows, one-direction loops cause fewer headaches than bi-directional single track.

Junctions and avoiding rail congestion

Building the junction itself

A split gets built by joining two rails into one, then adding a third rail at the joint. A junction can have at most three rails coming off one point, and a Railroad Switch Control appears where they meet, with a white arrow showing which way the switch is thrown. Now and then the control doesn't spawn at all, and the junction silently won't work. If a train gets stuck routing through a brand-new junction, rebuild the joint in a different order.

You also can't split a track right up against a station or platform. Leave a short piece of plain rail between them, or the switch won't take.

Signalling the junction

This is where "path in, block out" pays off. Path Signals at every entrance let trains reserve non-crossing paths and actually share the junction, and Block Signals on the exits keep trains from stopping inside it. Really big interchanges can chain Path Signals back to back, since a train reserves its whole path through the chain up to the next Block Signal. Keep path blocks level, and remember that a station can't live inside one.

Junction blocks should be tight. Every meter of track inside the junction is a meter a train holds while it waits for its exit to clear.

The real fix: double track

Signals can only do so much with a single track. The standard answer is a double-track mainline, one track per direction, driven on the right. Two trains going opposite ways never see each other, and trains going the same way just queue at signals like polite traffic. It costs more rail, and it's also the difference between a network that scales and one that deadlocks every third trip.

Space the two directions at least one block apart. Tracks sitting too close together can read as a single block (curves are the usual culprit), and then your signals throw errors that make no sense until you check the block colors.

Grade separation and waiting room

Where two mainlines meet, put one over the other. Bridges cost nothing but rail, and a spot where tracks merely cross still counts as one shared block, so both lines end up stopping for each other unless you separate them properly. The community "turbine" interchange designs linked from the wiki's Railway page are worth copying outright rather than inventing your own.

There's no stacker building in the game. Waiting areas are long snake tracks next to a busy station, and signals along the snake turn it into a proper queue. When a station backs up, adding a snake approach track fixes it for far less than a second station would cost you.

Electrifying track for locomotive power

There's one locomotive in the game and it runs on pure grid power. You don't load fuel at all. The trade is that it draws from your factory, 25 MW just to exist, up to 110 MW while accelerating or grinding uphill, and trains top out at 120 km/h. The HUD shows the sum for the whole train, so four locomotives reads anywhere from 100 to 440 MW depending on what they're doing.

The track is a power line

Powered rails carry electricity end to end. Plug a station into your grid and every station on that connected rail network joins it, along with anything wired to those stations. That makes rails the cheapest way to power a distant outpost. Instead of running power poles a kilometer, you run the rail you were building anyway and wire the far station.

One catch, and it bites people constantly. Two rails that cross without a junction don't share power. The connection has to be an actual junction where the rails snap together. Your Hover Pack taps rails for power too, which is a nice perk when you're out inspecting the line.

Braking gives a little back

Hold the key opposite your direction of travel and the locomotive switches to regenerative braking, pushing up to 33 MW back into the grid. Subtract the 25 MW it draws just to run and you net about 8 MW. That's a rounding error on a real factory, but it's free, and downhill runs with a heavy train give back the most.

The air brake on Space is the strong one, a fixed 900 kN at any speed, and the regenerative brake actually gets stronger below 80 km/h, 2,000 kN against 600 above it. Stack both for the fastest stop. The wheels on your cars glow red when you really lean on the brakes, which is a fun detail and nothing more.

Sizing the grid for trains

So how much grid does a rail network actually eat? Peak draw is what trips you, not the average. Four trains leaving four stations in the same minute can stack several hundred MW on top of whatever the factory is already pulling, and a tripped grid stops every locomotive mid-acceleration. The brakes keep working with zero power, so a train never rolls away uncontrolled, but one that trips out on a hill sits on the slope until power comes back.

Keep a few hundred MW of headroom, or give the rail network its own grid outright. Do that and trains turn into the most boring, most reliable transport in the game, which is exactly what you want from them.