RS-15974Community server
typical Test2
Offline 9.195.144.165:20000 checked 6d 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 populated is typical Test2?
typical Test2 is offline at this moment; the last signal was 6 days 18 hours ago. The average over the last seven days comes to 0 players.
What is the ranking of typical Test2?
The last seven days of player hours place typical Test2 at #15,974, in the top 71% of ranked servers.
Tags and filters
On Top Rust Servers, which lists and filters carry typical Test2?
These Top Rust Servers lists count typical Test2 among their servers: 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.
What is the meaning of the tags on typical Test2?
The game's server browser reads the tags that typical Test2 publishes: gmrust (Game mode): Standard survival, as in Rust; mp40 (Max players): It has 40 slots; ts8 (Group limit): At most 8 per team, as standard in the game; v2634 (Protocol): Protocol 2634 is required to join; your game must be on the same version; cs166652 (Build): Running game build 166652; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): Region code not set. 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.
Rules, settings, and map
What map is used on typical Test2?
A procedural map, created by the game, is in use on typical Test2.
What does typical Test2 run for rules and settings?
The name typical Test2 does not state a gather rate. Groups use the default maximum of 8 players. You play survival, the normal mode where you gather, build and raid. Player versus player combat and raiding are enabled. The server browser shows it under Community. The server runs with VAC on.
Server details
What Rust version is typical Test2 on?
On Linux, typical Test2 operates Rust network protocol 2634 and build 166652. The protocol must match for you to join; Steam will update your game.
Where can typical Test2 be found?
A region is not published by typical Test2. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. You reach it at 9.195.144.165:20000.
How reliable is typical Test2?
Currently offline is typical Test2, last seen 6 days 18 hours ago. Across the last 7 full days, it was online for 3 of 168 hours, or 2%. It was first observed by Top Rust Servers on 6 October 2026.
Wipe schedule
On what schedule does typical Test2 wipe?
Too few wipes are recorded for typical Test2 to establish a rhythm. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. The world it is running now dates from 8 days 19 hours ago.
Joining the server
How can I connect to typical Test2?
Use the console: open Rust, press F1, and type client.connect 9.195.144.165:20000. Or simply click Launch Rust here; it opens the game through Steam and connects you.