test
Offline 133.204.156.197:28015 checked 35d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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- 522/550
- 438/450
- 60/250
- 66/250
- 53/100
- 164/200
Quick answers
from the figures on this pageReset cycle
How often does test wipe, and when?
Its rhythm cannot be told from the wipes of test on record: there are too few. 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 55 days 11 hours ago.
Tag meanings
Which tags does test carry, and what do they mean?
These are the tags test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
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.
Population
What position does test hold among Rust servers?
Ranking for test: #13,264 on seven-day player hours, top 61% of all ranked servers.
How full does test get?
test is not responding; status offline, last seen 35 days 11 hours ago.
Operator and location
What location is test hosted in?
Reading: location. test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 133.204.156.197:28015.
What Rust version is test on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by test. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on test, and is it online?
Reading: offline. test last answered 35 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Rules and settings
How is test configured, and what rules are in force?
Reading the name gives no gather rate for test. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is test on?
The game generates a procedural map for test.
Connection
How can you get onto test?
To join: start Rust, press F1 and type client.connect 133.204.156.197:28015. Or press Launch Rust here and Steam opens the game and connects you.