Station XX-15454 · no signal
TESTSERVER
Offline 91.97.157.227:28015 checked 4d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,454
- top 70%
- Last wipe
- 5d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 2 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 16 Nov, 10:53 UTC5d ago | M0.0■steady | 0 | – | running | 0 |
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 TESTSERVER?
The map on TESTSERVER is procedural, produced by the game.
Which settings and rules apply on TESTSERVER?
You will find no gather rate in the name of TESTSERVER. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. It is a community server, and the browser lists it under Community. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on TESTSERVER?
TESTSERVER is not responding at this moment and is offline, last seen 4 days 9 hours ago. Averaged across the last seven days, the population was 0 players.
How does TESTSERVER rank against other Rust servers?
The last seven days of player hours place TESTSERVER at #15,454, in the top 70% of all ranked servers.
Server facts
How reliably does TESTSERVER stay online?
As recorded now, TESTSERVER is not reachable, the last contact having been 4 days 9 hours ago. 4 of 96 hours in the last 4 full days were up time, 4% of the total. 16 November 2026 is when Rust Server Trends first recorded it.
Where in the world is TESTSERVER hosted?
No region is published by TESTSERVER. 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 91.97.157.227:28015.
What build of Rust does TESTSERVER use?
On Linux, TESTSERVER runs Rust network protocol 2636 and build 170545. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on TESTSERVER?
On average, the busiest point of its recent wipes drew 0 players. The peak on the most recent wipe came 0 hours after the wipe.
How often does TESTSERVER wipe, and on which days?
On record so far are too few of TESTSERVER's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. The present world dates from 5 days 1 hours.
Lists and tags
What do the server tags on TESTSERVER mean?
The game's server browser reads the tags TESTSERVER publishes: gmvanilla (Game mode): This is vanilla survival; mp2 (Max players): Slots: 2; ts8 (Group limit): This uses the game default of 8 per team; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs170545 (Build): The game build is 170545; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does TESTSERVER appear?
You will find TESTSERVER on the following Rust Server Trends lists: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How to join
What steps get you onto TESTSERVER?
Enter client.connect 91.97.157.227:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.