![[LATAM] DISTRITO CERO | VANILLA | SOLO/DUO/TRIO | WIPE 22/10 banner](https://i.postimg.cc/5yyFSCqQ/a3d843c1-b66f-4288-a9cb-500402391fda.png)
[LATAM] DISTRITO CERO | VANILLA | SOLO/DUO/TRIO | WIPE 22/10
Server admin? Sign in with Steam to claim this server.
112 ms · Chicago
Jitter 7.8 ms
Last checked 2 m ago
4 / 100 players
Procedural Map
Max 3 21 days live Avg ping 97.4 ms Avg jitter 6.9 ms Wipe cycle 7 ±0 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 130.94.105.242:30120
First seen 27.09.2026
Last wipe: (2 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 7 | |
| 7 | |
| 7 | |
| — |
Player count history
Wipe timing behind this data is sometimes inferred rather than confirmed, so daily figures right around a wipe boundary can land on the wrong day. Accuracy improves over time as detection gets more precise.
Highest peak 18 Oct 2 · 02:45 UTC Median daily peak 8 (median of daily peaks, not average population)
Observed daily peak
22 full · 0 partial · 0 offline · 9 no data
Population persistence across recent wipes
Each line follows one wipe cycle from the moment it started, lined up by days since that wipe rather than by calendar date — so you can compare how well this server held onto its population after different resets, independent of when each one happened.
- Oct 15
- Oct 8
- Oct 1
- Sep 24
Server info
DISTRITO CERO — Rust latino, vanilla de verdad.
» Rates x1 · loot sin tocar
» Solo / Duo / Trio · grupo máximo 3 · teaming = ban al grupo completo
» Wipe de mapa todos los jueves · el conocimiento (blueprints) se borra solo el primer jueves de cada mes · próximo mapa: jueves 15/10
» Mapa 3500 procedural · host en Sudamérica, ping bajo LATAM
» EAC + staff activo · admins no juegan
» Sin kits, sin VIP, sin pay to win
Sitio web: distritocero.xyz
Discord: discord.gg/yf8K27bRdp — reportes, team y avisos de wipe
rs01K*faozJ^0rAi40%ozz
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 112 ms | 4 | |
| Online | 101 ms | 0 | |
| Online | 94 ms | 0 | |
| Online | 112 ms | 2 | |
| Online | 99 ms | 4 | |
| Online | 93 ms | 4 | |
| Online | 101 ms | 5 | |
| Online | 100 ms | 4 | |
| Online | 101 ms | 4 | |
| Online | 96 ms | 4 | |
| Online | 97 ms | 3 | |
| Online | 96 ms | 0 | |
| Online | 96 ms | 3 | |
| Online | 107 ms | 5 | |
| Online | 114 ms | 4 | |
| Online | 104 ms | 2 | |
| Online | 106 ms | 3 | |
| Online | 100 ms | 5 | |
| Online | 106 ms | 5 | |
| Online | 105 ms | 0 | |
| Online | 100 ms | 0 | |
| Online | 111 ms | 3 | |
| Online | 100 ms | 6 | |
| Online | 106 ms | 2 | |
| Online | 103 ms | 7 | |
| Online | 106 ms | 6 | |
| Online | 95 ms | 0 | |
| Online | 91 ms | 1 | |
| Online | 96 ms | 0 | |
| Online | 95 ms | 0 | |
| Online | 90 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 100 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 1 | |
| Online | 92 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 97 ms | 1 | |
| Online | 98 ms | 2 | |
| Online | 96 ms | 0 | |
| Online | 95 ms | 4 | |
| Online | 96 ms | 2 | |
| Online | 101 ms | 2 | |
| Online | 90 ms | 1 | |
| Online | 96 ms | 1 | |
| Online | 97 ms | 2 | |
| Online | 96 ms | 2 | |
| Online | 96 ms | 2 |
Other servers in Colombia (low ping)
Frequently asked questions
What does "wipe" mean in Rust?
A wipe resets a server's map and usually player progress too — bases, resources, and blueprints, unless the server keeps blueprints through wipes (shown here as "No BP wipe"). Most servers wipe on a regular schedule, often weekly.
What does "force wipe" mean?
Facepunch pushes a mandatory update on the first Thursday of each month that requires every Rust server to wipe, regardless of its own schedule — a "force wipe," distinct from a server's regular map wipe.
How do I know when this server wipes?
The "Next wipe" time above is extracted from the server's own published schedule. "High confidence" means the server stated an explicit date or time; "Predicted" means it's estimated from the server's typical cadence and isn't guaranteed.
How do I connect to this server?
Copy the server address above, open Rust's in-game console with F1, and run client.connect followed by the address — or connect directly through Steam's server browser using the same address.