RS-15956Community server
typical Test2
Offline 9.195.144.101:20000 checked 8d 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.
Population
How populated is typical Test2?
typical Test2 is offline at this moment; the last signal was 8 days 18 hours ago.
What is the ranking of typical Test2?
The last seven days of player hours place typical Test2 at #15,956, in the top 71% of ranked servers.
Tags, lists, and filters
On Top Rust Servers, which lists and filters carry typical Test2?
On these Top Rust Servers lists you will find typical Test2: Best Rust community servers. 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; Last wipe: In the last 2 weeks.
What is the meaning of the tags on typical Test2?
Published by typical Test2 for the game's server browser to read: 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): This server runs protocol 2634; match it to connect; cs166652 (Build): The game build is 166652; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): No region code is assigned. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.
Rules, settings, and map
What is the map on typical Test2?
typical Test2 uses a procedural map, which the game generates.
What settings and rules does typical Test2 use?
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. A community server, it is found under the Community tab. VAC, Valve's anti-cheat, is enabled.
Server info
What is the Rust version on typical Test2?
typical Test2 uses Rust network protocol 2634 and build 166652 with Linux as its system. Joining requires matching protocols, and Steam updates your game automatically.
What is the server location for typical Test2?
No region is published by typical Test2. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. 9.195.144.101:20000 is its address.
What is the uptime of typical Test2?
Currently offline is typical Test2, last seen 8 days 18 hours ago. It spent 0 of the last 168 hours online across 7 days, giving 0% uptime. The first time Top Rust Servers saw it was on 5 October 2026.
Wipe cycle
On what schedule does typical Test2 wipe?
The record holds too few wipes to determine typical Test2's pattern. 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 9 days 14 hours ago.
How to join
How can I connect to typical Test2?
Use the console: open Rust, press F1, and type client.connect 9.195.144.101:20000. Or simply click Launch Rust here; it opens the game through Steam and connects you.