typical test
Offline 15.204.83.240:20999 checked 9d 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 11 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% 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- 160/500
- 120/100
- 191/225
- 97/700
- 230/700
- 345/350
Quick answers
from the figures on this pageWipe timing
How often does typical test wipe, and when?
The rhythm of typical 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. 17 days 21 hours ago the current world was made.
Tags
Which tags does typical test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server from typical test. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does typical test appear in Rust Metrics lists and filters?
These Rust Metrics lists carry typical test: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does typical test hold among Rust servers?
Ranking for typical test: #15,379 on seven-day player hours, top 70% of all ranked servers.
How full does typical test get?
Reading for typical test: offline at this moment; last seen 9 days ago.
Operator and location
Which location does typical test run from?
No region comes from typical test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 15.204.83.240:20999.
What Rust version is typical test on?
Reading: typical test, Rust network protocol 2634 and build 167398, Linux. Matching protocol is required to join. Let Steam update your game.
What is the uptime on typical test, and is it online?
Reading: offline. typical test last answered 9 days 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 11 October 2026.
Map and rules
How is typical test configured, and what rules are in force?
Reading the name gives no gather rate for typical test. 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. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.
Which map is live on typical test?
Check: map. Procedural, size 1,000, seed 6738, generated by the game on typical test. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
How can you get onto typical test?
Check: join. Open Rust, press F1, then enter client.connect 15.204.83.240:20999. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.