Logistics

【Factorio】How to Build a Main Bus and Decide Its Width

A main bus is one of the most manageable factory designs in Factorio, flowing primary materials in one direction and branching to individual production lines. Based on vanilla v2.0, this guide uses reference values like yellow belts at 15 items/sec, red belts at 30 items/sec, and 48 stone furnaces per yellow belt to explain main bus fundamentals, typical 4-belt+2-tile spacing, and how many iron plates, copper plates, and green circuits to allocate.

Logistics

【Factorio】How to Build a Main Bus and Decide Its Width

A main bus is one of the most manageable factory designs in Factorio, flowing primary materials in one direction and branching to individual production lines. Based on vanilla v2.0, this guide uses reference values like yellow belts at 15 items/sec, red belts at 30 items/sec, and 48 stone furnaces per yellow belt to explain main bus fundamentals, the reasons the standard "4 belts + 2 tiles" layout is widely adopted, and how many iron plates, copper plates, and green circuits you should allocate.

I once had copper dry up immediately after unlocking blue science, and had to rebuild a thin bus almost from scratch. From that experience, I can say with confidence that the main bus design's stability in mid-game depends far more on securing 2–3× the initial width from the start than on neat appearance.

This guide serves as an entry point for beginners to move beyond "just laying things down" and judge by the numbers, and for intermediate players to establish a baseline for how to fit a standard ~14-belt bus to their factory scale.

【Factorio】What Is a Main Bus? Prerequisites Before Deciding Width

The Main Bus Definition and Role

A main bus is a design method that consolidates primary materials like iron plates, copper plates, steel, and electronic circuits into a single directional flow, then branches sideways at necessary points to feed each production line. Think of it as building the factory's backbone first, then branching off red science, green science, ammunition, and module ingredients as individual lines from that spine.

The reason this approach is favored in Factorio is straightforward: the material flow becomes visible. You can easily see where iron flows, where copper runs short, and which materials are jammed, making it less likely for the factory to become spaghetti-like. Guides on main bus construction also cover this concept—consolidating key resources into a trunk line and distributing to individual branches—as a fundamental principle.

Let's align terminology early. Conveyor belts are the basic equipment for transporting materials; yellow can carry 15 items/sec, and red carries 30 items/sec. Underground conveyor belts thread belts underground to avoid crossings—frequently used in main buses to cleanly handle branching and crossing. What matters isn't just visual neatness but making clear which lines are primary trunks and which are branches.

A common layout pattern is grouping 4 belts together and leaving gaps between groups. This isn't so much a mathematical optimum as a practical standard that emerged because branching, crossing, and expansion become much easier to work with. For example, arranging 4 iron plates, 4 copper plates, 2 green circuits, and 2 steel makes it instantly clear how many belts of each material you have when looking at the factory.

In my early days, I once thought "if it looks convenient, I should put everything on the main bus"—gears, copper wire, brick, coal—and consolidated everything into the central trunk. While it looked tidy, only the width ballooned, and the distance to branching points grew, reducing work efficiency. A main bus works better when viewed as a trunk line carrying only primary materials used repeatedly across the factory, not an all-in-one strip.

Adoption Merits and Demerits

The main bus's greatest merit is clarity. With material flow unified in one direction, you can trace iron-flow lines for iron shortages or copper-flow lines for copper shortages to find the root cause. When expanding, you simply add a new assembly block beside the existing line and cut needed materials from the bus, making expansion planning straightforward. Guides like "Factorio Factory Design Philosophy: Mastering the Standard Main Bus" also emphasize visibility and high expandability as major advantages.

Another strength is standardized branching. Rather than rethinking the configuration from scratch each time, having a pattern—"trunk runs vertically, assembly on one side, pull only needed materials sideways"—reduces workload considerably. Beginners especially struggle more with routing than shortages themselves. A main bus eases that confusion. Its excellence as an entry point to factory design comes largely from reducing the amount of thinking required.

However, drawbacks are equally clear. First, it consumes a lot of space. Because you reserve empty lanes for the future and gaps between groups, the same output requires more land than a dense layout. Furthermore, transporting materials over distance increases belt consumption. Early on, this cost is heavy, and if you load materials "just in case," infrastructure swells before the factory grows.

