How the server health score works
What the 0 to 100 health score measures, how it's calculated from average TPS and uptime, and how to interpret it.
Updated 7 June 2026
The server health score is a single number between 0 and 100 that summarises how well your server has been performing over the time range you're viewing. It appears at the top of your analytics dashboard whenever plugin TPS data is available.
What it measures
The score combines two inputs, weighted by how directly each one affects the player experience:
- Average TPS, weighted at 70%: your average ticks per second over the selected range, measured against the ideal of 20. TPS is the most direct measure of whether the game feels smooth, so it carries most of the score.
- Average uptime, weighted at 30%: the percentage of the period your server was reachable and online.
Memory and entity counts are not part of the score directly. They influence it through their effect on TPS, which is what the score is built around.
How it's calculated
The two inputs are combined with a simple weighted formula:
health = (avg_tps / 20) × 70 + (avg_uptime / 100) × 30
A server averaging 20 TPS with 100% uptime scores 100. A server averaging 18 TPS with 98% uptime scores about 92. The result is rounded to the nearest whole number. Because both inputs are averages over the range you're viewing, the score smooths out brief spikes: switch to the 7-day view for a recent read, or 30 and 90 days for the longer trend.
Interpreting the score
| Score | What it means |
|---|---|
| 80–100 | Healthy, no action needed |
| 50–79 | Some stress, worth a closer look |
| 0–49 | Degraded performance or uptime, investigate |
The health score is most useful as a trend, not a snapshot. A score of 72 trending down from 90 over the past week is more concerning than a score of 65 that has been stable for a month.