Station XX-7318 · no signal
a test server
Offline 76.151.115.232:28015 checked 3d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #7,318
- top 33%
- Last wipe
- 4d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 33% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 10.3 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 25 Oct, 10:32 UTC4d ago | M0.0▲rising | 1 | – | running | 0 | |
| Mon 5 Oct, 05:26 UTC24d ago | M0.0■steady | 0 | – | 20.2 days | 0 | |
| Sun 4 Oct, 22:06 UTC25d ago | M0.3▲rising | 2 | – | 0.3 days | 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 pageRules and settings
Which map is running on a test server?
a test server uses a procedural map, which the game generates.
Which settings and rules apply on a test server?
You will find no gather rate in the name of a test server. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on a test server?
a test server is not responding at this moment and is offline, last seen 3 days 23 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 1.
How does a test server rank against other Rust servers?
On player hours for the past week, a test server sits at #7,318, which puts it inside the top 33% of every ranked server.
Operator and location
How reliably does a test server stay online?
a test server is down at the moment; the last recorded contact was 3 days 23 hours ago. It was up 10% of the time across the last 7 full days: 16 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 4 October 2026.
Which region does a test server run from?
No region is published by a test server. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 76.151.115.232:28015 is the address it uses.
Which Rust version is a test server running?
Rust network protocol 2635 and build 168909 on Windows is what a test server runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on a test server?
The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does a test server run its wipes?
No next wipe can be predicted for a test server, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 4 days 14 hours.
Tags
What do the server tags on a test server mean?
The game's server browser reads the tags a test server publishes: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): The server has 50 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. 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 a test server appear?
The Rust Server Trends lists that take in a test server are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Connecting
How do you connect to a test server?
Enter client.connect 76.151.115.232: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.