typical TEST
Offline 192.255.237.203:28015 checked 28d 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
daily · 1 is bestTop 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
newest first| 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
- 383/ 450
- 192/ 200
- 593/ 600
- 318/ 325
- 313/ 325
- 400/ 450
Quick answers
Tags and listings
Where does typical TEST appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry typical TEST are: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What's the meaning of the tags on typical TEST?
gmrust (Game mode): This is the standard Rust survival experience; mp100 (Max players): The slot count is 100; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs164530 (Build): It's on build 164530; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty — that is the tag list typical TEST puts out for the game's server browser. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server info
What's the location of typical TEST?
No region comes from typical TEST. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 192.255.237.203:28015.
Is typical TEST up, and how often does it stay online?
The server typical TEST is not reachable at the moment; the last sighting was 28 days 16 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 18 September 2026.
What is the Rust version for typical TEST?
On Linux, typical TEST runs Rust network protocol 2633 and build 164530. The protocol must match to join; Steam will update your game.
Wipe details
How often does typical TEST wipe?
Too few wipes are on record for typical TEST to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 30 days 14 hours is how long ago this world came into being.
Rules and settings
Which rules and settings is typical TEST running?
The name of typical TEST contains no gather rate. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser lists it under Community, making it a community server. The server runs Valve's anti-cheat, VAC.
What's the map on typical TEST?
A game-generated procedural map of size 1,000 with seed 6738 is in play on typical TEST. You can see it on RustMaps from this page, since the same size and seed produce the same map.
Player stats
What's the population like on typical TEST?
The last sighting of typical TEST was 28 days 16 hours ago; it is offline right now.
Where does typical TEST sit in the rankings?
For player hours in the last seven days, typical TEST ranks #15,490, within the top 69% of ranked servers.
How to join
How do you get into typical TEST?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 192.255.237.203:28015.