Station XX-14919 · no signal
Test Server - Dont enter
Offline 201.254.83.131:28015 checked 16d ago
- Players now
- 0/ 3
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,919
- top 68%
- Last wipe
- 18d 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 3 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 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 19h. The force wipe · high confidence
- wipe-day peak
- 2players, last three wipes
Coming wipes
- 7d 19hThu 5 Nov, 19:00 UTCFW
- 35d 19hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 9 Oct, 23:52 UTC18d ago | M0.0▲rising | 2 | – | running | 1 |
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 Test Server - Dont enter?
A procedural map runs on Test Server - Dont enter, generated by the game.
Which settings and rules apply on Test Server - Dont enter?
The name of Test Server - Dont enter gives no gather rate. The group limit is 8 players, the game's default. It plays in survival 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. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Live population
What is the current population on Test Server - Dont enter?
Test Server - Dont enter is not responding at this moment and is offline, last seen 16 days 23 hours ago.
How does Test Server - Dont enter rank against other Rust servers?
On player hours for the past week, Test Server - Dont enter sits at #14,919, which puts it inside the top 68% of every ranked server.
Operator and location
How reliably does Test Server - Dont enter stay online?
Test Server - Dont enter is down at the moment; the last recorded contact was 16 days 23 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 9 October 2026.
Which region does Test Server - Dont enter run from?
A region is not published by Test Server - Dont enter. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 201.254.83.131:28015.
Which Rust version is Test Server - Dont enter running?
Test Server - Dont enter is running Rust network protocol 2634 and build 167398 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on Test Server - Dont enter?
On average, the busiest point of its recent wipes drew 2 players. The peak on the most recent wipe came 1 hours after the wipe.
How often does Test Server - Dont enter wipe, and on which days?
At the force wipe each month Test Server - Dont enter wipes, and at no other time. 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 18 days 23 hours. Its tags state a monthly wipe schedule.
Server tags
What do the server tags on Test Server - Dont enter mean?
Tags published by Test Server - Dont enter and read by the game's server browser include gmvanilla (Game mode): Survival in vanilla mode; mp3 (Max players): The server has 3 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167398 (Build): It runs game build 167398; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 Test Server - Dont enter appear?
The Rust Server Trends lists that take in Test Server - Dont enter are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Join the server
How do you connect to Test Server - Dont enter?
You can connect by pressing F1 in Rust and typing client.connect 201.254.83.131:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects 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.