Testing DO NOT ENTER
Offline SA 179.37.82.15:29015 checked 6h ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 50% of all ranked servers, top 83% in SA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 18d 7h. The force wipe · high confidence
Coming wipes
- 18d 7hThu 5 Nov, 19:00 UTCFW
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 18 Oct, 04:18 UTC7h ago | – | – | running | 1 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
Quick answers
Tags and filters
Where does Testing DO NOT ENTER appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Testing DO NOT ENTER: Modded Rust servers. The server list shows it under 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; Last wipe: In the last 24 hours.
What's the meaning of the tags on Testing DO NOT ENTER?
Testing DO NOT ENTER's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp50 (Max players): There are 50 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167781 (Build): It's on build 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^m (Monthly): Facepunch's force wipe is when this server wipes each month; ^v (Vanilla): No changed rates, no kits, no rule tweaks: this is the game Facepunch released; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; SA (South America): The server browser lists it under South America. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
How well does Testing DO NOT ENTER perform?
The last 48 hours saw an average of 123 server fps, never dropping below 123. Buildings, deployables and all other world objects added up to as many as 94,072 entities. 2,135 MB was the highest memory it used. What players notice as lag comes from low fps and a rising entity count.
Where can you find Testing DO NOT ENTER?
Testing DO NOT ENTER lists South America as its location, with the SA tag. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 179.37.82.15:29015.
Is Testing DO NOT ENTER up, and how often does it stay online?
Right now Testing DO NOT ENTER is offline, having last been seen 6 hours ago. According to its reported uptime, the last restart was about 18 minutes ago. Rust Going Deep has had it on record since 18 October 2026.
What Rust version is Testing DO NOT ENTER on?
The version on Testing DO NOT ENTER is Rust network protocol 2634 and build 167781, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
How often does Testing DO NOT ENTER wipe?
The only wipe Testing DO NOT ENTER takes is the monthly force wipe. All Rust servers wipe at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 7 hours is how long ago this world came into being. The tags list wipes scheduled every month.
Rules and settings
Which rules and settings is Testing DO NOT ENTER running?
Its name does not state a gather rate for Testing DO NOT ENTER. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. Plugins in use: Oxide. Vanilla is its own description: no changed rates, no kits, no rule tweaks: this is the game Facepunch released. VAC is on: Valve's anti-cheat is active.
What's the map on Testing DO NOT ENTER?
A game-generated procedural map of size 4,300 with seed 430076273 is in play on Testing DO NOT ENTER. The map is reproducible from its size and seed, so RustMaps can show it from this page.
Player stats
How many players are on Testing DO NOT ENTER?
Testing DO NOT ENTER was last seen 6 hours ago and is offline as you read this. The seven-day average is 1 players, with a peak of 1. At 01:00 UTC in the last 48 hours, the average reached its highest: 1 players.
Where does Testing DO NOT ENTER sit in the rankings?
Over the last seven days, Testing DO NOT ENTER sits at #10,934 by player hours, among the top 50% of all ranked servers and #182 in South America.
Getting in
What's the process to join Testing DO NOT ENTER?
To join, open Rust, hit F1, and enter client.connect 179.37.82.15:29015. Or click Launch Rust on this page to open the game through Steam and connect. You can find its website at https://discord.com/invite/AFCK2MPMCB.