Test
Offline 46.138.149.57:28015 checked 36d 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 67% 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- 248/250
- 172/225
- 19/250
- 22/250
- 23/100
- 78/200
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Test follow?
Its rhythm cannot be told from the wipes of Test on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 55 days 9 hours ago the current world was made.
Tag meanings
Which tags does Test carry, and what do they mean?
These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163493 (Build): Game build reading: 163493; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. 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
What position does Test hold among Rust servers?
Ranking for Test: #15,470 on seven-day player hours, top 67% of all ranked servers.
What is the population on Test?
Test is not responding; status offline, last seen 36 days 9 hours ago.
Operator and location
What location is Test hosted in?
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 46.138.149.57:28015.
What Rust version is Test on?
Rust network protocol 2633 and build 163493 on Windows is the build Test runs. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Test, and is it online now?
Test reports offline. The last reading came 36 days 9 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 22 September 2026.
Settings and map
How is Test configured, and what rules are in force?
Reading the name gives no gather rate for Test. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Test?
The game generates a procedural map for Test.
Connection
How do you connect to Test?
Check: join. Open Rust, press F1, then enter client.connect 46.138.149.57:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.