Station XX-7622 · recording
Rust TestServer
Online 211.106.63.210:28015 checked 10m ago
- Players now
- 2/ 50
- 4% full
- Motion · 24 h
- M0.3▲rising
- +2 players on the day
- 7-day average
- 0
- peak 2
- Rank
- #7,622
- top 34%
- Last wipe
- 8h ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 2of 50 slots
- Motion · 24 h
- M0.3▲rising+2 players
- Sharpest hour
- +1into Thu 02:00 UTC
- Peak · 48 h
- 2most 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 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 34% 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, 22:59 UTC8h ago | – | – | – | – | 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 Rust TestServer?
The procedural map on Rust TestServer is size 4,250 with seed 856364890, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on Rust TestServer?
You will find no gather rate in the name of Rust TestServer. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.
Population
How many players are recorded on Rust TestServer right now?
A reading taken now shows 2 players on Rust TestServer, which has 50 slots. Across seven days this server recorded an average of 0 players and a peak of 2. The busiest point in the last 48 hours came at 02:00 UTC, averaging 2 players.
How does Rust TestServer rank against other Rust servers?
The last seven days of player hours place Rust TestServer at #7,622, in the top 34% of all ranked servers.
Operator and location
How reliably does Rust TestServer stay online?
As recorded now, Rust TestServer is running. Its reported uptime points to a restart about 6 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. 14 October 2026 is when Rust Server Trends first recorded it.
How well does Rust TestServer perform under load?
The 48-hour average is 100 server fps; 60 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 188,809. It reached a ceiling of 8,408 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does Rust TestServer run from?
No region is published by Rust TestServer. 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 211.106.63.210:28015.
Which Rust version is Rust TestServer running?
Rust TestServer is running Rust network protocol 2635 and build 167781 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
How often does Rust TestServer wipe, and on which days?
On record so far are too few of Rust TestServer's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 8 hours is how long the current world has been running.
Lists and tags
What do the server tags on Rust TestServer mean?
Tags published by Rust TestServer and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) 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 Rust TestServer appear?
You will find Rust TestServer on the following Rust Server Trends lists: Rust community servers without the side modes. You will find it under these filters 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 24 hours.
How to join
What steps get you onto Rust TestServer?
To join, enter client.connect 211.106.63.210:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.