typical [TEST]
Offline 9.244.19.246:28017 checked 42d 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- 196/250
- 182/200
- 16/250
- 14/250
- 15/100
- 90/200
Quick answers
from the figures on this pageWipe timing
What wipe timing does typical [TEST] follow?
To tell the rhythm of typical [TEST], too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 47 days 10 hours ago.
Tags
Which tags does typical [TEST] carry, and what do they mean?
Tags published by typical [TEST], read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is 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 typical [TEST]?
Rust Metrics lists featuring typical [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.
Population
What position does typical [TEST] hold among Rust servers?
Ranking for typical [TEST]: #15,521 on seven-day player hours, top – of all ranked servers.
What is the population on typical [TEST]?
Status for typical [TEST]: offline. Last seen 42 days 11 hours ago.
Server
Where does typical [TEST] sit?
Reading: location. typical [TEST] gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 9.244.19.246:28017.
What Rust version is typical [TEST] on?
Rust network protocol 2633 and build 163794 on Linux is the build typical [TEST] runs. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is typical [TEST], and is it online now?
typical [TEST] reports offline. The last reading came 42 days 11 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 15 September 2026.
Settings and map
How is typical [TEST] configured, and what rules are in force?
No gather rate appears in the name: typical [TEST]. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. 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.
Which map is live on typical [TEST]?
Check: map. Procedural, generated by the game, on typical [TEST].
Join
How do you connect to typical [TEST]?
Press F1 in Rust and enter client.connect 9.244.19.246:28017. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.