Real ping, not a distance estimate
Most Rust server browsers, including Steam’s own, show a “ping” figure that’s actually estimated from geographic distance — not measured. Rusti.fi measures the real thing: a distributed network of probes, positioned in Helsinki, Frankfurt, Chicago, and other regions, sends the same connection query Rust’s own client uses directly to each server and times the round trip. Pick the region closest to you and the ping shown is the ping you’d actually get.
Populated servers are re-measured as often as every 90 seconds, so the numbers reflect what’s happening now, not a stale snapshot from whenever the server was last discovered.
Where wipe times come from
Server owners don’t submit wipe schedules to Steam in any structured way — most publish them as free text in their server’s name or description (“Wiped 3 days ago”, “Map wipe every Thursday at 18:00 CET”). Rusti.fi parses that text directly, recognizing dozens of real-world phrasings collected from actual servers, and converts it into a real timestamp — including resolving announced timezones to the correct UTC time, accounting for daylight saving.
Every extracted wipe time carries a confidence level:
- High confidence — the server stated an explicit date or time.
- Predicted — no explicit next occurrence was found, only a recurring cadence label like “Weekly”; the next wipe is estimated from that cadence and the server’s own last known wipe.
Player counts, and why they’re sometimes capped centrally
Rust’s own server-query protocol reports both player count and server capacity as a single byte — a hard ceiling of 255. A server configured for more than 255 slots will report a wrapped, meaningless number over that protocol. Rusti.fi detects this and falls back to Steam’s own uncapped listing for those specific servers, rather than showing an obviously wrong count.
What we don’t do
Rusti.fi doesn’t run ads disguised as server listings, doesn’t accept payment to inflate a server’s position in search results, and doesn’t independently verify a server’s self-reported population — no third party can, since that data is ultimately self-reported by each server process. What we can verify, and do, is ping, uptime, and whether a server’s own published text matches what actually happens.