typical TEST
Offline 192.255.237.203:28021 checked 39d 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, measured since 18 Sep. 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- 636/675
- 485/525
- 59/250
- 36/250
- 138/200
- 255/300
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 40 days 13 hours ago.
Lists and filters
How should you read the tags on typical TEST?
These are the tags typical TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 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; cs164530 (Build): Build 164530; 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 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.
Player count
What position does typical TEST hold among Rust servers?
Ranking for typical TEST: #15,490 on seven-day player hours, top 69% of all ranked servers.
What player count does typical TEST carry?
Reading for typical TEST: offline at this moment; last seen 39 days 14 hours ago.
Server
Which location does typical TEST run from?
No region tag on typical TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 192.255.237.203:28021.
What Rust version is typical TEST on?
Version check: Rust network protocol 2633 and build 164530 on Linux, run by typical TEST. Check: protocol. To join, your game must match; Steam handles the update.
Is typical TEST up, and how often does it stay up?
Reading: offline. typical TEST last answered 39 days 14 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 18 September 2026.
Rules and settings
How is typical TEST configured, and what rules are in force?
No gather rate appears in the name: typical TEST. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
What map is typical TEST on?
Check: map. Procedural, size 1,000, seed 6738, generated by the game on typical TEST. View it on RustMaps from this page: matching size and seed give an identical map.
Connection
How can you get onto typical TEST?
Press F1 in Rust and enter client.connect 192.255.237.203:28021. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.