Offline SA 179.37.47.85:29015 checked 37d ago
Testing DO NOT ENTER
Connect
srv = rust.server("179.37.47.85:29017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 61% of all ranked servers, top 73% in SA. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h. # The force wipe
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 179.37.47.85:29015
- region
- SA
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 21 Sep 2026, 19:30 UTC
- hostname
- –
- first seen
- 21 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | RustArgentinaSergiopalm PVP/PVE | SA · groups of 8+ · monthly · 1 on average | 1/100 |
| 1 | CHARRUA | SA · groups of 8+ · monthly · 1 on average | 1/100 |
| 2 | BRASUKA - VANILLA | MENSAL | SEM LIMITE | SA · groups of 8+ · monthly · 1 on average | 4/200 |
| 3 | Rustoria.co - BR Long | SA · groups of 12+ · monthly · 65 on average | 89/200 |
| 4 | [LATAM] Sudamerica United | 26/10 Wipe | SA · groups of 32+ · monthly · 16 on average | 27/200 |
| 5 | PICKLE VANILLA WIPE MAPA 22/10 | BPS FORCE | SA · groups of 8+ · monthly · 11 on average | 10/100 |
Quick answers
From the figures on this page.
Population
How does Testing DO NOT ENTER compare in the rankings?
Player hours over the last seven days: #14,002 for Testing DO NOT ENTER, #208 in South America, within the top 61% of the ranked set.
How full does Testing DO NOT ENTER run?
Testing DO NOT ENTER returns no live count at this refresh, having last been seen 37 days 6 hours ago.
Server data
What Rust version does Testing DO NOT ENTER run?
Version Rust network protocol 2633 and build 164530 on Windows is reported by Testing DO NOT ENTER. Joining needs the same protocol on your game; Steam handles the update.
Is Testing DO NOT ENTER up, and what does its uptime show?
The latest sample has Testing DO NOT ENTER offline, with a last sighting 37 days 6 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 21 September 2026.
Which location does Testing DO NOT ENTER run from?
In South America, Testing DO NOT ENTER lists itself, using the SA tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 179.37.47.85:29015 is its address.
Settings and map
What rules and settings are recorded for Testing DO NOT ENTER?
The name Testing DO NOT ENTER carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Vanilla, by its own description: facepunch's stock game, with rates, kits and rules untouched. VAC, Valve's anti-cheat, is enabled.
Which map has Testing DO NOT ENTER selected?
Testing DO NOT ENTER runs a procedural map, which the game generates.
Wipe schedule
When does Testing DO NOT ENTER wipe, and how often?
Expect an estimate: Testing DO NOT ENTER's next wipe is projected from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 37 days 8 hours ago. A monthly wipe schedule is published in its tags.
Lists and tags
Where does Testing DO NOT ENTER appear among Rust Data lists and filters?
On Rust Data, Testing DO NOT ENTER appears in these lists: Modded Rust servers. It appears under these filters on the server list: 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 you read the server tags on Testing DO NOT ENTER?
These tags are published by Testing DO NOT ENTER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; SA (South America): South America is its listing in the server browser. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join Testing DO NOT ENTER?
The manual route: launch Rust, F1, then client.connect 179.37.47.85:29015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.