RS-15521Community server
typical [TEST]
Offline 9.244.19.246:28017 checked 27d 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
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
What is the typical player count on typical [TEST]?
typical [TEST] is offline at this moment; the last signal was 27 days 17 hours ago.
What is the ranking of typical [TEST]?
On player hours across seven days, typical [TEST] is #15,521, inside the top – of all ranked servers.
Tags and filters
On Top Rust Servers, which lists and filters carry typical [TEST]?
These Top Rust Servers lists count typical [TEST] 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.
What is the meaning of the tags on typical [TEST]?
gmrust (Game mode): Standard survival, as in Rust; mp100 (Max players): Player slots: 100; ts8 (Group limit): The team limit is 8, which is the game default; v2633 (Protocol): Protocol 2633 is required to join; your game must be on the same version; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): Region code not set are the tags typical [TEST] publishes, and the game's server browser reads them. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.
Map and rules
What is the map on typical [TEST]?
A procedural map, created by the game, is in use on typical [TEST].
What does typical [TEST] run for rules and settings?
The name typical [TEST] does not state a gather rate. Groups use the default maximum of 8 players. It runs survival, standard survival: gathering, building and raiding. 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 details
What is the Rust version on typical [TEST]?
Rust network protocol 2633 and build 163794 is what typical [TEST] runs, on Linux. Joining requires matching protocols, and Steam updates your game automatically.
Where can typical [TEST] be found?
There is no region published by typical [TEST]. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. 9.244.19.246:28017 is its address.
What is the uptime of typical [TEST]?
The server typical [TEST] is down at the moment, with its last appearance 27 days 17 hours ago. It spent 0 of the last 168 hours online across 7 days, giving 0% uptime. It was first observed by Top Rust Servers on 15 September 2026.
Wipe details
How often does typical [TEST] wipe?
The record holds too few wipes to determine typical [TEST]'s pattern. Every Rust server is wiped by the force wipe each month; the next occurs on Thursday 5 November at 19:00 UTC. Its world was last replaced 32 days 15 hours ago.
Connection
What is the process to join typical [TEST]?
Use the console: open Rust, press F1, and type client.connect 9.244.19.246:28017. Or simply click Launch Rust here; it opens the game through Steam and connects you.