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 → the server keeps up → TPS stays at 20.
• MSPT > 50 → ticks take longer than the budget → TPS falls below 20.

This is why MSPT is the better early-warning signal. A server at 10 MSPT is using a fifth of its budget — tons of headroom. A server at 45 MSPT still shows a flawless 20 TPS, but it's running at the edge: one more farm, one more player, one busy neighbor on an oversold node, and it tips over.

Two servers can both display "20 TPS" and be in completely different shape. MSPT is 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 (average and percentiles).
• 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, not on request, not via a support ticket.
2. A straight answer to "how many servers share a core at peak?"
3. 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.