Factorio Space Age Trains: Platform Arrival Windows, Cargo Bay Handoff Timing, and 3 Deadlocks Fixed

The moment a cargo pod from your Vulcanus platform hits the landing pad, a clock starts. If your planet-side trains aren’t already cleared and ready, the next pod drop will scatter tungsten plates across the ground — no warning, no error, just a mess you have to robot-clean by hand. That handoff window is what most Factorio train guides never cover.

Factorio 2.0’s train signal rules haven’t changed. What changed is what arrives at your stations. Classical rail networks move ore and circuits between factories on a single planet. Space Age layers a second scheduling system on top — the space platform schedule — that must synchronize with your ground-side trains or the whole interplanetary supply chain stalls. This guide covers both layers and shows you exactly where they need to connect.

Verified against Factorio 2.0 (Space Age). Values may change with future updates.

Quick Start: 8 Steps Before You Lay a Rail

1. Pick LHD or RHD on the first rail you place — left-hand or right-hand drive; mixing them causes permanent signaling headaches across the whole save.
2. Chain signals at every intersection entry, rail signals at every exit — one rule that prevents 90% of deadlocks.
3. Every signal block must be at least as long as your longest train — a 4-wagon train that can’t fit in a block will block itself.
4. Place at least 2 extra cargo bays next to your landing pad — the base landing pad has 80 slots and 3 drop hatches; each cargo bay adds 20 slots and one more hatch.
5. Put buffer chests between the landing pad and your train loading station — trains load from chests via inserters, not directly from the pad.
6. Use “All requests satisfied” as your platform wait condition until you tune timing — this keeps the platform at the planet until everything requested has landed.
7. Set train station limits at every multi-train station — unset limits let unlimited trains queue and create gridlock.
8. Upgrade to rocket fuel as soon as Nauvis blue science is running — solid fuel caps top speed at roughly 272 km/h; rocket fuel hits roughly 298 km/h with 80% better acceleration.

Train Signal Refresher: The One Rule You Actually Need

Rail signals divide track into blocks — sections of rail where only one train can be present at a time. When a train enters a block, every signal leading into that block turns red and holds other trains out. The two signal types differ in exactly one way: how they handle a train that can’t yet proceed.

A rail signal lets a train stop and wait in its current block indefinitely. That works fine on open stretches, but it becomes a problem inside an intersection — a waiting train blocks every other path through that intersection simultaneously.

A chain signal refuses entry unless the train can confirm a clear path through to the next rail signal. If the exit is blocked, the train holds before the intersection rather than inside it. The practical rule from the official wiki: chain signals in and before crossings, rail signals at the exits of crossings.

A deadlock is what happens when that rule breaks. Four trains arrive at a four-way intersection from four directions simultaneously. Each enters because it could see a green chain signal — but now each blocks the exit of the train behind it, and every train waits for a train that’s also waiting. The network stops until you manually drive one train backward. The chain signal rule prevents this because a train that can’t see a clear exit block never enters the intersection in the first place.

Signal spacing rule: after the exit signal of any junction, the next signal must be placed far enough away to fit your longest train between the two signals. A 4-wagon train that half-fits into a block occupies that block entirely — the signal behind it stays red, and trains queue back into the junction. For 1-4 trains (one locomotive, four wagons), that means roughly 7 rail lengths between the junction exit and the next downstream signal.

Classic Nauvis Network Patterns

Choose your drive side before you build anything. Left-hand drive (LHD) and right-hand drive (RHD) are both valid; the Factorio community defaults to LHD. The choice itself doesn’t matter — mixing them in the same save does, because signals stop working correctly at junctions where the sides collide.

Train sizes use a shorthand that counts locomotives first, wagons second. A 1-2 train has one locomotive and two cargo wagons. A 2-4 has two locomotives on the front and four wagons. Locomotive count affects acceleration and grade performance; wagon count determines throughput per trip.

For the interplanetary context, the 1-4 train is the standard starting point. A cargo landing pad with two extra cargo bays holds 120 slots. A 1-4 train carries 160 cargo slots (4 wagons x 40 slots each). That means one train trip clears a full landing pad load with room to spare — the buffer chests in between absorb the timing gap while the train loads.

