Station XX-6810 · no signal
TestServer
Offline 45.178.1.154:28015 checked 3d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #6,810
- top 31%
- 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
- 1of 10 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 31% 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.
- usual gap
- 4.8 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 26 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 23 Oct, 15:56 UTC5d ago | M0.0■steady | 1 | – | running | 1 | |
| Sun 18 Oct, 20:34 UTC10d ago | M0.0▲rising | 1 | held half | 4.8 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 pageServer rules
Which map is running on TestServer?
TestServer uses a procedural map, which the game generates.
Which settings and rules apply on TestServer?
You will find no gather rate in the name of TestServer. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on TestServer?
No players are recorded on TestServer at this moment; it is offline, and the last sighting was 3 days 21 hours ago. The seven-day average is 1 players, with a peak of 1.
How does TestServer rank against other Rust servers?
Over the last seven days, TestServer recorded enough player hours to reach #6,810 worldwide, placing it in the top 31% of all ranked servers.
Server facts
How reliably does TestServer stay online?
TestServer is down at the moment; the last recorded contact was 3 days 21 hours ago. 21 of 168 hours in the last 7 full days were up time, 12% of the total. On 12 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is TestServer hosted?
No region is published by TestServer. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 45.178.1.154:28015.
What build of Rust does TestServer use?
Rust network protocol 2635 and build 168909 on Windows is what TestServer runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on TestServer?
On average, the busiest point of its recent wipes drew 1 players. 26 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
On what timetable does TestServer run its wipes?
The rhythm of TestServer cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 5 days 5 hours is how long the current world has been running.
Tags
What do the server tags on TestServer mean?
These are the tags TestServer publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots are available; 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): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. 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?
These Rust Server Trends lists include TestServer: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How to join
How do you connect to TestServer?
Enter client.connect 45.178.1.154: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.