How to Read Ping and Player Statistics on PingTrack
Updated
PingTrack (pingtrack.lenni0451.net) is a public dashboard that tracks Minecraft server statistics and ping histories. To interpret it, read each number against its time window: the range selector (10 minutes, 1 hour, 24 hours, 7 days, 30 days) sets the period that every "range" figure describes, while "current" values are live readings and "all-time" values are historical records that ignore the selector. The dashboard also shows a refresh/pause control and a "Last updated" timestamp, so check those before trusting any number as current.
The dashboard at a glance
The main page opens with summary tiles and a server table:
- Active / Tracked Servers — how many servers are currently reporting versus how many are on the tracking list.
- Total Online Players — combined player count across tracked servers at the last refresh.
- Best Ping in Range — the lowest latency observed on any tracked server within the selected time window.
- Avg / Worst Ping — the average and highest latency across the window.
- Player Count History — a graph you can copy, with linear or logarithmic scaling.
- Server table — columns for Server Name, Online Players, Range Peak, All-Time Peak, Current Ping, and Range Avg Ping, with search, pinning, and a detailed overview link per server.
Ping metrics explained
Current ping
The latency measured at the most recent refresh. It is a single snapshot, so one high or low reading is not a trend. If the page is paused, this value is frozen at the pause moment — the "Last updated" field tells you how old it is.
Range avg ping
The mean latency over the selected window. This is the number to compare across servers, because it smooths out momentary spikes. A server with a low current ping but a high range average has been unstable recently.
Best / avg / worst ping in range
The summary tiles give the floor, middle, and ceiling of latency across all tracked servers in the window. Use them to judge the overall health of your tracked list: a wide gap between best and worst suggests at least one server is struggling, and the per-server table tells you which.
Choosing a time range
The selector changes what "range" means everywhere on the page:
| Range | Best for |
|---|---|
| 10 minutes / 1 hour | Spotting a problem happening right now |
| 24 hours | Daily patterns, such as evening peak load |
| 7 days | Weekly cycles and recurring maintenance windows |
| 30 days | Long-term stability and gradual degradation |
A server that looks fine at 1 hour can look poor at 30 days if it has periodic outages. Check more than one window before drawing conclusions.
Player count metrics explained
Range peak vs. all-time peak
Range peak is the highest concurrent player count within the selected window. All-time peak is the highest ever recorded for that server and does not change when you switch ranges. A server whose range peak equals its all-time peak is at or near its historical maximum; one far below it is quieter than its best day.
Online players and player count history
The Online Players column is the current count. The history graph plots counts over the selected window, and you can switch between linear and logarithmic scaling — logarithmic makes large and small servers comparable on one chart. Copying the graph gives you the underlying data for your own records.
A worked example
Suppose a server shows Current Ping 40 ms, Range Avg Ping 95 ms (24 hours), Range Peak 120 players, and All-Time Peak 300 players. The reading means: right now latency is good, but over the past day it averaged more than twice that, so there were slow periods. Player activity today peaked at 120, well under the server's record of 300 — it is currently below its historical high. Switching to 7 days and finding the range average drops to 60 ms would tell you the slowdown is recent rather than chronic.
Practical checks before you decide
- Confirm the refresh state: if paused, note the "Last updated" time.
- Compare range average, not just current ping, when judging stability.
- Use at least two time ranges before concluding a server is unhealthy or quiet.
- Treat all-time peak as context, not a current performance measure.
The dashboard is a monitoring view; it reports what has been measured and does not itself diagnose causes. Use the per-server detailed overview for the full history behind any figure.