Trust signals
How MineTracker flags suspicious player counts
Some Minecraft servers report player counts that are technically valid status responses but unlikely to represent real connected players. MineTracker does not hide that uncertainty; it scores and explains it.
Large flatlines
A large server should normally show some movement across many samples. If a high player count stays almost perfectly flat over time, MineTracker treats that as suspicious and lowers the trust score.
Alias and duplicate signals
Many domains can point to the same backend. When several entries share an IP and report the same player count, MineTracker marks them as likely aliases and avoids counting the same population multiple times in totals.
Meme numbers and odd patterns
Numbers such as repeated 9999-style values, missing sample lists, unusual caps or inconsistent status behavior can all contribute to a lower confidence score. These signals are shown as context, not as a final accusation.
Why max players is not enough
Some real networks report a current player count above a nominal max player value because the max field is used as a display hint or proxy value. MineTracker therefore does not treat current players above max players as fake by itself.
More context
Continue reading
How tracking works · Fake count detection · Java vs Bedrock · Uptime explained · Peak times