piapia123
en

Satisfactory Conveyor Throughput

Games

Everything runs locally in your browser — nothing is uploaded

Input
Drop a file here to load its contents
Output

From the belt tier (Mk.1 at 60/min through Mk.6 at 1200/min), the machine count and the output per machine, work out total throughput, belts needed, belt utilisation and the bottleneck. Two things to hold on to: the unit is items per minute, not per second; and while parallel belts add up, a split point still chokes a single belt — one machine feeding a Mk.1 belt makes that belt the bottleneck no matter how many you merge downstream.

Features

  • Belt tiers Mk.1 60 through Mk.6 1200 (per min)
  • Machines × output per machine = total production
  • Belts needed (rounded up)
  • Belt utilisation and where the bottleneck is
  • An optional sorter tier (Mk.1 60, Mk.2 120 and so on)
  • Parallel belts add their capacity together

How to use

  1. Pick the belt tier and the sorter tier
  2. Fill in machines, output per machine and belt count
  3. Or write one machine count per line to run separate cases
  4. Read the bottleneck row to decide what to upgrade

FAQ

Is the rate per minute or per second?
Per minute (items/min). Mk.1 is 60/min — one per second — and Mk.5 is 780/min. Reading it as per second shrinks demand sixtyfold, and both 60 and 1 look plausible, so nothing jumps out.
Do parallel belts guarantee the throughput?
Not always. Parallel belts add up (`belts × rate per belt`), but what actually chokes production is a split point: if one machine feeds a low-tier belt, that belt is the bottleneck and merging more belts downstream does not help. So the result gives both the total and the bottleneck.
Where does the sorter fit?
The sorter (at the tier you choose) sits in series with the belts, so the effective throughput is the minimum of three: machine output, total belt capacity and sorter capacity. A sorter below the belt tier becomes the bottleneck.

Related tools