typical TEST
Offline 192.255.237.203:28017 checked 29d 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
- 182/ 200
- 475/ 450
- 613/ 675
- 198/ 225
- 220/ 275
- 122/ 200
Quick answers
Tags and filters
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.
How should you read the tags on typical TEST?
The server browser shows these tags for typical TEST: gmrust (Game mode): This is the standard Rust survival experience; mp100 (Max players): It holds 100 players; ts8 (Group limit): The default team size of 8 applies here; 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. 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. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 192.255.237.203:28017.
What's the uptime like for typical TEST?
typical TEST is down at the moment; it was last up 29 days 2 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. Rust Going Deep has had it on record since 18 September 2026.
What Rust version is typical TEST on?
The version on typical TEST is Rust network protocol 2633 and build 164530, on Linux. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
How often does typical TEST wipe?
typical TEST's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 30 days 2 hours ago.
Settings and map
What settings are in place on typical TEST?
No gather rate appears in the name of typical TEST. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. 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?
typical TEST uses a procedural map of size 1,000 with seed 6738, made by the game. You can see it on RustMaps from this page, since the same size and seed produce the same map.
Population
What's the population like on typical TEST?
The last sighting of typical TEST was 29 days 2 hours ago; it is offline right now.
What position does typical TEST hold in the server rankings?
Over the last seven days, typical TEST is #15,490 by player hours, among the top 69% of all ranked servers.
Getting in
What's the process to join 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:28017.