Station management comes down to two approaches. Train limits (set per station in the train stop GUI) cap how many trains can queue at a station at once — set them to 1 for dedicated routes, 2 to 3 for high-volume stations with stackers. Stackers are waiting sidings placed before busy stations so queued trains don’t block the main line. Use one or the other: train limits are simpler; stackers give more control at megabase scale.

The Interplanetary Handoff: The New Coordination Layer

Here’s what actually happens when a space platform reaches a planet: the platform hub GUI functions exactly like a train stop. Planets appear in the schedule as stops. Wait conditions — “all requests satisfied,” “inactivity 30 seconds,” circuit network signals — control when the platform leaves. The platform even outputs circuit signals for its current contents, destination, and velocity.

The cargo path from orbit to factory floor looks like this:

1. Platform arrives at the planet’s orbit position.
2. Cargo pods drop from the platform’s cargo bays to the planet’s cargo landing pads.
3. Landing pad inventory fills — 80 base slots, plus 20 slots per attached cargo bay.
4. Inserters extract items from the landing pad into buffer chests (the landing pad has no direct rail connection — inserters are the bridge).
5. Train loading inserters pull from those buffer chests into waiting wagons.
6. Train departs to the factory station.

The timing problem sits between steps 3 and 4. A landing pad with zero attached cargo bays has 80 slots and 3 drop hatches — it receives 3 item stacks per pod cycle. Each cargo bay you attach adds 20 more slots and one more hatch. With two extra cargo bays, you get 120 slots and 5 simultaneous hatches, which means faster drops and more buffer before overflow.

What happens on overflow: when the landing pad’s inventory is full and a cargo pod arrives, the items scatter on the ground near the pad. They don’t vanish — but you need construction robots or a deconstruction planner to recover them, which adds friction you don’t want in a running factory.

The buffer sizing rule of thumb: your landing pad plus buffer chest capacity should hold at least one full platform cargo drop. For a 1-4 train hauling 160 slots of tungsten plate, that means 160 slots of buffer. Two iron chests (48 slots combined) aren’t enough; four iron chests give you 96 slots of buffer that, combined with the 120-slot landing pad, covers the typical platform drop with margin. In practice, four to six iron chests behind the landing pad is the minimum that prevents scatter on a standard one-platform setup.

Platform wait condition strategy: “All requests satisfied” is the safest starting condition. It keeps the platform in orbit until every item it was asked to deliver has landed on the pad — it won’t leave mid-drop and strand you with a half-filled buffer. Once your network is stable and you want faster planet-to-planet cycling, switch to “Inactivity 30 seconds”: the platform leaves 30 seconds after cargo movement stops, which handles the case where some items simply aren’t available to send.

Dynamic request circuit: connect a constant combinator to the cargo landing pad’s circuit input and set it to output the maximum stock you want of each item. Connect an arithmetic combinator to subtract current pad inventory from that maximum. The landing pad reads the difference as its active request — it only asks the platform for what it actually needs, not a flat maximum every orbit. This prevents your platform from ferrying 200 tungsten plates when the buffer chests already hold 180.

Per-Planet Train Priorities

Each planet produces different cargo weights, throughput rates, and time constraints. A single train configuration doesn’t fit all four planets.

Vulcanus: Tungsten ore and tungsten plates are among the densest cargoes in the game. Two locomotives on a 2-4 train give 250% acceleration with nuclear fuel — crucial when hauling full wagons up elevated rail ramps. The foundry on Vulcanus runs continuously, so your train network needs consistent throughput rather than burst capacity. Set the foundry output station limit to 2 so a second train pre-queues while the first loads, keeping the foundry’s output buffer from backing up into production. Calcite trains run on a separate, lower-frequency schedule since calcite is consumed more slowly than tungsten plate. See the Factorio Vulcanus Guide for the full foundry production chain that feeds these trains.

Fulgora: Scrap recyclers output a random mix of items — the output side of recycling is inherently variable. Use circuit routing to direct trains to specific item-type stations rather than a single generic scrap station. Holmium plates are lightweight and high-value; a 1-2 train is efficient because you won’t fill four wagons before the next supply window anyway. Quality modules from electromagnetic plants are the lowest-volume output — dedicated 1-1 trains on a low-frequency schedule prevent quality modules from getting mixed with common outputs at the landing pad.

