Factorio Megabase Server Specs 2026: 1k+ SPM, UPS Limits, Real Numbers

If you’ve ever watched your Factorio save chew through update ticks until the game starts stuttering, you’ve met the real cost of scale. A Factorio server doesn’t slow down when bullets fly or bases burn. It slows down because the simulation has to step every belt segment, every assembler, every inserter, every train, sixty times per second, no matter who’s logged in. Cross 1,000 science per minute and that simulation cost becomes the single thing that decides whether the server feels good or feels broken.

This is the guide we wished existed when our customers started shipping megabases. The numbers below are calibrated against real hosted servers, not synthetic benchmarks. If you’re planning a base that pushes past a thousand science per minute, you’ll want to read this before you pick a host or order a box.

What actually slows a Factorio server down

Factorio’s headless server runs the world simulation on a single core. There is no automatic parallelism across belts, trains, or biters. Every tick, the same core walks through every entity in the game and recalculates state. On modern hardware this looks effortless for the first hundred hours. It stops looking effortless somewhere around the megabase threshold, which is loosely defined as a base producing 1,000+ science per minute (SPM) sustained.

The metric that matters is updates per second, or UPS. The server aims for 60 UPS. If a tick takes longer than 16.67 milliseconds to compute, the server drops below 60 and the world starts running in slow motion. Belts move slower. Trains take longer. Biters reach you later. Combat, transport, and production all decouple from real time. Players notice immediately.

Three things drive a server toward sub-60 UPS faster than anything else:

• Entity count and density. Every belt segment, inserter, machine, lamp, and pipe consumes a slice of tick budget. Sparse bases stay cheap. Dense bases get expensive.
• Active fluid networks. Pipes and pumps are notoriously expensive to simulate because each network resolves every tick. Long oil and lubricant runs are common UPS killers.
• Train pathfinding. A train recalculating its route is much more expensive than a train cruising on a known path. Big rail networks with many simultaneously-pathing trains create UPS spikes.

Mods compound all three. Krastorio 2, Space Exploration, and Pyanodon mods routinely cost more UPS per entity than vanilla. A modded server hits the UPS ceiling at a lower SPM than a vanilla one.

CPU: the real bottleneck

Because Factorio’s main thread is single-core bound, raw clock speed and instruction-per-cycle performance matter far more than core count. A modern desktop CPU with high single-core performance (Intel 13th/14th gen i5 or i7, AMD Ryzen 7 7700X, Ryzen 9 7950X) will hold 60 UPS on much larger bases than a server-class chip with 32 cores at lower clocks.

What to look for when picking a host or building a box:

• High single-thread Geekbench / Cinebench R23 single score. Above 2,000 Cinebench R23 single is comfortable for big bases. Above 2,200 is comfortable for serious megabases.
• Sustained boost clock, not just peak. Many “fast” CPUs only hit peak boost for a few seconds. Factorio runs for hours. Servers that throttle under continuous load lose UPS continuously.
• Disabled hyperthreading on the server thread, if you can. Counterintuitive, but Factorio occasionally benefits from running on a clean physical core without the SMT sibling stealing pipeline resources. Most managed hosts don’t expose this, which is fine; the difference is single-digit percent.

Avoid older server hardware no matter how many cores it claims. A 32-core Xeon E5-2680 v4 from 2016 looks impressive on paper. It will run a vanilla megabase at 40 UPS while a single Ryzen 7700X chip at twice the clock runs it at 60.

RAM: enough for the save, headroom for autosaves

Factorio is famously light on RAM compared to its sibling games. A vanilla 1,000 SPM base typically uses 4 to 8 GB of process memory. Heavy mod packs push that toward 12 to 16 GB.

The sneaky overhead is autosaves. The server forks the process to write an autosave without freezing gameplay, which briefly doubles memory residency. If you’re sized at 8 GB and you forked during an autosave, the kernel needs 16 GB available or it starts swapping. Swap on a Factorio server destroys UPS for as long as the autosave takes.

Practical sizing:

• Up to 1k SPM vanilla: 8 GB total, 4 GB free for the autosave fork
• 1k to 3k SPM vanilla or moderately modded: 16 GB total
• 3k+ SPM or heavy mod packs (Space Exploration, Pyanodon): 32 GB minimum

Network: surprisingly forgiving

