typical TESTING
Offline 15.204.83.240:21000 checked 15d 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 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% 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- 366/425
- 457/500
- 980/1000
- 53/100
- 964/1000
- 32/250
Quick answers
from the figures on this pageWipe schedule
What wipe timing does typical TESTING follow?
Its rhythm cannot be told from the wipes of typical TESTING 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. 22 days 10 hours ago the current world was made.
Tag meanings
Which tags does typical TESTING carry, and what do they mean?
Tags published by typical TESTING, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): 40 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. 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 TESTING?
These Rust Metrics lists carry typical TESTING: 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 TESTING hold among Rust servers?
Ranking for typical TESTING: #15,244 on seven-day player hours, top 71% of all ranked servers.
What is the population on typical TESTING?
typical TESTING is not responding; status offline, last seen 15 days 18 hours ago.
Server
Where does typical TESTING sit?
No region tag on typical TESTING. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 15.204.83.240:21000.
What Rust version is typical TESTING on?
Version check: Rust network protocol 2634 and build 167398 on Linux, run by typical TESTING. To get in, your game needs the same protocol; Steam applies the update.
Is typical TESTING up, and how often does it stay up?
Reading: offline. typical TESTING last answered 15 days 18 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 8 October 2026.
Map and rules
How is typical TESTING configured, and what rules are in force?
No gather rate appears in the name: typical TESTING. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is typical TESTING on?
Size 1,000 and seed 1: the game generates the procedural map on typical TESTING from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Connection
What do you do to join typical TESTING?
Check: join. Open Rust, press F1, then enter client.connect 15.204.83.240:21000. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.