Efficiency-wise, a main bus isn't an optimal-efficiency approach. For megabases prioritizing UPS or SPM, direct rail connections, dedicated lines, and on-site production become more rational. For example, electronic circuits consume enormous quantities and couple tightly with copper wire. Looking at ratios, if you want to flow green circuits at 15 items/sec, you need copper wire at 22.5 items/sec. Even from this single view, it makes sense to build a dedicated block for copper-plate-to-circuits and feed only finished circuits back to the bus, rather than threading copper wire through a long trunk.

💡 Tip

Think of a main bus not as "a method to unify the entire factory" but as "a technique to place only commonly repeated materials on a shared trunk line." This prevents design failures.

Factorio Factory Design Philosophy: Mastering the Standard Main Bus welovefactorio.com

Target Version and Scope of This Article

This article focuses on vanilla v2.0. Main bus concepts have been widely used since earlier versions, but to help readers make practical decisions, the premises align with the current vanilla environment. The scope is narrowed because bus width directly connects to the factory's overall logistics design. In vanilla, designing to organize and flow primary materials on Nauvis often remains strong, functioning as a foundation for standard factory building.

Space Age, released 2024-10-21, is a paid expansion. For early-game Nauvis setup, main bus effectiveness remains quite similar. Organizing iron plates, copper plates, steel, and circuits in a trunk line to stabilize research and intermediate supplies works directly. However, mid-to-late game brings planetary specialization and alternate logistics, so you can't assume one continuous main bus expansion through endgame. This article thus treats Space Age as supplementary, distinguished from vanilla standards.

In Space Age, the premise "unknown materials appear later" becomes stronger, so taking even wider initial width has practical examples. Conversely, feeding everything to the trunk becomes less necessary; materials like blue circuits or sulfur with consolidated consumption centers work better as adjacent blocks. This understanding—that conventional main buses work early in Nauvis but shift to mixed designs late—is most accurate to actual play.

Main Bus Basic Layout | Why Is Standard?

The Logic of 4 Belts Per Group + 2 Tiles Between

The classic main bus format groups 4 conveyor belts and places a 2-tile gap between groups. This isn't cosmetic convention—it's highly logical when repeated branching is in mind. Keeping 4 belts together makes it easy to "handle the same material as a bundle," like 4 iron plates and 4 copper plates, and which material group ends where becomes obvious at a glance.

What matters equally is the 2-tile gap between groups. This space isn't wasted. It becomes an escape route when using underground belts for crossing and extraction, reducing belt-to-belt intersections. It serves as a walking route and provides room to place electrical poles for powering assembly lines. In other words, treating a 4-belt bundle and 2-tile margin as one unit makes transport, branching, and maintenance simultaneously workable.

Early on, I thought gaps were wasteful and packed them tightly, but the moment I reorganized to 4+2 format, the sense of doing major construction every branch-off dropped noticeably. Underground belt swaps alone settled the extraction shape neatly, and adding assembly lines later rarely broke the main trunk. This lightness in operation is the biggest reason it became standard.

Guides like "Main Bus Factory Design" and factory design documentation also present 4-belt grouping with gaps as the fundamental approach. There's no need to completely reject 3 or 6 belts, but in practical handling, 4-belt divisions balance very well.

【Factorio】Strategy Blog ③ Main Bus Factory Design maruwakablog.com

Branching, Merging, and the "Outer-First" Approach

The 4-belt format works well because it's compatible with underground-belt-based branching. Main buses repeatedly need to pass materials sideways without stopping the trunk. If you constantly try to pull inward, belt-to-belt crossings multiply and wiring quickly gets complex. With 4 belts grouped, you can relatively smoothly extract from either outer side.

My guiding principle here is "prioritize branching from outer belts." With 4 belts, first pull from the outer one nearest the assembly area; if more is needed, use the next one inward. Fixing this rule makes branching decisions at each point much simpler. You stop thinking "should I extract from the center or the edge?" each time.

