Station SA-15344 · no signal
Testing DO NOT ENTER
Offline SA 179.37.19.42:29015 checked 4d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,344
- top 69% · #204 in SA
- Last wipe
- 11d ago
- monthly schedule
- Next wipe
- 7d 3h
- 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 25 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers, top 85% in SA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. 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?
Testing DO NOT ENTER runs a procedural map of size 4,096 with seed 1337, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Testing DO NOT ENTER?
You will find no gather rate 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, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. By its own description it is vanilla: no changed rates, kits or rules: this is the game as Facepunch ships it. The server has VAC on, Valve's anti-cheat.
Player counts
What is the current population on Testing DO NOT ENTER?
Testing DO NOT ENTER is not responding at this moment and is offline, last seen 4 days 10 hours ago. The seven-day average for this server is 0 players.
How does Testing DO NOT ENTER rank against other Rust servers?
The last seven days of player hours place Testing DO NOT ENTER at #15,344, in the top 69% of all ranked servers and #204 in South America.
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 4 days 10 hours ago. Of the 72 hours in the last 3 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 25 October 2026.
Where in the world is Testing DO NOT ENTER hosted?
In South America Testing DO NOT ENTER lists itself, with the tag SA. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 179.37.19.42:29015.
What build of Rust does Testing DO NOT ENTER use?
On Windows, Testing DO NOT ENTER runs Rust network protocol 2635 and build 167781. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
On what timetable does Testing DO NOT ENTER run its wipes?
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. It has run its current world for 11 days 11 hours. Its tags state a monthly wipe schedule.
Lists and 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): You'll find standard Rust survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs167781 (Build): Game build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^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. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Testing DO NOT ENTER appear?
These Rust Server Trends lists include Testing DO NOT ENTER: Modded Rust servers, tracked live. On the server list, the filters it matches are: 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.
How to join
What steps get you onto Testing DO NOT ENTER?
To join, enter client.connect 179.37.19.42: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.