Test
Offline 77.119.168.64:28015 checked 10d 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 bestTop 69% 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- 322/375
- 210/250
- 34/250
- 28/250
- 54/100
- 73/200
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Test follow?
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. 10 days 4 hours ago the current world was made.
Lists and filters
How should you read the tags on Test?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; v2590 (Protocol): Your game must run protocol 2590 to get in; cs123128 (Build): The server runs game build 123128; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Test. 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?
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; Last wipe: In the last 2 weeks.
Player count
Where does Test sit in the rankings?
Ranking for Test: #15,247 on seven-day player hours, top 69% of all ranked servers.
What is the population on Test?
Reading for Test: offline at this moment; last seen 10 days 4 hours ago.
Server
Where does Test sit?
No region tag on Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 77.119.168.64:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2590 and build 123128, Windows. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on Test, and is it online?
Test reports offline. The last reading came 10 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 18 October 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on Test?
Reading the name gives no gather rate for Test. The group limit is not published. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is Test on?
Procedural map on Test, made by the game's generator.
Join
How do you connect to Test?
To join: start Rust, press F1 and type client.connect 77.119.168.64:28015. Or press Launch Rust here and Steam opens the game and connects you.