Back to tools

Minecraft TPS & Lag Monitor

Paste your /tps, /mspt, timings or spark output and find out exactly what is slowing your server down, with plain-language fixes ranked by impact.

Input

Paste your server output

A bare /tps line is enough. Colour codes and console timestamps can stay in the paste — they are stripped for you.

Nothing leaves your browser. Everything is parsed locally.

Ctrl + Enter also runs the analysis.

What TPS means

Reading the number

  • 20 TPS the server finishes every tick with time to spare. Perfect.
  • 19.5 to 20 fine. Normal wobble, nobody feels it.
  • 15 to 19.5 noticeable. Mobs stutter, hits feel late, redstone drifts.
  • Below 15 severe. The world visibly runs in slow motion.

MSPT is the other half of the story: one tick has a 50 ms budget. Above 50 ms the server cannot finish a tick in time and TPS starts falling.

Live monitoring is coming later. This version is paste-only and never connects to anything. Auto-polling over RCON is planned for a later release.

Results

Paste something on the left, or use one of the sample buttons, and the breakdown appears here.

How to get the numbers

Commands worth running before you paste

/tps every Spigot, Paper and Purpur server. Gives the 1m/5m/15m averages. This alone is enough for a useful reading.

/mspt Paper and forks. Milliseconds per tick, which shows a problem earlier than TPS does.

/spark health or /spark profiler, paste the text output. Not the link: this tool never fetches a report URL.

/timings report paste the text you can copy out of the report. The percentage column is what gets ranked.

Running your own game server?

Wespner game servers with DDoS protection, NVMe drives and activation within minutes.

Browse hosting