Offline88.204.55.228:28015checked 24d ago
test
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 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 wipesQuick answers
from the figures on this pageRules, map and settings
What are the server rules for test?
The name of test does not state a gather rate. Groups are capped at 8 players, the default in the game. The server runs survival, gather, build, raid: the standard game. PvP and raiding are enabled. Under Community in the server browser, it is a community server. Anti-cheat VAC from Valve is on.
What map is used on test?
A procedural map is what test runs, generated by the game.
Tags, lists and filters
Where can test be found in Rust Player Count lists and filters?
These Rust Player Count lists include test: Best Rust PvE servers. You can find it on the server list using these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you interpret the tags on test?
For the game's server browser, test publishes: gmrust (Game mode): The usual Rust survival experience; mp5 (Max players): The server has 5 slots; ts8 (Group limit): This uses the default team cap: 8 players; v2633 (Protocol): To join, your game must match protocol 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): It uses RakNet, the game's default networking; $r? (Region code): The region code field is empty. You will also find its current players, its queue and its world creation time in the tags, displayed at the top of this page.
Player numbers
What is the player count on test?
Currently offline, test was last seen 24 days 20 hours ago.
Where does test sit in the rankings?
Over the last seven days, test is #14,101 for player hours, placing it in the top – of ranked servers.
Server details
How reliable is test, and is it online?
test is down at the moment and was last seen 24 days 20 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. 19 September 2026 is when Rust Player Count first saw it.
What Rust version is used on test?
On Windows, test runs Rust network protocol 2633 and build 164530. Joining requires the same protocol on your game; Steam updates it for you.
What is the location of test?
There is no region published by test. The location shown by Rust Player Count is the one a server provides; it does not verify where the machine actually is. It is located at 88.204.55.228:28015.
Wipe days
When does test wipe?
Too few wipes are recorded for test to reveal its pattern. On Thursday 5 November at 19:00 UTC the next monthly force wipe arrives, wiping every Rust server. The world in play was created 24 days 23 hours ago.
How to join
What is the process to join test?
Joining is done by opening the console (F1) and running client.connect 88.204.55.228:28015. Another way is the Launch Rust option on this page, which uses Steam to start Rust and put you in.
Server tags
what each one meansPublished as mp5,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp5
ts8
v2633
cs164530
ptrak
$r?
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.