Testing DO NOT ENTER
Offline SA 179.37.82.15:29015 checked 10d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 18 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 88% in SA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 10h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 10hFW
- WPT 2Thu 3 Dec, 19:00 UTC35d 10hFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 18 Oct, 04:18 UTC11d ago | 1 | – | 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- 0/100
- 0/200
- 31/200
- 4/200
- 2/100
- 3/120
Quick answers
from the figures on this pageReset cycle
What happens on Testing DO NOT ENTER when wipe day comes?
The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.
How often does Testing DO NOT ENTER wipe, and when?
With the force wipe, once a month, Testing DO NOT ENTER wipes. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 11 days 4 hours ago the current world was made. A monthly wipe schedule is published in its tags.
Tags
How should you read the tags on Testing DO NOT ENTER?
Tags published by Testing DO NOT ENTER, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game; SA (South America): South America is the browser category it sits in. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Testing DO NOT ENTER?
Rust Metrics lists featuring Testing DO NOT ENTER: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: 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.
Occupancy
What position does Testing DO NOT ENTER hold among Rust servers?
Top 69% of all ranked servers: Testing DO NOT ENTER takes #15,266 on seven-day player hours and #204 in South America.
How full does Testing DO NOT ENTER get?
Testing DO NOT ENTER is not responding; status offline, last seen 10 days 8 hours ago.
Server details
Where does Testing DO NOT ENTER sit?
Its SA tag places Testing DO NOT ENTER in South America. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 179.37.82.15:29015.
What Rust version is Testing DO NOT ENTER on?
Reading: Testing DO NOT ENTER, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.
Is Testing DO NOT ENTER up, and how often does it stay up?
Reading: offline. Testing DO NOT ENTER last answered 10 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 18 October 2026, recorded by Rust Metrics.
Map and rules
What rules does Testing DO NOT ENTER enforce, and what are its settings?
No gather rate appears in the name: Testing DO NOT ENTER. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. The server calls itself vanilla, with this meaning: the stock game: Facepunch's rates, kits and rules, unchanged. Anti-cheat reading: VAC on, Valve's system.
What map is Testing DO NOT ENTER on?
Check: map. Procedural, size 4,096, seed 1337, generated by the game on Testing DO NOT ENTER. View it on RustMaps from this page: matching size and seed give an identical map.
How to join
How can you get onto Testing DO NOT ENTER?
Press F1 in Rust and enter client.connect 179.37.82.15:29015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://discord.com/invite/AFCK2MPMCB is where its website sits.