Offline 192.255.237.203:28021 checked 40d ago
typical TEST
Connect
srv = rust.server("192.255.237.203:28022")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
1000 · seed 6738- map
- Procedural Map
- size
- 1000
- seed
- 6738
Server
srv.info()- address
- 192.255.237.203:28021
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Sep 2026, 05:01 UTC
- hostname
- –
- first seen
- 18 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 491 on average | 72/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 106/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 284 on average | 320/350 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 16/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 403/450 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 253 on average | 299/325 |
Quick answers
From the figures on this page.
Population
What position does typical TEST take in the server rankings?
Player hours over seven days put typical TEST at #15,490, in the top 69% of the ranked set.
How many players does typical TEST hold at once?
typical TEST returns no live count at this refresh, having last been seen 40 days 21 hours ago.
Server facts
What is the Rust version on typical TEST?
The build is Rust network protocol 2633 and build 164530 on Linux, run by typical TEST. Steam updates your game for you, but the protocol must match to join.
How reliable is typical TEST, and is it up?
Offline now for typical TEST, last seen 40 days 21 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 18 September 2026.
Which location does typical TEST run from?
For typical TEST, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 192.255.237.203:28021.
Rules, settings, map
Which settings and rules does typical TEST run?
The name typical TEST carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat status: VAC on.
Which map has typical TEST selected?
Size 1,000, seed 6738: the procedural map on typical TEST, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does typical TEST wipe, and on what schedule?
A rhythm cannot be read from the wipes of typical TEST on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 41 days 20 hours ago.
Tags and filters
Which Rust Data filters and lists contain typical TEST?
These Rust Data lists include typical TEST: Rust community servers, unfiltered. 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 server tags on typical TEST?
The game's server browser reads these tags from typical TEST: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): The server runs build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into typical TEST?
In Rust, F1 opens the console: type client.connect 192.255.237.203:28021. Launch Rust on this page does the same by opening the game through Steam and connecting.