Outer-first priority has real advantages beyond appearance. To deliver materials stably to the bus's far end, having early lines consume from the outside rather than the inside keeps flow traceable. When feeding critical lines, reading how much each belt is used becomes easier. As a result, you can read how the supply tapers toward the end. When later expanding production runs for merging back, clarity about which bundle and where to return materials keeps the trunk organized. The main bus thrives on using the same rules consistently rather than shortest connections. The 4-belt grouping makes those rules visible.

💡 Tip

When branching gets confusing, first check if you can pull from an outer belt. This alone makes underground belt routing much smoother and lets you expand without breaking the main line.

Single-Side vs. Both-Sides Layout Trade-Off

After laying the main bus, whether you expand assembly only on one side or spread to both sides significantly affects how manageable the factory becomes. Pure space efficiency favors both-sides: the same bus length feeds production lines left and right, compressing land use.

Yet for beginners to intermediates, single-side expansion is overwhelmingly easier to manage. The reason is simple: branching direction, power routing, walking paths, and expansion space all align in one direction. If you decide to place assembly blocks only on the bus's right side, all branches become consistently right-facing. Tracing which material strip was pulled for what is easier, and extending a line later just means "expanding right."

Both-sides expansion becomes harder because design rules double. Your right side pulls copper and iron in one order; your left side threads underground once more before pulling, creating small exceptions that pile up. The main bus's visibility suddenly worsens. When expansion on one side starts interfering with branching positions on the other, it becomes hard to spot gaps. Width efficiency rises, but cognitive load during expansion grows substantially.

I once attempted both-sides for compactness but hit capacity walls with nearly every expansion after blue science. When "this material was used on the right too" and "I can't remember where I pulled steel on the left" become common, fixing one branch cascades into full reconstruction. After shifting to single-side, despite using slightly more land, I could track factory state in my head far longer.

The main bus inherently prioritizes structural visibility over land efficiency. With that premise, coupling 4+2 grouped belts, single-side assembly, and outer-priority branching raises main bus usability noticeably.

Deciding Main Bus Width | Working Backward from Demand to Determine Belt Count

Set Your Target Stage First (Red-Green / Blue-Purple-Yellow / Pre-Rocket)

Rather than deciding bus width by feel ("better be wide"), determine which tech stage you want this bus to handle first. I personally divide this into three: through red-green, through blue-purple-yellow, and through pre-rocket. Width is determined by demand, not terrain, so setting an endpoint first is the design's starting point.

A small bus works for red-green. Flowing iron plates, copper plates, and green circuits with side-production for shortfalls is very manageable. Scaling to blue-purple-yellow raises iron and copper consumption, making green circuits less negligible. Stretching to pre-rocket means starting with "2 of each" runs a high risk of later bottlenecks.

Critically, don't try loading all materials to the bus initially. Base width decisions on primary materials like iron plates, copper plates, and green circuits—used repeatedly across lines and directly affecting bus numbers. Conversely, materials with narrow use cases better become dedicated lines at the stage they're needed. Note: "around 14 belts" is a community guideline example, not a hard value. For precise design, reverse-calculate from your target stage and supply capacity.

My early stumbling point was exactly here. Treating blue science as an extension of red-green, visible bottlenecks are very different at the same width. Leaving the target stage vague makes "why are we short?" impossible to answer later. Setting your target stage upfront clarifies both necessary-belt calculations and future expansion decisions.

Reverse-Calculating from Belt Throughput and Smelting Capacity

The practical work of width-setting is converting needed volume into belt equivalents. The sequence is: 1) set target stage, 2) estimate needed volume of commonly used materials, 3) convert to belt count from throughput and smelting capacity, 4) add margins and finalize width. The numerical foundation here is yellow belts at 15 items/sec and red belts at 30 items/sec. Switching to red mid-way doubles capacity per belt.

Supply-side confirmation is equally essential. One stone furnace produces iron plates at 0.3125/sec, so 48 furnaces are needed to fill one yellow belt. Steel furnaces need 24 per yellow belt. In other words, wanting 2 iron-plate belts requires not just 2 belts but also 96 stone furnaces or 48 steel furnaces as backing. A 4-belt iron bus without matching smelting capacity is just a visually wide unfilled bus.