Gleba: Spoilage is the only train scheduling rule that Gleba adds. Bioflux, seeds, and organic products have a spoilage timer. A train waiting at a loading station under a “full cargo” condition while bioflux slowly rots is worse than a train that leaves half-empty. Switch your Gleba loading stations to “Inactivity 10 seconds” — if the inserters stop moving items for 10 seconds, the train leaves regardless of fill level. Small 1-1 trains also help: shorter loading time means less time waiting, which means less spoilage in transit.

Aquilo: Cold temperatures limit early infrastructure on Aquilo, and the planet’s output — cryogenic science packs and railguns — is comparatively low volume. The practical approach, widely used in the community, is to use the space platform itself as the primary distribution hub for Aquilo rather than building a full train network immediately. Cargo pods deliver everything Aquilo needs (crude oil, construction materials) and carry out science packs when production permits. A small 1-2 train covering the distance between the landing pad and the cryogenic plant is enough for early Aquilo logistics — expand the rail network only after the cryogenic science chain is stable.

Fluid Wagon Best Practices

A fluid wagon holds 25,000 units of fluid and has three connection ports, all on the top of the wagon. With pumps at both loading and unloading stations, you can push up to 3,600 L/s in Factorio 2.0 — significantly faster than piping directly from wagon ports without pumps.

Never mix fluids in one wagon. Each fluid wagon compartment locks to one fluid type once filled. If you send a wagon loaded with lubricant on a route that also loads sulfuric acid, and the wagon arrives with even one unit of lubricant in it, it won’t accept the acid. Use a dedicated wagon per fluid type, and name stations clearly — “Acid Load” and “Lubricant Load” as separate stops on the same route.

For the multi-planet chemistry chains Space Age introduces — Gleba’s bioflux into plastic, Vulcanus’s sulfuric acid for ore processing — the safest pattern is one train per fluid circuit, never routing two chemical fluids on the same consist. If you need higher throughput for a single fluid, add wagons to the same train rather than mixing types.

Fluids don’t travel well via cargo pods: you’d need to barrel them on the platform and unbarrel them on the ground. That adds assembly machine complexity on the platform. Route fluids planet-side via train; reserve cargo pod drops for solid items.

Fuel Progression: Solid to Nuclear

Fuel choice affects top speed and acceleration, not just burn time. The differences matter more than they look on paper because acceleration is what determines how fast a heavily loaded train recovers from stops at stations and signals.

Rocket fuel and nuclear fuel reach the same top speed, but nuclear fuel’s acceleration advantage is significant for heavy 2-4 trains. A 2-4 tungsten train on nuclear fuel reaches cruising speed in roughly half the distance of the same train on solid fuel — which matters on routes with multiple stations and intermediate signals forcing slow-downs.

The practical upgrade path: solid fuel until your Nauvis oil refinery is running consistently, then rocket fuel across all trains, then nuclear fuel specifically on your heaviest Vulcanus and long-haul routes. Don’t rush nuclear fuel — the uranium processing chain takes time to set up, and rocket fuel already gives you the full top speed bonus.

3 Common Space Age Train Deadlocks — Fixed

Deadlock 1: The Two-Junction Trap

What you see: two trains face each other at a T-junction, neither moving, with no other trains blocking them. You placed rail signals between two junctions that are too close together.

Why it happens: a train enters the first junction and its tail end sits in the second junction’s block. The second train waiting to enter the second junction can’t proceed because the first train’s tail is occupying its entry block. Both trains wait indefinitely.

Fix: replace the rail signals between the two junctions with chain signals. Now the first train won’t enter the first junction unless the block beyond the second junction is clear — its tail will never sit in the second junction’s entry block. Alternatively, space the junctions further apart so a full train fits between them.

Deadlock 2: Landing Pad Overflow Cascade

What you see: items scattered around your cargo landing pad; trains queued at the loading station but not moving; platform sitting in orbit not departing.

Why it happens: the platform dropped cargo faster than the buffer chests could drain to the loading station. The landing pad filled, overflow scattered, the circuit network reads the landing pad as full, and the platform’s “all requests satisfied” condition triggers — so the platform thinks the delivery is complete and prepares to leave while the ground side is still gridlocked.

