Rust Server Analytics 41,406 players11,624 servers
All servers
Drill-through Server detail

Testing DO NOT ENTER

Offline SA 179.37.82.15:29015 checked 10d ago

Drill-through
FilterServeris Testing DO NOT ENTER
Attributes
monthly wipes vanillamoddedoxide
Last refreshed
Players now 0/ 50
7-day average 0 peak –
Rank #15,266 top 69% · #204 in SA
Last wipe 11d ago monthly schedule
Next wipe 7d 11h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
No hourly history yet.

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
This server has not answered a direct query in the last 48 hours.

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 best
RankRank in region
15k10k15k20k18 Oct19 Oct21 Oct22 Oct24 Oct25 Oct

Top 69% of all ranked servers, top 88% in SA. Ranked on player hours over the last seven days.

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe · high confidence

wipe-day peak1players, last three wipes

Coming wipes

InWhen, UTCKind
7d 11hThu 5 Nov, 19:00 UTCFW force wipe
35d 11hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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
ServerProfilePlayers now
RustArgentinaSergiopalm PVP/PVE SA · groups of 8+ · monthly · 1 on average 0 / 100
BRASUKA - VANILLA | MENSAL | SEM LIMITE SA · groups of 8+ · monthly · 1 on average 0 / 200
Rustoria.co - BR Long SA · groups of 12+ · monthly · 66 on average 30 / 200
[LATAM] Sudamerica United | 26/10 Wipe SA · groups of 32+ · monthly · 17 on average 2 / 200
PICKLE VANILLA WIPE MAPA 22/10 | BPS FORCE SA · groups of 8+ · monthly · 11 on average 5 / 100
[LATAM] Nakers | Sin Limite | Mensual SA · groups of 8+ · monthly · 4 on average 2 / 120

Quick answers

from the figures on this page

Wipe data

When does Testing DO NOT ENTER wipe?

With the force wipe, once a month, Testing DO NOT ENTER wipes. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The current world dates from 11 days 3 hours. The tags carry a monthly wipe schedule.

Wipe day on Testing DO NOT ENTER: what should you expect?

Across recent wipes the busiest point averaged 1 players. The highest player count on the latest wipe arrived 0 hours in.

Server

Which location hosts Testing DO NOT ENTER?

The SA tag on Testing DO NOT ENTER lists it in South America. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. 179.37.82.15:29015 is its address.

Which Rust version is Testing DO NOT ENTER on?

On Windows, Testing DO NOT ENTER runs Rust network protocol 2634 and build 167781. Your game must match the protocol to join, and Steam applies that update.

Is Testing DO NOT ENTER up, and how steady is its uptime?

Last seen 10 days 7 hours ago, Testing DO NOT ENTER now reports offline. Of 168 hours in the last 7 full days, 0 were up: 0%. It entered Rust Server Analytics records on 18 October 2026.

Tags

How should the tags on Testing DO NOT ENTER be read?

gmrust (Game mode): Rust survival, standard ruleset; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default team size of 8; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs167781 (Build): Game build: 167781; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^m (Monthly): The wipe cycle is monthly and follows Facepunch's force wipe; ^v (Vanilla): Stock Facepunch settings, with no rate changes, kits or extra rules; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): The Modded section, because plugins or settings modify play; SA (South America): Its browser listing sits in South America are the tags Testing DO NOT ENTER publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does Testing DO NOT ENTER appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count Testing DO NOT ENTER among their servers: Modded Rust servers: live data. It appears on the server list under the following filters: 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.

Population

What position does Testing DO NOT ENTER hold in the server rankings?

Testing DO NOT ENTER holds #15,266 on seven-day player hours and #204 in South America, inside the top 69% of the ranked field.

How many players does Testing DO NOT ENTER carry?

The last sighting of Testing DO NOT ENTER was 10 days 7 hours ago; it is offline at this refresh.

Map and rules

What are the settings on Testing DO NOT ENTER, and its rules?

The name of Testing DO NOT ENTER does not state a gather rate. The game's default 8-player group limit is in force. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Oxide. Vanilla is its own description: stock Facepunch settings, with no rate changes, kits or extra rules. The server runs with VAC, Valve's anti-cheat, enabled.

The map on Testing DO NOT ENTER: which one is it?

The game generates a procedural map of size 4,096 with seed 1337 for Testing DO NOT ENTER. Size and seed fix the map, so a RustMaps view is available from this page.

How to join

How can a player join Testing DO NOT ENTER?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 179.37.82.15:29015. Find it online at https://discord.com/invite/AFCK2MPMCB.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,^m,^v,SA,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Rust survival, standard ruleset.
mp50
Max players 50 slots in total.
ts8
Group limit Default team size of 8.
v2634
Protocol Protocol 2634 is required: your game must match to connect.
cs167781
Build Game build: 167781.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code A region code is not set.

Wipe schedule

^m
Monthly The wipe cycle is monthly and follows Facepunch's force wipe.

Difficulty

^v
Vanilla Stock Facepunch settings, with no rate changes, kits or extra rules.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.
^z
Modded The Modded section, because plugins or settings modify play.

Region

SA
South America Its browser listing sits in South America.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.