RS-16490Community server
typical TEST
Offline 9.244.18.186:30000 checked 18d 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 many players are usually on typical TEST?
Currently, typical TEST is offline; the last sighting was 18 days 9 hours ago.
How is typical TEST ranked?
The last seven days of player hours place typical TEST at #16,490, in the top 71% of ranked servers.
Server tags and lists
Where does typical TEST appear among the Top Rust Servers lists and filters?
On these Top Rust Servers lists you will find 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.
How should you read the tags on typical TEST?
Published by typical TEST for the game's server browser to read: 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; v2633 (Protocol): This server runs protocol 2633; match it to connect; cs165217 (Build): Game build: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $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 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. Up to 8 players per group, as the game defaults. You play survival, standard survival: gathering, building and raiding. Combat and raiding between players are allowed. It appears under Community in the server browser and is a community server. The server runs with VAC on.
About the server
What version is typical TEST running?
Rust network protocol 2633 and build 165217 is what typical TEST runs, on Linux. The protocol must match for you to join; Steam will update your game.
Where can typical TEST be found?
A region is not published by typical TEST. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. 9.244.18.186:30000 is its address.
What is the uptime of typical TEST?
typical TEST is offline now; the last time it was seen was 18 days 9 hours ago. Across the last 7 full days, it was online for 0 of 168 hours, or 0%. It was first observed by Top Rust Servers on 25 September 2026.
Wipe schedule
How often does typical TEST wipe?
Not enough wipe data exists yet to identify the rhythm of typical TEST. The monthly force wipe applies to every Rust server; the next one is on Thursday 5 November at 19:00 UTC. The world it is running now dates from 18 days 21 hours ago.
Joining the server
What is the process to join typical TEST?
To connect manually, open the console with F1 and type client.connect 9.244.18.186:30000. Or click Launch Rust on this page to open Rust through Steam and connect directly.