typical TESTING
Offline 9.195.144.165:21000 checked 22d 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 72% 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- 152/250
- 192/250
- 572/675
- 32/100
- 659/775
- 550/625
Quick answers
from the figures on this pageWipe timing
When does typical TESTING wipe?
To tell the rhythm of typical TESTING, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 22 days 15 hours ago the current world was made.
Tag meanings
How should you read the tags on typical TESTING?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): 40 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Game build reading: 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from typical TESTING. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show typical TESTING?
On Rust Metrics, typical TESTING 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.
Population
Where does typical TESTING sit in the rankings?
Player hours over seven days put typical TESTING at #15,955, in the top 72% of all ranked servers.
How full does typical TESTING get?
Reading for typical TESTING: offline at this moment; last seen 22 days 9 hours ago.
Operator and location
Which location does typical TESTING run from?
Reading: location. typical TESTING gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 9.195.144.165:21000.
What Rust version is typical TESTING on?
Version check: Rust network protocol 2634 and build 166652 on Linux, run by typical TESTING. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on typical TESTING, and is it online?
Check: connection. typical TESTING is offline at this moment. Last contact was 22 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 7 October 2026.
Map and rules
What rules does typical TESTING enforce, and what are its settings?
Reading the name gives no gather rate for typical TESTING. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. 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 TESTING?
The game generates a procedural map for typical TESTING.
Join
How can you get onto typical TESTING?
Press F1 in Rust and enter client.connect 9.195.144.165:21000. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.