Station SA-14002 · no signal
Testing DO NOT ENTER
Offline SA 179.37.47.85:29015 checked 36d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,002
- top 61% · #208 in SA
- Last wipe
- 36d ago
- monthly schedule
- Next wipe
- 8d 2h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
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 61% of all ranked servers, top 73% in SA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 8d 2h. The force wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on Testing DO NOT ENTER?
The map on Testing DO NOT ENTER is procedural, produced by the game.
Which settings and rules apply on Testing DO NOT ENTER?
You will find no gather rate in the name of Testing DO NOT ENTER. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. By its own description it is vanilla: unchanged from Facepunch's release: no altered rates, kits or rules. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on Testing DO NOT ENTER right now?
Testing DO NOT ENTER is not responding at this moment and is offline, last seen 36 days 19 hours ago.
How does Testing DO NOT ENTER rank against other Rust servers?
Testing DO NOT ENTER is #208 in South America and #14,002 worldwide on the past week's player hours, within the top 61% of ranked servers.
Server details
How reliably does Testing DO NOT ENTER stay online?
As recorded now, Testing DO NOT ENTER is not reachable, the last contact having been 36 days 19 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 21 September 2026.
Where in the world is Testing DO NOT ENTER hosted?
In South America Testing DO NOT ENTER lists itself, with the tag SA. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 179.37.47.85:29015.
What build of Rust does Testing DO NOT ENTER use?
Rust network protocol 2633 and build 164530 on Windows is what Testing DO NOT ENTER runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
How often does Testing DO NOT ENTER wipe, and on which days?
From the force wipe the next wipe of Testing DO NOT ENTER is estimated. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 36 days 20 hours. A monthly wipe schedule is published in its tags.
Tags
What do the server tags on Testing DO NOT ENTER mean?
Tags published by Testing DO NOT ENTER and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs164530 (Build): Game build: 164530; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; SA (South America): In the server browser it appears under South America. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Testing DO NOT ENTER appear?
You will find Testing DO NOT ENTER on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up 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.
Join the server
How do you connect to Testing DO NOT ENTER?
To join, enter client.connect 179.37.47.85:29015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.