An entry in the registerNo. 14,002
Testing DO NOT ENTER
Offline SA 179.37.47.85:29015 checked 37d ago
Testing DO NOT ENTER is a Rust server in South America. It was offline at the last count. It stands at No. 14,002 of the ranked servers, the top 61%, and No. 208 in South America. It last wiped 37d ago, on a monthly schedule, and the next wipe is expected on Thursday 5 November, with the force wipe. Its own tags class it as vanilla, modded, oxide.
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
§ 3Standingthe rank, daily · 1 is best
Top 61% of all ranked servers, top 73% in SA. Ranked on player hours over the last seven days.
§ 4The wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 7h. The force wipe
§ 5The record of wipesnewest first
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes
- 1 RustArgentinaSergiopalm PVP/PVE0/100 SA · groups of 8+ · monthly · 1 on average
- 2 BRASUKA - VANILLA | MENSAL | SEM LIMITE0/200 SA · groups of 8+ · monthly · 1 on average
- 3 Rustoria.co - BR Long21/200 SA · groups of 12+ · monthly · 66 on average
- 4 [LATAM] Sudamerica United | 26/10 Wipe1/200 SA · groups of 32+ · monthly · 15 on average
- 5 PICKLE VANILLA WIPE MAPA 22/10 | BPS FORCE0/100 SA · groups of 8+ · monthly · 11 on average
- 6 [LATAM] Nakers | Sin Limite | Mensual3/120 SA · groups of 8+ · monthly · 4 on average
§ 7Questions answeredfrom the figures in this entry
Server details
What Rust version is Testing DO NOT ENTER on?
Rust network protocol 2633 and build 164530 on Windows is what Testing DO NOT ENTER runs. The protocol must match on your game to join; the update comes through Steam.
How reliable is Testing DO NOT ENTER, and is it online now?
Testing DO NOT ENTER shows offline as of the latest refresh, last seen 37 days 14 hours ago. The records show 0% uptime over the last 7 full days: 0 of 168 hours up. Rust Server Stats records a first sighting on 21 September 2026.
Where does Testing DO NOT ENTER operate from?
Under the SA tag, Testing DO NOT ENTER lists itself in South America. The location Rust Server Stats shows is the one a server states; the machine's own location is not looked up. 179.37.47.85:29015 — that is the address.
Settings and map
The map for Testing DO NOT ENTER: which one is it?
Generation by the game gives Testing DO NOT ENTER its procedural map.
What settings and rules does Testing DO NOT ENTER run?
Nothing in the name of Testing DO NOT ENTER gives a gather rate. Eight players per group is the default and the limit here. Play is survival, gather, build and raid: the standard game. Combat and raiding between players are permitted. The server browser lists it under Modded, where plugins or settings alter the game. Plugins run here: Oxide. The server describes itself as vanilla: no changed rates, kits or rules: the game as Facepunch ships it. VAC, Valve's anti-cheat, is enabled.
Population
How full does Testing DO NOT ENTER get?
Testing DO NOT ENTER is offline at present; the last response came 37 days 14 hours ago.
Where does Testing DO NOT ENTER sit in the rankings?
Ranked on seven-day player hours, Testing DO NOT ENTER holds #14,002, with #208 in South America; the top 61% of ranked servers includes it.
Tag and list record
Testing DO NOT ENTER sits in which Rust Server Stats lists and filters?
The Rust Server Stats lists Testing DO NOT ENTER fits: Modded Rust servers. On the server list it comes up under these filters: Region: South America; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should the tags on Testing DO NOT ENTER be read?
These tags are Testing DO NOT ENTER's, and the game's browser reads them: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 is the number of slots; ts8 (Group limit): 8 to a team, which is the default; v2633 (Protocol): Join only on protocol 2633; other versions cannot connect; cs164530 (Build): The build number is 164530; ptrak (Networking): RakNet carries it, the standard layer for the game; $r? (Region code): No region code is set; ^m (Monthly): One wipe a month, alongside the force wipe from Facepunch; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the browser lists it as Modded; SA (South America): In the browser it appears under South America. At the top of this page are its current players, queue and world creation time, all taken from the tags.
Wipe schedule
The wipe timetable for Testing DO NOT ENTER: what does it show?
The estimate for Testing DO NOT ENTER's next wipe is drawn from the force wipe. On Thursday 5 November at 19:00 UTC comes its next wipe, the force wipe that takes every Rust server. The world now in play was generated 37 days 16 hours ago. The tags list wipes as monthly.
Connection
How does one connect to Testing DO NOT ENTER?
Join on this page with Launch Rust, which opens Rust through Steam and connects you, or open the console with F1 and enter client.connect 179.37.47.85:29015.