Fix: add cargo bays to the landing pad (more hatches means faster drops and fewer overflow events), increase buffer chest count behind the pad, and set your loading station inserter conditions to trigger when the buffer is meaningfully stocked rather than running always-on. If inserters only fire when the buffer has items, you prevent the state where the train loads halfway and sits waiting while the pad overflows.

Deadlock 3: Train Limit Starvation

What you see: one factory station backed up with full buffers; another station running empty; trains queued at the full station even though the empty station needs supply.

Why it happens: the station limits are either unset (unlimited trains queue at whichever station they were assigned) or set too high relative to the number of trains in the pool. Trains reserve a slot at a station before they arrive — if a train is en route to station A, it holds a slot there, and another train sees slot B available and reserves it too. Both trains go to A; station B gets nothing.

Fix: set train limits at all stations to match physical capacity — if a station has one loading track, set the limit to 1. For multi-train setups with stackers, set the limit equal to the stacker depth plus one. Use circuit network output from the loading/unloading inserters to dynamically raise and lower the station limit: if inserters have been idle for 60 seconds, set limit to 0 so no new trains divert there.

Player Type: What to Prioritize First

Frequently Asked Questions

Do I need completely separate train networks on each planet?

No — but each planet needs its own naming convention for stations. Train schedules use station names as routing keys. If you name a stop “Iron Unload” on both Nauvis and Vulcanus, a train assigned to that name can route to either planet’s station, which breaks your supply chain. Prefix every station with the planet: “VULC — Tungsten Unload” vs “NAUVS — Iron Unload.” The actual rail networks are independent since planets are separate surfaces with no cross-planet track — but consistent naming prevents schedule confusion when you copy blueprints between planets.

What’s the minimum cargo bay count for a reliable landing pad?

Two extra cargo bays beyond the base pad gives you 120 inventory slots and 5 simultaneous drop hatches — the practical minimum for a 1-4 train route. With only the base pad (80 slots, 3 hatches), you’ll hit overflow regularly on any platform carrying a full cargo load. Three extra cargo bays (140 slots, 6 hatches) is the comfortable setup for two-platform supply chains where platforms arrive within a few minutes of each other. More than four extra bays gives diminishing returns unless you’re running a megabase with multiple platforms sharing the same orbit cycle.

How do I know if my handoff timing is off before things break?

Watch three signals. First, items scattered around the landing pad means overflow — your buffer is too small or your trains are too slow to clear it. Second, a platform sitting in orbit with a full cargo bay for more than two to three minutes under “all requests satisfied” means the landing pad is full and not draining — train frequency is too low. Third, empty buffer chests when the platform arrives means train frequency is too high — you’re sending trains on empty runs. The ideal state is buffer chests at 20 to 40% full when the platform arrives: enough buffer to absorb the drop, not so full that overflow is imminent.

Key Takeaways

Space Age doesn’t break Factorio’s train system — it adds a vertical handoff layer on top of it. The space platform schedule behaves exactly like a train schedule; the cargo landing pad behaves exactly like a train loading station with inserters and buffer chests. The only genuinely new coordination challenge is timing: your buffer between the landing pad and the train must be large enough to hold one full platform cargo drop without overflow, and your train frequency must drain that buffer before the next platform arrives.

Start simple — “all requests satisfied” conditions, 1-4 trains, four iron chests as a buffer — and tune from there. The chain signal rule and station limits are the same whether you’re running coal on Nauvis or tungsten from Vulcanus. Get those right first, then expand to per-planet train pools and circuit-based dynamic requests once the basics are running cleanly.

For a broader look at the Space Age expansion and progression, see the Factorio Space Age Beginner’s Guide. For Vulcanus-specific production chains and the tungsten logistics setup that feeds these trains, see the Factorio Vulcanus Guide.

Sources

• Tutorial:Train signals — Official Factorio Wiki
• Space platform — Official Factorio Wiki
• Cargo landing pad — Official Factorio Wiki
• Fuel — Official Factorio Wiki
• Friday Facts #381 — Space Platforms | Factorio
• Friday Facts #437 — Cargo Pod Deep Dive | Factorio
• What’s your interplanetary logistics strategy? — Factorio Forums (forums.factorio.com/viewtopic.php?t=125137)
• Factorio: Automated Space Logistics — marcleoseguin.com
• Logistic train vanilla — One train group — Factorio Forums (forums.factorio.com/viewtopic.php?t=117459)

Michael R.

I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.