TEST
Offline 2.63.25.148:28015 checked 41d 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 bestWipe 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- 231/250
- 15/250
- 23/250
- 113/200
- 45/200
- 43/100
Quick answers
from the figures on this pageWipe schedule
When does TEST wipe?
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 in play was created 41 days 16 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): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. 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?
On Rust Metrics, TEST sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under 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: #13,352 on seven-day player hours, top – of all ranked servers.
What player count does TEST carry?
Status for TEST: offline. Last seen 41 days 15 hours ago.
Server details
Which location does TEST run from?
No region comes from TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 2.63.25.148:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 163794 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.
What is the uptime on TEST, and is it online?
Reading: offline. TEST last answered 41 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 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. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.
Which map is live on TEST?
Check: map. Procedural, generated by the game, on TEST.
How to join
How do you connect to TEST?
Press F1 in Rust and enter client.connect 2.63.25.148:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.