RS-15490Community server
typical TEST
Offline 192.255.237.203:28017 checked 25d 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, measured since 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 69% 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 TEST?
typical TEST is offline at this moment; the last signal was 25 days 4 hours ago.
What is the ranking of typical TEST?
On player hours across seven days, typical TEST is #15,490, inside the top 69% of all ranked servers.
Tags, lists, and filters
Where does typical TEST show up in Top Rust Servers lists and filters?
These Top Rust Servers lists include typical TEST: 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.
How should you read the tags on typical TEST?
gmrust (Game mode): Standard survival, as in Rust; mp100 (Max players): Player slots: 100; ts8 (Group limit): At most 8 per team, as standard in the game; v2633 (Protocol): This server runs protocol 2633; match it to connect; cs164530 (Build): Game build: 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is assigned are the tags typical TEST publishes, and the game's server browser reads them. 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.
Settings and map
What is the map on typical TEST?
A procedural map of size 1,000 with seed 6738, created by the game, is in use on typical TEST. Viewing it on RustMaps is possible from this page: the same size and seed give the same map.
What settings and rules does typical TEST use?
You will not find a gather rate in the name typical TEST. Up to 8 players per group, as the game defaults. survival is the game mode, the normal mode where you gather, build and raid. Combat and raiding between players are allowed. The server browser shows it under Community. The server runs with VAC on.
Server info
What Rust version is typical TEST on?
Rust network protocol 2633 and build 164530 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. It answers at 192.255.237.203:28017.
How reliable is typical TEST?
typical TEST is offline now; the last time it was seen was 25 days 4 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 18 September 2026.
Wipe schedule
How often does typical TEST wipe?
Too few wipes are recorded for typical TEST to establish a rhythm. 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 26 days 3 hours ago.
Connection
What is the process to join typical TEST?
Use the console: open Rust, press F1, and type client.connect 192.255.237.203:28017. Or simply click Launch Rust here; it opens the game through Steam and connects you.