Test
Offline 95.179.39.212:28015 checked 41d 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 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- 70/250
- 93/200
- 202/250
- 6/100
- 248/250
- 393/375
Quick answers
from the figures on this pageReset cycle
When does Test wipe?
To tell the rhythm of Test, too few of its wipes 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 41 days 17 hours ago.
Lists and filters
Which tags does Test carry, and what do they mean?
Tags published by Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Game build reading: 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Test?
These Rust Metrics lists carry Test: Rust community servers: live readings. Check: filters. On the server list it appears under these: 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?
Player hours over seven days put Test at #13,305, in the top – of all ranked servers.
How full does Test get?
Reading for Test: offline at this moment; last seen 41 days 7 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. The endpoint you need is 95.179.39.212:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2633 and build 164530, Windows. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Test, and is it online?
Test reports offline. The last reading came 41 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 18 September 2026.
Map and rules
What rules does Test enforce, and what are its settings?
Reading the name gives no gather rate for Test. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
What map is Test on?
The game generates a procedural map for Test.
Join
How can you get onto Test?
Press F1 in Rust and enter client.connect 95.179.39.212:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.