Green circuits work the same way. Electronic circuits require a 3:2 copper-wire-to-circuit ratio, so flowing 15 green circuits/sec (one yellow belt) needs 22.5 copper wire/sec. But converting that 22.5/sec into "how many belts" and "how many assemblers" requires specifying what assembler type (with its craft speed) and modules you're using. Practically, the sequence is: 1) set target items/sec, 2) check recipe craft time and output per item, 3) calculate assembler count from craft speed, 4) convert that production speed to belt equivalents. When citing assembler types (Assembling Machine 1/2/3), attaching a primary source like the Factorio Wiki is recommended.

A design tip is to bulk up shared materials first and cut special ones to dedicated lines. Keep iron, copper, and green circuits as main trunk, then split other materials to dedicated production when needed. This improves bus clarity. When the bus feels tight, checking smelting capacity and branching organization before adding belts usually hits the real cause faster.

The 2–3× Margin Philosophy and Width-Decision Checklist

Once necessary belt count is clear, don't use that number as-is. In actual operation, demand estimates nearly always grow. New intermediate materials tempt additions to the bus; copper plates assumed at 2 belts become 4-belt desires. So I aim for 2–3× the currently needed belts as the upper margin and secure that footprint in advance. The thinking is, reserve future expansion room land-and-all upfront.

For example, if targeting through blue-purple-yellow and current need appears ~8 belts, actually prep width enough for ~16 belts, leaving a significant cushion for later. Viewing Space Age forward, you'll want room for unknown materials and specialty blocks, so margins merit being slightly wider. Early on, empty belts look wasteful, but compared to horizontal factory widening later, initial blank space is very cheap.

Before finalizing width, I lock down at minimum:

  • Target stage: red-green, blue-purple-yellow, or pre-rocket?
  • Belt color: stay yellow or transition to red midway?
  • Per-material belt count: how many iron, copper, and green-circuit belts?
  • Margin: 2× or 3× the necessary count?
  • Expansion plan: where to merge, which groups to transition to red?

💡 Tip

When the bus feels tight, shortage often splits between "insufficient belts" and "insufficient smelting." Checking furnace count and branching positions before expanding belts often fixes the jam without wider trunk.

"Main Bus Factory Design" also emphasizes initial width generous enough that later expansion becomes difficult, justifying front-loaded investment. Derive necessary volume in numbers, then layer 2–3× margin on top. This sequence lets "how many belts?" be answered from demand, not guesswork.

Small Bus

The most straightforward initial design is starting with a small bus of iron 2, copper 2, green ~1 plus 1–2 spare belts, staying smooth from red-green science through early military. I use this as the baseline for beginner guidance. The reason is straightforward: core flows are secured, width stays narrow enough that repositioning carries light burden.

This configuration's strength is speed to function. Reserving 2 iron and 2 copper belts lets early assembly machines, belts, inserters, and ammunition flow easily; dedicating 1 green-circuit belt already improves downstream visibility substantially. As noted earlier, green circuits carry heavy copper loading, so treating green circuits as an independent single belt rather than lumped "iron and copper" prevents design collapse.

Conversely, mid-game this small scale bottlenecks. Especially post-blue science, copper and circuit demand explodes. My experience confirms iron 2, copper 2, green 1 is "minimal practical setup for smooth early game," not long-term completion. However, narrow width makes fixes easy, and reconstruction cost for a thin bus is still manageable. Starting small and observing shortfall reasons while correcting teaches faster than oversizing initially.

Standard Bus

For general-purpose adoption, a ~14-belt standard bus is the most applied. Practically, a 4-belt group × 3 + 2 belt arrangement is extremely usable, and gets you comfortably to pre-rocket. Guides similarly treat this ~14-belt baseline as the design target.

At this scale, manageability as a "grouped unit" becomes important. Anchoring to 4-belt divisions makes it visually clear which groups handle iron, where copper concentrates, and where intermediate materials sit. I usually focus on iron plates, copper plates, steel, and green circuits as leads, treating the remainder as auxiliary frames. Rather than weighting everything equally, separating high-consumption trunks from auxiliary lines stabilizes operations.

