RS-15955Community server
typical TESTING
Offline 9.195.144.165:21000 checked 7d 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 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.
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 TESTING?
typical TESTING is offline at this moment; the last signal was 7 days 19 hours ago.
Where does typical TESTING sit in the rankings?
Ranked #15,955 on seven-day player hours, typical TESTING is in the top 72% of all ranked servers.
Tags, lists, and filters
Where does typical TESTING show up in Top Rust Servers lists and filters?
These Top Rust Servers lists include typical TESTING: Best Rust community servers. It appears under these filters 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 TESTING?
The game's server browser reads the tags that typical TESTING publishes: gmrust (Game mode): Survival follows the standard Rust ruleset; mp40 (Max players): Player slots: 40; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): To join, your game must be on protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): The region code is left blank. Shown at the top of this page, and also in the tags: its players now, its queue, and the time its world was made.
Settings and map
Which map is running on typical TESTING?
typical TESTING uses a procedural map, which the game generates.
Which settings and rules apply on typical TESTING?
You will not find a gather rate in the name typical TESTING. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid in the standard game. Player versus player combat and raiding are enabled. It appears under Community in the server browser and is a community server. The server runs with VAC on.
Server info
What version is typical TESTING running?
On Linux, typical TESTING operates Rust network protocol 2634 and build 166652. The protocol must match for you to join; Steam will update your game.
What is the location of typical TESTING?
No region is published by typical TESTING. 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:21000.
How reliable is typical TESTING?
Currently offline is typical TESTING, last seen 7 days 19 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 7 October 2026.
Wipe details
How often does typical TESTING wipe?
The record holds too few wipes to determine typical TESTING's pattern. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. Its world was last replaced 8 days 1 hours ago.
Joining the server
How can I connect to typical TESTING?
To connect manually, open the console with F1 and type client.connect 9.195.144.165:21000. Or click Launch Rust on this page to open Rust through Steam and connect directly.