typical TESTING
Offline 9.195.144.165:21000 checked 22d ago
Measurements
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
Top 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
| 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.
Quick answers
Population
How does typical TESTING rank against other Rust servers?
Over the past week it ranks #15,955 for player hours, which puts typical TESTING in the top 72% of all ranked servers.
How busy is typical TESTING?
At this count typical TESTING is offline, with its last sighting 22 days 6 hours ago.
Lists and tags
What do the server tags on typical TESTING mean?
These are the tags typical TESTING publishes, as read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): The server has 40 slots; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): The protocol is 2634; a different version will not connect; cs166652 (Build): This server runs game build 166652; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.
Which Rust Population lists and filters include typical TESTING?
These Rust Population lists include typical TESTING: Community servers, field-listed. Filter the server list by Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more and it will show up.
Wipe schedule
What is the wipe schedule on typical TESTING?
Too few wipes are on record for typical TESTING to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. Counted from 22 days 12 hours ago, that is how long the current world has stood.
Map and rules
Which map does typical TESTING run?
typical TESTING uses a map the game generates: procedural.
What are the rules and settings on typical TESTING?
The name tells you nothing about gather rates: typical TESTING states none. No limit is set beyond the standard 8 players per group. You get survival here, gather, build and raid, as in the standard game. Combat between players, raids included, is permitted. You will find it under Community: it is a community server. VAC, Valve's anti-cheat, runs here.
About the server
Which version of Rust does typical TESTING run?
On Linux, typical TESTING runs Rust network protocol 2634 and build 166652. Your game needs the same protocol to join; Steam takes care of updating it.
Is typical TESTING online, and how reliable is it?
We last saw typical TESTING 22 days 6 hours ago, and it is offline now. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. The first sighting by Rust Population was on 7 October 2026.
Where is typical TESTING located?
No region is published by typical TESTING. The location a server claims is what Rust Population shows, not the place where the machine stands. Connect at 9.195.144.165:21000.
Getting in
How do I join typical TESTING?
Open the console with F1 in Rust and enter client.connect 9.195.144.165:21000. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.