Factorio’s multiplayer protocol is tick-locked, which means the server only has to push small state deltas to each client. Bandwidth requirements per player are modest. A megabase server with eight active players rarely exceeds 1 Mbit/s sustained upload.

What matters more is latency and packet loss. Factorio’s lockstep model means a single dropped packet from one player stalls the whole simulation until that player catches up. A server with intermittent network issues feels broken even when CPU and RAM are fine. Pick a host with low jitter to your region. Don’t host a European megabase from a US datacenter if you can avoid it.

Disk: it’s all about autosaves

The save file for a megabase grows surprisingly large. A 1,000 SPM vanilla save can hit 200 MB. A 3,000 SPM Space Exploration save can hit 1 GB. The server writes the full save every autosave interval, plus a rolling backup count.

Two recommendations:

• SSD only. Spinning disks will turn the autosave pause from “barely noticeable” into “the whole server stalls for 15 seconds while we wait for the rotational write”.
• Set autosave interval based on player tolerance. The default 5 minutes is generous. On a megabase, every autosave costs a tiny but real UPS dip. If your group is okay with re-doing 10 minutes of work after a crash, double the interval and you’ll feel the smoother gameplay.

Recommended specs by tier

These are honest tiers calibrated against real Factorio servers we host, not generic “good enough” recommendations.

• Casual co-op, up to 300 SPM, 2-6 players, vanilla: Any modern 4-core CPU with strong single-thread, 4 GB RAM, SSD. Even an entry-level VPS works.
• Serious bases, 300 to 1,000 SPM, 4-10 players, light mods: Modern 6-core consumer CPU (Ryzen 5 7600, i5-13600), 8 GB RAM, NVMe SSD.
• Megabase, 1,000 to 3,000 SPM, 4-12 players, vanilla or moderate mods: 8-core high-clock CPU (Ryzen 7 7700X, i7-13700K), 16 GB RAM, NVMe SSD, low-jitter connection.
• Extreme, 3,000+ SPM, modded, ambitious: Top-tier consumer CPU (Ryzen 9 7950X3D, i9-14900K), 32 GB RAM, NVMe, expect to accept lower UPS at some point.

When you outgrow a single server

Eventually every megabase hits a ceiling that no hardware fixes. Vanilla Factorio has a hard limit somewhere around 10,000 SPM where even the fastest single-core CPU can’t sustain 60 UPS. At that point you have three realistic options.

First, accept lower UPS. Many of the largest community megabases run happily at 40 to 50 UPS. The game still works. Belts just move a bit slower. If everyone is on the same server they’re all running at the same simulation rate so nothing feels broken, only stretched.

Second, redesign for UPS efficiency. The community has documented patterns that trade aesthetics for tick cost. Tile-able beacon-heavy designs are usually cheaper than sprawling spaghetti at the same throughput. Direct-insertion chains can be cheaper than belt chains. The book-length wiki article “Optimization” is worth a careful read.

Third, move to a smaller scope. Some groups run “tournament” servers that reset every few months. The base never has time to outgrow the hardware. The competitive structure ends up more fun than the megabase grind anyway, for a lot of players.

How much does a Factorio server cost?

The honest answer is that hosting costs are dominated by CPU class, not by Factorio’s appetite. A casual 4-player server costs the same as any small VPS, typically $5 to $8 per month. A megabase server on a high-clock dedicated core costs more, usually $10 to $20 per month from a managed host that gives you the kind of CPU performance the game needs.

Self-hosting a megabase on your home PC is technically possible but practically painful. Your home internet is usually higher-latency and less stable than a datacenter connection, and you can’t keep your gaming rig running 24/7 without burning electricity and wear. Most groups that try self-hosting move to a managed host within a few months.

If you’re sizing for a megabase and want a host that actually understands Factorio’s CPU requirements, our managed Factorio hosting runs on high-clock modern CPUs with NVMe SSD and gives you a panel for save management and mod handling. Save uploads, mod installs, and config changes happen in the panel, not over SSH.

Bottom line

Megabase Factorio is the rare game where CPU clock speed is the only thing that matters and core count is almost irrelevant. Pick a host whose CPU is fast on a single thread, give the server enough RAM that autosaves don’t push it into swap, put the world on an SSD, and you’ll spend more time growing your base than fighting your hosting.

For the next step up, we’re building a Factorio production ratio calculator that will help you size belts and inserters before you commit them to the build. Once it’s live we’ll cross-link it from this article.