TEST
Offline 77.43.208.61:28015 checked 35d ago
Server instruments
no direct query in 48 hoursPlayers now
10% 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- 330/375
- 220/250
- 37/250
- 31/250
- 55/100
- 78/200
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 next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 35 days 8 hours ago the current world was made.
Tags
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): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165405 (Build): The server runs game build 165405; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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.
Where does TEST appear in Rust Metrics lists and filters?
Rust Metrics lists featuring 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.
Occupancy
What position does TEST hold among Rust servers?
Ranking for TEST: #13,182 on seven-day player hours, top 61% of all ranked servers.
What player count does TEST carry?
TEST is not responding; status offline, last seen 35 days 8 hours ago.
Operator and location
Which location does TEST run from?
Reading: location. TEST gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 77.43.208.61:28015.
What Rust version is TEST on?
Version check: Rust network protocol 2633 and build 165405 on Windows, run by TEST. Matching protocol is required to join. Let Steam update your game.
How reliable is TEST, and is it online now?
Check: connection. TEST is offline at this moment. Last contact was 35 days 8 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 23 September 2026.
Map and rules
How is TEST configured, and what rules are in force?
Reading the name gives no gather rate for TEST. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
Which map is live on TEST?
Procedural map on TEST, made by the game's generator.
How to join
How do you connect to TEST?
Check: join. Open Rust, press F1, then enter client.connect 77.43.208.61:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.