Test
Offline 89.208.22.43:28015 checked 44d 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- 222/250
- 15/250
- 18/250
- 130/200
- 44/200
- 41/100
Quick answers
from the figures on this pageWipe timing
What wipe timing does Test follow?
The rhythm of Test's wipes cannot be told yet: too few are on record. 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 44 days 14 hours ago.
Lists and filters
Which tags does Test carry, and what do they mean?
Tags published by Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Test?
On Rust Metrics, Test sits in these lists: 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 player count does Test carry?
Test is not responding; status offline, last seen 44 days 13 hours ago.
Server details
Which location does Test run from?
Reading: location. Test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 89.208.22.43:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2633 and build 163794, Windows. Matching protocol is required to join. Let Steam update your game.
How reliable is Test, and is it online now?
Check: connection. Test is offline at this moment. Last contact was 44 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
What rules does Test enforce, and what are its settings?
Check: gather rate. The name Test does not state one. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. 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?
Check: join. Open Rust, press F1, then enter client.connect 89.208.22.43:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.