test
Offline 77.48.47.4:28015 checked 25d 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 70% 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- 659/700
- 418/475
- 37/250
- 56/250
- 222/200
- 112/150
Quick answers
from the figures on this pageWipe schedule
How often does test wipe, and when?
To tell the rhythm of test, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 25 days 21 hours ago.
Tag meanings
How should you read the tags on test?
These are the tags test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166586 (Build): Game build reading: 166586; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is 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?
These Rust Metrics lists carry test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does test sit in the rankings?
Player hours over seven days put test at #15,973, in the top 70% of all ranked servers.
What is the population on test?
Status for test: offline. Last seen 25 days 15 hours ago.
Server details
Where does test sit?
No region tag on test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 77.48.47.4:28015.
What Rust version is test on?
Reading: test, Rust network protocol 2634 and build 166586, Windows. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on test, and is it online?
test reports offline. The last reading came 25 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 2 October 2026.
Map and rules
How is test configured, and what rules are in force?
Check: gather rate. The name test does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.
What map is test on?
Check: map. Procedural, generated by the game, on test.
Connection
What do you do to join test?
Press F1 in Rust and enter client.connect 77.48.47.4:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.