TEST
Offline 185.119.0.41:28015 checked 41d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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- 253/275
- 20/250
- 16/250
- 167/200
- 62/200
- 39/100
Quick answers
from the figures on this pageReset cycle
What wipe timing does TEST follow?
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. 42 days 16 hours ago the current world was made.
Lists and filters
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; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does TEST appear in Rust Metrics lists and filters?
Rust Metrics lists featuring TEST: 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
What position does TEST hold among Rust servers?
Ranking for TEST: #15,488 on seven-day player hours, top – of all ranked servers.
What is the population on TEST?
Status for TEST: offline. Last seen 41 days 13 hours ago.
Server
Which location does TEST run from?
Reading: location. TEST gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 185.119.0.41:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 163794 on Windows is the build TEST runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on TEST, and is it online?
Check: connection. TEST is offline at this moment. Last contact was 41 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 15 September 2026.
Settings and map
What rules does TEST enforce, and what are its settings?
No gather rate appears in the name: TEST. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
What map is TEST on?
Procedural map on TEST, made by the game's generator.
Connection
What do you do to join TEST?
Check: join. Open Rust, press F1, then enter client.connect 185.119.0.41:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.