Station XX-6638 · no signal
TestServer
Offline 89.182.189.254:28015 checked 2h ago
- Players now
- 1/ 15
- 7% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 2
- peak 3
- Rank
- #6,638
- top 30%
- Last wipe
- 12h ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 15 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +2into Wed 19:00 UTC
- Peak · 48 h
- 3most players in any hour
- Events picked
- 1wipe on this record, in red
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, measured since 28 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 30% 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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 28 Oct, 13:34 UTC12h ago | – | – | – | – | running | 2 |
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 pageMap and rules
Which map is running on TestServer?
TestServer runs a procedural map of size 6,000 with seed 984372799, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on TestServer?
The name of TestServer gives no gather rate. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Population
How many players are recorded on TestServer right now?
No players are recorded on TestServer at this moment; it is offline, and the last sighting was 2 hours ago. The seven-day average is 2 players, with a peak of 3. The busiest point in the last 48 hours came at 19:00 UTC, averaging 3 players.
How does TestServer rank against other Rust servers?
The last seven days of player hours place TestServer at #6,638, in the top 30% of all ranked servers.
Operator and location
How reliably does TestServer stay online?
TestServer is down at the moment; the last recorded contact was 2 hours ago. Its reported uptime points to a restart about 9 hours ago. Its earliest appearance in the records of Rust Server Trends dates to 28 October 2026.
Does TestServer hold a steady tick rate?
The 48-hour average is 83 server fps; 69 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 204,065. Its highest memory use was 4,080 MB. Low fps together with a growing entity count is what players experience as lag.
Which region does TestServer run from?
A region is not published by TestServer. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 89.182.189.254:28015 is the address it uses.
Which Rust version is TestServer running?
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 day
On what timetable does TestServer run its wipes?
Too few wipes of TestServer are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 12 hours.
Tags
What do the server tags on TestServer mean?
These are the tags TestServer publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp15 (Max players): Slots: 15; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed 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: 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 24 hours.
Connecting
How do you connect to TestServer?
You can connect by pressing F1 in Rust and typing client.connect 89.182.189.254: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.