The 3-vs-4-vs-6 belt distinction is more about ease of use than raw performance. 3-belt groups save space but make left/right extractions ambiguous and branching intent muddy during expansion. 4-belt groups standardize branching patterns, making underground routing mentally repeatable—most maintainable. 6-belt groups theoretically flow more but bind branching freedom and scatter "which belt serves which branch" logic.

I once tried 6-belt grouping to capture width upfront, but every branch became geometrically messy and expansion reading consumed time. Simply splitting the same belt count into 4-belt groups arranged horizontally dramatically improved maintainability. Splitting 6-belt bundles into parallel 4-belt groups proves more durable long-term than monolithic approaches.

💡 Tip

When unsure about standard-bus scaling, parallel 4-belt groups beat single large 6-belt bundles for preserving design intent across edits and preventing collapse.

Expanded Bus

For mid-to-late-game longevity, an expanded bus centered on iron 4, copper 4 becomes practical. Critically, intentionally preserve empty lanes rather than fill them. The concept is reserving space for future specialty lines or new materials, designed in from the start.

This configuration's strength is room to expand against rising demand. Anchoring iron 4 and copper 4 provides stable footing even when adding circuit-specialty blocks or steel-specialty blocks nearby, staying robust through pre-rocket. Since copper especially gets squeezed by circuit demand, treating copper 4 as the baseline works frequently. Space Age awareness similarly favors main-material thickness over trying to bus everything.

Naturally, early cost and footprint become heavier. Forming iron 4 and copper 4 early demands large smelting setup and land, making initial pacing slower than small or standard. But this weight isn't waste—it's front-paying reconstruction avoidance. I often choose expanded buses for mid-game frameworks not for "current optimality" but as "don't-dismantle-later design."

Even here, 4-belt parallel units beat 6-belt monoliths practically. Treating iron 4 and copper 4 as independent bundles clarifies red-belt timing, specialty-block insertion points, and late-game trunk retention. Centering on 6-belt groups instead makes in-group modification harder later. Expanded-bus quality hinges less on raw belt count than how gracefully future edits integrate.

Bus Cargo Selection | How to Handle Green Circuits and Copper Plates

Standard Materials for Bus Transport

Bus cargo should center on materials repeatedly consumed by multiple lines from early to mid-game: iron plates, copper plates, steel, green circuits (electronic circuits), stone brick, coal, and plastic. The bus is less a "carry-everything road" and more a shared trunk supplying widely-used materials steadily. This framing works better.

Most critical here are iron and copper. Iron's shortage is usually traceable, but copper bottlenecks sneak up. Circuits devour copper massively. My experience: iron shortages get hunted easily, but copper jams read as "circuits took it all" surprise. When deciding bus cargo, anticipate copper demand's weight before iron seems tight.

Including green circuits on the bus is tempting but requires a key caveat. For early-to-mid standard buses, it's valid. Circuits support research, module precursors, and various intermediates widely, justifying complete-product transport. However, here's the crucial prerequisite: flowing circuits works; flowing copper wire to the main bus breaks stability. The ratio shows: electronic circuits need copper wire 3-to-circuits 2. Yellow-belt circuit output demands proportionally more copper wire. That differential is why copper-wire-to-circuits becomes a specialty block while circuit-as-main-bus-product remains viable.

Stone brick, coal, and plastic aren't primary leads but still get distributed across multiple lines, so adding 1 belt each to the main bus straightens overall wiring. Brick especially is "low volume but absence halts multiple places"—high auxiliary-trunk value. Treating these as thinner than main leads but not hand-me-down operations settles things cleanly.

Materials Warranting Specialty Lines

First specialty-line candidate is electronic circuits. Green circuit distribution across multiple consumption sites plus copper-wire dependency nearly always strains copper supply if locally produced. I initially tried adjacent production near each consumer, but research and intermediate explosion caused cascading jams. Switching to a dedicated block near copper plates converting copper plate→copper wire→green circuits, returning only finished circuits to the bus transformed visibility.

