typical TESTING
Offline 9.195.144.165:21000 checked 10d ago
Players
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
- 457/ 425
- 581/ 600
- 331/ 425
- 709/ 750
- 108/ 200
- 324/ 325
Quick answers
Tags and search
Where does typical TESTING appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include typical TESTING: Rust community servers, going deep. You can find it on the server list by these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
What's the meaning of the tags on typical TESTING?
gmrust (Game mode): Survival, as standard Rust does it; mp40 (Max players): It holds 40 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game has to be on protocol 2634; cs166652 (Build): It's on build 166652; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty — that is the tag list typical TESTING puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What's the location of typical TESTING?
There is no published region for typical TESTING. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 9.195.144.165:21000.
Is typical TESTING up, and how often does it stay online?
typical TESTING is down at the moment; it was last up 10 days 22 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 7 October 2026.
What Rust version is typical TESTING on?
Rust network protocol 2634 and build 166652 is what typical TESTING runs, on Linux. The protocol must match to join; Steam will update your game.
Wipe details
How often does typical TESTING wipe?
The wipes recorded for typical TESTING are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 11 days 4 hours is how long ago this world came into being.
Settings and map
What settings are in place on typical TESTING?
Its name does not state a gather rate for typical TESTING. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. It sits under Community in the server browser: a community server. VAC is on: Valve's anti-cheat is active.
Which map is active on typical TESTING?
A procedural map, generated by the game, is in play on typical TESTING.
Player stats
How many players are on typical TESTING?
typical TESTING was last seen 10 days 22 hours ago and is offline as you read this.
What position does typical TESTING hold in the server rankings?
Over the last seven days, typical TESTING is #15,955 by player hours, among the top 72% of all ranked servers.
Join info
How do you get into typical TESTING?
To join, open Rust, hit F1, and enter client.connect 9.195.144.165:21000. Or click Launch Rust on this page to open the game through Steam and connect.