test
Offline 114.33.108.48: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- 287/300
- 228/250
- 21/250
- 23/250
- 27/100
- 110/200
Quick answers
from the figures on this pageReset cycle
How often does test wipe, and when?
Its rhythm cannot be told from the wipes of test on record: there are too few. 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 21 days 22 hours ago.
Tags
How should you read the tags on test?
Check: tags. The game's server browser reads 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): Protocol 2634: join only on the same game version; cs166652 (Build): The server runs game build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $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.
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.
Population
Where does test sit in the rankings?
Player hours over seven days put test at #15,960, in the top 71% of all ranked servers.
What player count does test carry?
test is not responding; status offline, last seen 21 days 22 hours ago.
Operator and location
Where does test sit?
No region comes from test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 114.33.108.48:28015.
What Rust version is test on?
Version check: Rust network protocol 2634 and build 166652 on Windows, run by test. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is test, and is it online now?
Reading: offline. test last answered 21 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 7 October 2026.
Settings and map
How is test configured, and what rules are in force?
Check: gather rate. The name test does not state one. 8 players per group, the default value. 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?
Check: map. Procedural, generated by the game, on test.
How to join
How do you connect to test?
Check: join. Open Rust, press F1, then enter client.connect 114.33.108.48:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.