Ratio logic clarifies this. Electronic circuit assembly is copper wire 3 : circuits 2. Producing one yellow-belt's circuits alone demands stronger copper-wire supply than fitting on the main trunk. Local copper-wire conversion followed by in-place circuit assembly beats distant copper-wire transport in both belt usage and guidance. Examples like "Electronic Circuit Production on Main Bus" stabilize via this approach.

Copper plates themselves warrant handling shifts as demand spikes. The base model (multi-belt distribution, bit-by-bit to consumers) works initially, but heavy-consumption lines deserve entire belt direct-feed judgment. Specialty blocks and late-game high-load lines digest cleaner fed full-width rather than fragmented shares. This isn't luxury but applying trunk lines where density is highest. Underfed hunger across many sites loses to saturation at consumption loci.

💡 Tip

When green-circuit jams hit, before adding circuit belts, check whether copper fractionation is excessive. Dedicating full copper belts to heavy-load blocks fixes faster than expanding main trunks.

note.com

Adjacent/On-Site Production Candidates and Operation Tips

Materials stable on main bus can still fare better made adjacent to consumption rather than distributed globally. Prime examples are sulfur and blue circuits. Both spike locally with clear usage zones and concentration patterns, so on-site production at heavy-demand blocks works better than mainline constant supply.

Sulfur especially ties production design to distance from petrochemical blocks. Mainline sulfur is possible but feels clunky when needed spots are limited. Making sulfur adjacent to chemical lines, using immediately, avoids bus trunk muddying and later petrochemical refactors. Treat sulfur as self-contained within chemistry clusters rather than trunk-worthy.

Blue circuits mirror this. Endgame demand density peaks, and earlier intermediates get heavily drawn, so on-site near consumption beats long-trunk distribution. By standard-bus scope, green circuits mainline while blue circuits spin separately—very stable. Space Age prospectively favors local-production weight over unification, aligning with this mindset.

Operationally, early bus-fed vs. specialty-produced boundaries prevent confusion. I split: multi-line sparse use = bus; single-block continuous heavy draw = adjacent or on-site. Circuits especially warrant specialty-line switch once visible. Pre-mainline rework is much lighter than demolition later. Main bus stability hinges less on "what's loaded" than where consumption exits the trunk.

ASCII Configuration Example

A dedicated green-circuit line cleanly extracts copper plates beside copper-wire assembly, converts immediately, and returns only finished circuits to the main bus. Words alone muddy this, so a simple layout sketch helps:

Main Bus (progresses top to bottom)
[Iron Plates]   [Copper Plates]   [Steel]   [Stone Brick]

                    │
                    │ Extract copper plates
                    v
               ┌──────────────┐
               │ Copper Wire  │
               │ Assembler    │
               └────┬─────────┘
                    │
                    v
               ┌──────────────┐   Iron Plates
               │ Green Circuit│ ◄─── Branch-in
               │ Assembly     │
               └────┬─────────┘
                    │
                    │ Return only finished circuits
                    v
[Iron Plates]   [Copper Plates]   [Green Circuits]   [Steel]   [Stone Brick]

This form's advantage: the copper-plate-to-circuit flow is short, thick, and readable. Skipping long copper-wire transport makes shortfall tracking easy. In my experience, distributed green-circuit production across sites left me confused whether copper or circuits bottlenecked. Consolidated specialty-line design lets "copper input" and "product output" metrics diagnose state simply.

This layout's value scales with copper intensity. As specialty blocks demand more, swapping fractional distribution for full dedicated copper-belt supply eases expansion further. The main bus isn't an equality distributor but a backbone routing necessary trunks to necessary destinations. Circuits showcase this principle most clearly.

Common Failures and Solutions | Insufficient Width, Starved Tails, Terrain Collisions

Width Shortage Recovery and

The main bus's most common mistake is tightening width from early-game budgeting instinct. Fresh factories run on iron 2, copper 2 sizing, tempting tight sideways assembly. But compact placement blocks later steel or circuit additions. Single-side assembly gets strained; double-side becomes immovable. My personal experience: "space-wasting gaps felt bad early until late-game reconstruction felt terrible."

