TEST
Offline 95.24.166.123:28015 checked 21d 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 71% 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- 270/300
- 16/250
- 34/250
- 117/200
- 45/200
- 50/100
Quick answers
from the figures on this pageReset cycle
What wipe timing does TEST follow?
The rhythm of TEST's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 21 days 15 hours ago.
Tags
Which tags does TEST carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from TEST. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show TEST?
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
Where does TEST sit in the rankings?
Ranking for TEST: #15,982 on seven-day player hours, top 71% of all ranked servers.
What is the population on TEST?
Status for TEST: offline. Last seen 21 days 14 hours ago.
Operator and location
Which location does TEST run from?
No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 95.24.166.123:28015.
What Rust version is TEST on?
Rust network protocol 2634 and build 166652 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.
Is TEST up, and how often does it stay up?
TEST reports offline. The last reading came 21 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 6 October 2026, recorded by Rust Metrics.
Settings and map
How is TEST configured, and what rules are in force?
No gather rate appears in the name: TEST. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
What map is TEST on?
The game generates a procedural map for TEST.
Join
How do you connect to TEST?
Press F1 in Rust and enter client.connect 95.24.166.123:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.