test
Offline 88.204.55.228:28015 checked 39d ago
Server instruments
no direct query in 48 hoursPlayers now
20% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Peak: the most players in the first 48 hours. 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 wipes- 166/250
- 119/200
- 19/250
- 15/250
- 18/100
- 25/200
Quick answers
from the figures on this pageReset cycle
When does test wipe?
The rhythm of test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 39 days 15 hours ago.
Tag meanings
Which tags does test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does test appear in Rust Metrics lists and filters?
On Rust Metrics, test sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does test sit in the rankings?
Ranking for test: #14,101 on seven-day player hours, top – of all ranked servers.
How full does test get?
test is not responding; status offline, last seen 39 days 13 hours ago.
Server
Where does test sit?
No region tag on test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 88.204.55.228:28015.
What Rust version is test on?
Rust network protocol 2633 and build 164530 on Windows is the build test runs. Matching protocol is required to join. Let Steam update your game.
Is test up, and how often does it stay up?
test reports offline. The last reading came 39 days 13 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 19 September 2026.
Settings and map
What rules does test enforce, and what are its settings?
No gather rate appears in the name: test. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on test?
Check: map. Procedural, generated by the game, on test.
Join
What do you do to join test?
To join: start Rust, press F1 and type client.connect 88.204.55.228:28015. Or press Launch Rust here and Steam opens the game and connects you.