RS-15490Community server
typical TEST
Offline 192.255.237.203:28015 checked 24d 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 many players are usually on typical TEST?
Currently, typical TEST is offline; the last sighting was 24 days 22 hours ago.
How is typical TEST ranked?
The last seven days of player hours place typical TEST at #15,490, in the top 69% of ranked servers.
Tags 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. 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.
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): The team limit is 8, which is the game default; v2633 (Protocol): This server runs protocol 2633; match it to connect; cs164530 (Build): Running game build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region code is left blank 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 map is used on typical TEST?
The map on typical TEST is procedural, size 1,000, seed 6738, and generated by the game. You can look at the map on RustMaps from this page, because size and seed determine the map.
What settings and rules does typical TEST use?
The name typical TEST does not state a gather rate. Groups use the default maximum of 8 players. It runs survival, gather, build and raid in the standard game. 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.
Server info
What version is typical TEST running?
typical TEST uses Rust network protocol 2633 and build 164530 with Linux as its system. The protocol must match for you to join; Steam will update your game.
Where can typical TEST be found?
There is no region 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:28015.
What is the uptime of typical TEST?
Currently offline is typical TEST, last seen 24 days 22 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?
The record holds too few wipes to determine typical TEST's pattern. 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 26 days 19 hours ago.
Joining the server
How can I connect to typical TEST?
To connect, start Rust, hit F1, and enter client.connect 192.255.237.203:28015. You can also join by clicking Launch Rust here, which opens Rust through Steam and links you in.