Minecraft TPS Calculator
Calculate your server's TPS (Ticks Per Second) from the average tick time in milliseconds. See color-coded performance status and a full MSPT reference table.
MSPT to TPS Reference Table
| MSPT | TPS | Status |
|---|---|---|
| 10 ms | 20.00 | Excellent |
| 20 ms | 20.00 | Excellent |
| 30 ms | 20.00 | Good |
| 40 ms | 20.00 | Good |
| 50 ms | 20.00 | Perfect max |
| 55 ms | 18.18 | Slight lag |
| 60 ms | 16.67 | Moderate lag |
| 75 ms | 13.33 | Severe lag |
| 100 ms | 10.00 | Heavy lag |
| 200 ms | 5.00 | Unplayable |
Embed This Tool
Put the tick rate monitor on your own site or server wiki.
<iframe src="https://tools.astroworldmc.com/embed/tick-rate-monitor" width="700" height="550" frameborder="0" style="border:none;border-radius:12px;" loading="lazy" title="TPS Calculator"></iframe>
How to read MSPT and TPS
Take the tick time
Read the average MSPT from the tps command, from spark or from timings, and put that number in the field.
Read the tick rate
Under fifty milliseconds the server still runs twenty ticks a second. Above it, the rate is a thousand divided by your tick time.
Use the headroom
The capacity figure says how much of a tick is still free, which is what decides whether another farm or another plugin fits.
Compare in the table
The reference table lines tick times up against tick rates and the verdict that goes with each one.
How It Works
Understand and calculate TPS and tick timing.
One division on the 50 millisecond tick budgetPage updated
What Is TPS in Minecraft?
TPS stands for Ticks Per Second and measures how fast your Minecraft server processes game logic. The server targets 20 ticks per second, meaning each tick should complete within 50 milliseconds. When the average tick time (MSPT) exceeds 50ms, the server cannot maintain 20 TPS and begins to lag. Players experience slower block breaking, delayed mob movements, and rubber-banding when TPS drops.
MSPT (Milliseconds Per Tick) is the inverse measurement. It tells you how long each tick actually takes to process. The formula is simple: TPS = min(20, 1000 / MSPT). As long as MSPT stays at or below 50ms, TPS stays at a perfect 20. Once MSPT climbs above 50ms, TPS begins to fall proportionally. When MSPT sits above 50 because the garbage collector has no room to work, more memory is the cheaper fix than fewer players: the RAM calculator gives the allocation and the startup flags.
How to Check Your Server's MSPT
On Paper and Spigot servers, use the /tps command in-game to see the TPS over the last 1, 5, and 15 minutes. For MSPT specifically, Paper servers support the /mspt command which shows average and maximum tick times. Vanilla servers display tick time in the F3 debug screen (Java Edition) or through the /debug command.
Server monitoring tools like Spark provide detailed profiling data including per-tick timing breakdowns. Use these tools to identify what is causing high MSPT: entity processing, chunk loading, redstone calculations, or plugin overhead. Addressing the root cause is more effective than simply reducing view distance or entity limits.
The color coding in this calculator matches the standard used by most server communities: green (19+ TPS) means healthy, yellow (15-19 TPS) means noticeable lag, and red (below 15 TPS) means severe performance issues that need immediate attention. A server that sits under 20 usually carries more players than its hardware wants, and the player slot advisor puts a number on that, while view-distance and simulation-distance, the two settings that move TPS most, are in the server.properties generator.
The tick budget
| Target | 20 ticks per second, which gives each tick exactly 50 milliseconds to finish in. |
|---|---|
| MSPT | How long one tick actually took. Under 50 the server waits out the rest of the tick, over 50 it falls behind and TPS drops. |
| Ceiling | TPS never reads above 20 on its own. A server that finishes a tick in 10 ms is not running at 100 TPS, it is idle for 40 ms. |
| Since 1.20.3 | The tick command can query the rate, freeze the world and step it by hand, which makes it possible to run above 20 on purpose. |
| Redstone | One repeater tick is two game ticks, so 0.1 seconds. Every redstone timing derives from the same 50 ms unit. |
| A day | 24000 ticks, which is 20 real minutes at full speed. A server at 10 TPS makes a Minecraft day take 40. |
One fixed number carries this page: a server aims at 20 ticks per second, which leaves 50 milliseconds for a tick. The TPS, the share of the budget used and the delay per hour are that single division worked out on whatever value you type.
One division, and the three things it decides
The whole page is 1000 divided by your millisecond figure, capped at 20. What makes it worth reading is the second step: turn the same number into a share of the budget and into the minutes a Minecraft day now takes.
TPS = min(20, 1000 / MSPT)share of the budget = MSPT / 50a day is 24000 ticks, so its length in minutes = 24000 / TPS / 60an hour of ticks in real time = 60 x 20 / TPS minutesThe gap between 45 and 55 MSPT is ten milliseconds and the difference between a healthy server and a visibly slow one. Above 50 nothing is cushioned any more: every extra millisecond lands directly on furnaces, crops, hoppers and mob timers, and a day that runs long is the first thing players notice.
Frequently Asked Questions
Questions about TPS
TPS or MSPT, which should I watch?
MSPT. It is the cause and TPS is the symptom. A server at 45 MSPT is healthy with almost no margin left, and you would rather see that coming than wait for TPS to finally slip below 20.
Can TPS go above 20?
Not by itself. The server sleeps out any time it did not use, so 20 is the ceiling. Since 1.20.3 an operator can raise the target rate with the tick command, which is a deliberate change and not a performance win.
TPS is 20 but the game still feels laggy. Why?
Because that number only measures the server. Client frame rate, a slow connection and chunk loading all produce the same feeling while the server sits comfortably inside its 50 ms.
What eats the tick budget fastest?
Entities that all need updating, hoppers checking their contents every tick, and chunks being generated on demand. All three scale with what players build, which is why MSPT climbs slowly over months rather than all at once.
