TPS, ticks per second, is the most commonly cited Minecraft server performance number, and for good reason: it is easy to check and roughly tells you whether the server is keeping up. It is also, on its own, a slightly incomplete picture, which is worth understanding before you chase the number blindly.
What TPS actually measures
Minecraft's server runs on a fixed tick rate: 20 ticks per second, each with a 50-millisecond budget. TPS measures how many of those ticks the server is actually completing per second in practice. 20.0 is perfect. Anything meaningfully below that means the server cannot finish a tick's worth of work within its 50ms window and has to fall behind.
How to check it
On Paper and most forks, run:
/tps
This shows rolling averages over the last 1, 5, and 15 minutes. A healthy server sits at or very close to 20.0 across all three. For a more detailed breakdown, spark's /spark tps command gives additional context alongside the raw number.
Why TPS alone can be misleading
TPS is a derived, somewhat coarse metric, and on some setups it can read close to 20 even when individual ticks are taking meaningfully longer than 50ms, particularly with certain TPS-limiting configurations. This is exactly why MSPT (milliseconds per tick) is often the more trustworthy number for serious diagnosis, it measures tick duration directly rather than a rolling average that can mask spikes. We cover this in detail in our high MSPT guide.
What actually causes low TPS
In rough order of how often each is the culprit:
- Too many active entities (mobs, item drops, minecarts), see entity lag.
- View-distance or simulation-distance set too high, see chunk lag.
- A poorly optimized plugin or mod, best found with spark's profiler.
- Garbage collection pauses, see GC lag.
- The server itself being undersized for its player count and world size.
Using TPS as a health check, not a diagnosis
Treat /tps as your first-glance indicator, is something wrong, not your full investigation. Once it confirms a problem, move to spark profiling or MSPT to find the actual cause rather than guessing from the TPS number alone. Our full lag-fixing guide covers the fixes once you know what you are dealing with.
Getting headroom before it becomes a problem
A RAM calculator can confirm whether your plan matches your actual needs before TPS starts dropping under normal load. Tick Hosting's plans give you that headroom, starting with a free tier, from Tick Hosting's plans page.