RS-15962Community server
typical TEST
Offline 9.195.144.101:20003 checked 9d 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
Top 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
| 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.
Quick answers
From the figures on this page.
Player activity
How many players are usually on typical TEST?
typical TEST is offline at this moment; the last signal was 9 days 20 hours ago.
What is the ranking of typical TEST?
The last seven days of player hours place typical TEST at #15,962, in the top 71% of ranked servers.
Tags and filters
Where does typical TEST show up in Top Rust Servers lists and filters?
These Top Rust Servers lists include typical TEST: Best Rust community servers. These are the filters that bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on typical TEST?
gmrust (Game mode): Survival follows the standard Rust ruleset; mp100 (Max players): There are 100 slots; ts8 (Group limit): At most 8 per team, as standard in the game; v2634 (Protocol): This server runs protocol 2634; match it to connect; cs166652 (Build): The game build is 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is assigned are the tags typical TEST publishes, and the game's server browser reads them. At the top of this page you also see its players now, its queue, and the time its world was made, taken from the tags.
Settings and map
What map is used on typical TEST?
typical TEST uses a procedural map, which the game generates.
Which settings and rules apply on typical TEST?
You will not find a gather rate in the name typical TEST. The group limit is the game's default of 8 players. You play survival, the normal mode where you gather, build and raid. Combat and raiding between players are allowed. The server browser shows it under Community. The server runs with VAC on.
Server info
What is the Rust version on typical TEST?
Rust network protocol 2634 and build 166652 is what typical TEST runs, on Linux. The protocol must match for you to join; Steam will update your game.
What is the server location for typical TEST?
A region is not published by typical TEST. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. It answers at 9.195.144.101:20003.
What is the uptime of typical TEST?
typical TEST is offline now; the last time it was seen was 9 days 20 hours ago. Across the last 7 full days, it was online for 0 of 168 hours, or 0%. The first time Top Rust Servers saw it was on 4 October 2026.
Wipe schedule
On what schedule does typical TEST wipe?
Not enough wipe data exists yet to identify the rhythm of typical TEST. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. The present world has been live since 11 days 18 hours ago.
Joining the server
How can I connect to typical TEST?
Use the console: open Rust, press F1, and type client.connect 9.195.144.101:20003. Or simply click Launch Rust here; it opens the game through Steam and connects you.