Test
Offline 2.213.2.148:28015 checked 38d 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 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- 270/300
- 16/250
- 34/250
- 117/200
- 45/200
- 50/100
Quick answers
from the figures on this pageWipe schedule
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 in play was created 38 days 6 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; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; 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?
These Rust Metrics lists carry Test: Rust community servers: live readings. These filters bring it up on the server list: 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: #15,441 on seven-day player hours, top – of all ranked servers.
How full does Test get?
Status for Test: offline. Last seen 38 days 2 hours ago.
Operator and location
Which location does Test run from?
Reading: location. Test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 2.213.2.148:28015.
What Rust version is Test on?
Rust network protocol 2633 and build 164530 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?
Check: connection. Test is offline at this moment. Last contact was 38 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 19 September 2026.
Map and rules
What rules does Test enforce, and what are its settings?
Reading the name gives no gather rate for Test. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. 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 can you get onto Test?
Press F1 in Rust and enter client.connect 2.213.2.148:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.