What is TPS and MSPT — and how to check what your host really gives you

If you run a Minecraft server and only ever look at one chart, don't make it CPU percentage or RAM usage. Make it TPS — and its sharper sibling, MSPT. These two numbers are how your server feels to play.

TPS: the server's heartbeat

Minecraft simulates the world in ticks. Each tick advances everything one step: mobs move, water flows, redstone fires, crops grow. The game is designed to run 20 ticks per second — one every 50 milliseconds.

TPS (ticks per second) is the actual rate your server achieves.

• 20.0 — perfect. The world runs at real-time speed.
• 19.x — fine; brief dips happen (chunk generation, a big explosion).
• 15–18 — noticeable. The world runs 10–25% slower than real time: mobs stutter, item pickups delay, machines fall behind.
• Below 15 — painful. Combat, redstone timing, and farms all visibly break down.

An important detail: TPS can't go above 20. A server showing 20.0 might be cruising with headroom — or might be one creeper away from dropping. TPS tells you that you're keeping up, not how close to the edge you are. For that, you need MSPT.

MSPT: the budget behind the heartbeat

MSPT (milliseconds per tick) is how long each tick actually takes to compute. The budget is 50ms:

• MSPT > 50 → ticks take longer than the budget → TPS falls below 20.
• MSPT well under 50 → real headroom. A server at 10 MSPT is using a fifth of its budget.

This is why MSPT is the better early-warning signal — and why a server at 45 MSPT is running at the edge: one more farm, one more player, one busy neighbor on an oversold node, and it tips over.

But read that arrow in one direction only. MSPT measures the length of a tick, not the period of the loop. Work happens between ticks too, and a fixed-rate loop banks no credit: a tick that finishes 3 ms early does not pay for a tick that overruns by 50. So a mean comfortably inside the budget does not prove the server hit 20 TPS.

We have our own measurement of that gap. In July 2026 a customer's Fabric 1.21.11 server reported an average of 48.9 ms per tick — inside the budget, with the core itself saying "running normally" — while its world tick counter advanced 352 ticks in 20.064 seconds: 17.55 TPS. Its p95 was 51.7 ms and its p99 55.4 ms; the players felt it and the average didn't show it. That is why our panel now counts the world's own tick counter for the rate, and shows the p95 tail next to the mean, instead of inferring one number from the other.

Two servers can both display "20 TPS" and be in completely different shape. MSPT, its tail, and where the TPS number actually came from are the difference.

How to check on your own server

On Paper or Purpur (which most serious servers run):

• /tps — TPS averages over the last 1, 5, and 15 minutes.
• /mspt — recent tick durations (on Paper this prints average/min/max, not percentiles).
• tick query — from Minecraft 1.20.3, vanilla's own report: mean tick time, P50/P95/P99, and whether the game thinks it's keeping up.
• time query gametime twice, a measured interval apart — the ground truth. Divide the difference in ticks by the seconds you waited and you have the rate the world actually delivered, independent of any average.
• For deep dives, Spark profiles exactly what inside the tick is slow — entities, redstone, a specific chunk, a misbehaving plugin.

Run these at a quiet hour and again at prime time. The delta between those two readings tells you more about your hosting than any sales page.

Why tick metrics are still rare on hosting dashboards

CPU% and RAM graphs are easy to provide and easy to look good on. TPS and MSPT are different: they expose contention — what happens when an oversold node hits peak hours and your server stops getting the CPU time it needs. A node-level dashboard can look healthy while every server on it ticks at 14 TPS.

To be fair, this is improving — Exaroton shows live TPS in its own panel, and Aternos exposes spark-based tick data, and credit to them for it. But the incentive is worth understanding: the metrics that matter most to you are exactly the ones that would embarrass an oversold host. That's not a conspiracy, just an incentive — and it's why a beautiful panel with no tick metrics on it should make you curious.

What to demand from any host (including us)

1. Live TPS and MSPT for your server, on screen — on Paper, Purpur, Forge and NeoForge, and on Vanilla and Fabric from Minecraft 1.20.3, not on request, not via a support ticket.
2. A straight answer to where the TPS number comes from. A rate counted off the world's tick counter is a measurement. A rate inferred from average tick time is an estimate — and, as above, the two disagree exactly when it matters.
3. A straight answer to "how many servers share a core at peak?"
4. An at-capacity policy — what happens when the node is full? The real answer is "we stop adding servers," not "it's fine."

If a host can't or won't show you tick metrics, ask why — and don't accept a CPU% graph as a substitute. It's your world and your evenings — you're allowed to see the heartbeat.