Counter-strategy: simple. Reserve future width and footprint from the start. Main buses are cheaper widened early than reconstructed late. 4-belt grouping bases allocation on needed counts, explicitly holding spare group-slots unfilled. Standard-bus sense: preserve room for near-future material or line independence beyond immediate necessity. Space-Age perspective extends this—space margins matter more than unknowns.

Post-shortage salvation exists. Largest relief: disconnect heavy-consumption lines from bus dependency. Green-circuit and copper-heavy blocks becoming specialty production dramatically reduces main-trunk pressure. "Expand trunk" temptation fades if "exit-bus" alternate exists. Width shortage roots often in trying trunk-fed everything rather than branching heavy loads away. When pressure mounts, offload-to-specialty frequently beats widen-the-trunk.

Overlooked: smelting capacity before belt expansion. Wanting extra iron-plate belts means wanting extra furnace trains, not just trunk width. Yellow-belt capacity runs 48 stone furnaces; red-belt asks 96 stone or 48 steel. Expanding plates without furnace scaling leaves visual-only belt growth.

💡 Tip

When belts feel tight, before widening, confirm: 1) smelting adequacy, 2) fractionation patterns, 3) demand concentration. Often fixing just these three eliminates expansion need.

Mid-game red-belt adoption similarly requires production shift. Steel furnaces (24 per red belt) replace stone models (48 per yellow). Misaligning belt color with smelting type leaves buffered-but-hungry supplies.

Starved-Tail Remedies and Root-Cause Logic

Busses starving only at their far ends usually trace to over-fractionated branching. Early-game small splits seem acceptable; post-blue-science demand spikes hit differently. Tiny draws across many mid-line branches gradually deplete tail reach. Visually, trunk flows while tail terminals choke—baffling for newcomers.

Solutions split into direction. Outer-priority branching (covered earlier) and mid-trunk merging stabilize tail supply. Treating distribution as uniform-feed fails; priority reserves for downstream, overflow to others works better. Divider priorities operationalize this where available. Mentally separating "must-feed" belts from "nice-to-feed" belts dramatically sharpens behavior reading.

Heavy-consumption specialization also combats tail starvation. Rather than asking "add more trunk belts," ask "exit heavy drains early." Green-circuits and copper-draw lines converted to specialty-adjacent production drop demand pressure mid-trunk, letting remainder reach tail robustly. Fine fractionation accumulates unseen bottlenecks; obvious exit strategically placed dissolves them.

Personal example: my tail green-circuit assembly alone starved while trunk belts flowed—mysterious. Tracing revealed: mid-line copper and green pulls by assorted blocks created compound shortage. Rebalancing mid-fractionation externally, adding mid-merges for depleted lanes solved the "tail mystery." Bus tails stagnate from distribution weight misalignment, not endpoint machine failure. Diagnosing and re-siting heavy draws fixes faster than trunk expansion.

💡 Tip

Starved bus tails: check "where splits happen" before checking "is tail machinery OK?" Moving heavy drains to off-trunk production, adding mid-merges for deprived lanes fixes tail stability without wholesale widening.

Terrain Collision and Pragmatic Handling

Main buses emphasize straightness; cliffs, lakes, and oceans shatter this elegance. Curves scatter branching baselines; assembly distance deviates. Narrow-start factories losing both expansion

How Does Space Age Change Things? How Far to Take the Main Bus

Main Bus Remains Effective in Early Nauvis

Space Age was released on 2024-10-21, but when it comes to bootstrapping early Nauvis, the Main Bus remains just as effective. As outlined on the Factorio Wiki Space Age page and the Steam Factorio: Space Age page, the DLC expanded the game's scope significantly, but the core flow of laying out iron plates, copper plates, steel, and circuits in a visible main line to progressively unlock research and intermediate products hasn't changed.

This becomes clear when you think about design flow. In early Nauvis, what matters more than the variety of materials needed is being able to see where everything comes from. The Main Bus makes supply relationships easy to trace just by lining up key resources on a trunk line, and bottlenecks are visually trackable. Even on a first Space Age playthrough, this advantage carries over directly during the bootstrap phase. On my first DLC run, I found that laying down a conventional bus on Nauvis first created better research tempo than jumping straight into specialized logistics.

