Game Server Bandwidth Planning: Per-Player Bitrates, Transfers and Port Sizing

Bandwidth arguments on game hosting forums usually start with a provider quoting 10 Gbps and end with an admin paying for capacity they never touch. Game traffic is small in volume but sensitive in timing: a 64-player shooter might move 40 GB in a month while still needing low jitter on every packet. Port speed, monthly transfer, and per-player bitrate are three separate numbers and conflating them is where budgets go wrong.

Port speed is not the same as data transfer

Port speed caps the instantaneous rate bytes can leave your NIC, measured in megabits per second. Transfer is the cumulative volume over a billing period, usually in terabytes. A 1 Gbps port left saturated for a full month would move about 324 TB, which is far beyond what any game server generates.

Hosts quote both because they bill on both. You can have a 10 Gbps port and a 20 TB monthly cap, or a 1 Gbps port with unmetered transfer. Game servers almost never need the first number and frequently need certainty about the second, especially during mod-pack downloads and update pushes.

Measured bitrate per player, by game type

Per-player bitrate is the useful planning figure. A competitive shooter sends and receives roughly 30 to 60 kbps per player in each direction, so 64 players cost about 4 Mbps up and 4 Mbps down. Survival games with heavy world state, such as ARK or Valheim, run 80 to 150 kbps per player.

MMO-style servers with many entities visible at once push 150 to 250 kbps per player. Voice chat, if hosted on the same machine, adds 40 to 64 kbps per speaking participant. Add those figures and you get a realistic peak, which is typically two to four times lower than the port most admins rent.

Turning per-player figures into a monthly transfer budget

Multiply peak per-player bitrate by your average concurrent players, then by the hours the server runs. A 40-player Valheim server at 120 kbps per player, in and out, with 15 average concurrent during an eight-hour evening window, moves roughly 1.3 GB per evening or about 40 GB per month. Add mod and update distribution and you may double it.

The dominant transfer cost is usually not gameplay but content delivery: Steam workshop sync, mod-pack downloads, and map files served to joining players. A single 3 GB mod pack pushed to 200 unique joiners is 600 GB in one week. Plan transfer around downloads, then add gameplay traffic on top.

Burst, jitter and why port headroom still matters

Even with low average usage, every player joining a map triggers a burst of state transfer that can briefly exceed normal rate by tenfold. If the port is already near saturation from other tenants or from your own backups, those bursts queue and the joining player stalls at the loading screen while everyone else sees tick warnings.

Keep sustained utilisation below 30 percent of port speed so bursts fit without queuing. On a 1 Gbps port that means staying under 300 Mbps, which is generous for any single game server. If you consistently exceed it, your problem is a download bottleneck or a DDoS event, not insufficient port size.

Choosing between metered and unmetered plans

Metered plans are cheaper per month and fine when your traffic is predictable and low. Unmetered plans cost more but remove the risk of an overage invoice after a viral server launch or a mod-pack push. Many hosts throttle rather than bill overages, which is worse: the throttle hits exactly when your player count spikes.

Read the fair-use clause on unmetered offers, because most cap at a port speed and some count only outbound traffic. Our game hosting breakdown lists which plans meter outbound versus total volume, which is the distinction that decides whether a launch week costs you money.

Monitoring the numbers that predict trouble

Track four counters hourly: outbound bits per second, inbound bits per second, packet retransmits, and the 95th percentile rather than the average. Retransmits climbing while throughput is flat means packet loss on the upstream path, which no amount of extra port capacity fixes. The 95th percentile is what most providers bill against.

Set alerts at 60 percent of your committed rate and at 0.1 percent retransmit. Graph per-player bitrate alongside player count so you can see whether a client patch changed the protocol’s traffic shape. A sudden 40 percent rise after a game update is common and worth raising with the host.

Traffic management that reduces the bill

Serve mod packs and map files from a separate web host or object store rather than the game server itself, and enable compression on those downloads. Rate-limit simultaneous joins so the state transfer burst stays inside your port headroom. Cap voice chat codec bitrate and move it to a separate small instance if it becomes a large share of traffic.

Schedule backups during low-population hours and send them to remote storage over the same link only if you have measured headroom; otherwise snapshot locally and copy on a weekly schedule. For a full picture of hardware and network pairings across game types, check our dedicated server comparison table.

Plan for the download burst, not the average tick, and rent port size for the 95th percentile with 30 percent headroom. A 1 Gbps port with sane traffic management carries almost any single game community, and the money saved belongs in CPU clock speed.

Leave a Reply