Station SA-13825 · no signal
Testing DO NOT ENTER
Offline SA 179.37.0.31:29015 checked 3d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak 1
- Rank
- #13,825
- top 62% · #198 in SA
- Last wipe
- 10d ago
- monthly schedule
- Next wipe
- 7d 19h
- 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, measured since 24 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 62% of all ranked servers, top 83% in SA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 19h. 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 pageMap and rules
Which map is running on Testing DO NOT ENTER?
Generated by the game, the map on Testing DO NOT ENTER is procedural, size 4,096 with seed 1337. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on Testing DO NOT ENTER?
No gather rate appears in the name of Testing DO NOT ENTER. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. Vanilla is the label it uses for itself: unchanged from Facepunch's release: no altered rates, kits or rules. The server has VAC on, Valve's anti-cheat.
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 3 days 18 hours ago. The seven-day average is 0 players, with a peak of 1.
How does Testing DO NOT ENTER rank against other Rust servers?
For player hours across the last seven days, Testing DO NOT ENTER takes #13,825 overall and #198 in South America, inside the top 62% of all ranked servers.
Operator and location
How reliably does Testing DO NOT ENTER stay online?
No contact with Testing DO NOT ENTER right now, and the last recorded contact was 3 days 18 hours ago. It was up 7% of the time across the last 3 full days: 5 of 72 hours. On 24 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is Testing DO NOT ENTER hosted?
With its SA tag, Testing DO NOT ENTER lists itself in South America. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 179.37.0.31:29015 is the address it uses.
What build of Rust does Testing DO NOT ENTER use?
On Windows, Testing DO NOT ENTER runs Rust network protocol 2635 and build 167781. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
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. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 10 days 19 hours is how long the current world has been running. The tags it publishes carry a monthly wipe schedule.
Server tags
What do the server tags on Testing DO NOT ENTER mean?
These are the tags Testing DO NOT ENTER publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs167781 (Build): It runs game build 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^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): The game is changed by plugins or settings, placing it 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. You will find it 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; Last wipe: In the last 2 weeks.
Join the server
How do you connect to Testing DO NOT ENTER?
To join, enter client.connect 179.37.0.31: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. For the website, go to https://discord.com/invite/AFCK2MPMCB.
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.