Especially in the early game, ease of modification is more valuable than raw throughput. With a Main Bus, inserting new intermediate products needed for research, expanding existing lines, or just fattening up plate supply upstream are all straightforward modifications. With Space Age adding more complexity ahead, keeping a manageable backbone at the starting point helps prevent design decisions from wobbling.

Space Age/ja wiki.factorio.com

Late Game: Combine with Bot Logistics and Per-Planet Production

The bigger changes come later. In Space Age, production doesn't stay contained on Nauvis -- per-planet role specialization and robot logistics become deeply intertwined with factory design. If you keep the old mindset of "just add everything new to the Main Bus," the trunk line grows wider while management actually gets worse.

Even in vanilla v2.0, dedicated lines were effective late-game, but this trend is even stronger in Space Age. The reason is simple: the logistics center is no longer monolithic. Materials handled on Nauvis's shared trunk versus materials better kept within a specific planet or block separate naturally. The winning approach is "don't put everything on the bus; only put what belongs on the bus."

In my experience, the Space Age Main Bus works better as a backbone for stabilizing early-to-mid Nauvis rather than "the spine of the entire factory." Then, as the endgame approaches, feed high-consumption blocks and specialty materials through bot logistics or close production loops per planet. This separation lets you keep the trunk line clear while scaling up overall. Conversely, trying to unify everything invites rework every time a new material is added.

💡 Tip

In Space Age, thinking "limit the Main Bus's scope early" rather than "abandon the Main Bus" leads to more stable designs. Nauvis common materials go on the bus; heavy individual demands go on dedicated lines or bot logistics. That's the most manageable configuration.

Practical Example: Taking Extra Width and Spacing

What really helped on my first Space Age run wasn't predicting exact material names but creating room for unknown materials upfront. In a DLC with new elements, it's safer to start with multiple empty lanes rather than locking down exact lane counts from the beginning. As mentioned earlier, Main Bus width is expensive to add later, so building slack into the initial groundwork and skeleton is highly valuable. It's similar to buying expansion land before you need it.

For a concrete example, a first Space Age run works well with roughly 4 iron, 4 copper, 2 green circuits, 2 steel, 1 stone, 1 stone brick, 1 coal, 2 plastic as a baseline, with generous spacing between groups. This isn't a final form but a "slack-included design" that assumes you'll insert lanes later. It's a bit wider than the standard ~14-lane thinking, and leaving open space especially around iron and copper makes it easier to accommodate unknown intermediate products or dedicated supply lines.

On my first DLC run, I deliberately left several empty lanes. When new materials or lines I wanted to split off appeared, I could accommodate them without tearing apart existing blocks. This difference is huge -- without slack, every "add a new material" event triggers line relocation, but with slack, it's just adding a connection. Practical runs like the publicly shared "Factorio Space Age Express Route #2" also show that slack-friendly designs mesh well during first playthroughs.

Not just width but generous group spacing is also crucial. Even with enough lane count, if spacing is too tight, you can't insert branches or merges later. Space Age frequently creates "things I want to add afterward," so usability depends more on "what can I insert next to these belts" than belt count alone. Rather than optimizing for space from the start, building early Nauvis foundations wide, straightforward, and with slack is distinctively the strongest approach in the post-2024 context.

note.com

Summary: When in Doubt, Start with These Lane Counts

Start small, and when you see where things bottleneck, scale up -- that's plenty. If it were me, I'd bootstrap with a minimal temporary bus to push through early research, then redesign properly after logistics unlocks. When expanding, rather than adding everything to the trunk, strengthening plate supply first and splitting heavy intermediate products into dedicated lines tends to scale better and ultimately improves efficiency. When in doubt, follow this sequence: "bootstrap with a temporary bus, upgrade to a proper design, then spin off high-consumption products.

Share this article

T

Takuma

Over 3,000 hours in Factorio. A production line design specialist who has achieved 1k SPM megabases in multiple configurations, applying his professional plant engineering expertise to factory optimization.