Test
Offline 185.244.213.67:28015 checked 27d 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 69% 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- 206/250
- 287/300
- 764/800
- 45/100
- 861/900
- 690/725
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
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 27 days 23 hours ago.
Lists and filters
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): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): Build 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from Test. 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. 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.
Player count
What position does Test hold among Rust servers?
Player hours over seven days put Test at #16,013, in the top 69% of all ranked servers.
How full does Test get?
Status for Test: offline. Last seen 27 days 23 hours ago.
Operator and location
Where does Test sit?
Reading: location. Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 185.244.213.67:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 166494, Windows. Check: protocol. To join, your game must match; Steam handles the update.
Is Test up, and how often does it stay up?
Check: connection. Test is offline at this moment. Last contact was 27 days 23 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 1 October 2026.
Rules and settings
What rules does Test enforce, and what are its settings?
Check: gather rate. The name Test does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is Test on?
The game generates a procedural map for Test.
How to join
How do you connect to Test?
Check: join. Open Rust, press F1, then enter client.connect 185.244.213.67:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.