Offline 91.83.37.40:28015 checked 38d ago
TEST SERVER
Connect
srv = rust.server("91.83.37.40:28017")
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. 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 bestWipe 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 91.83.37.40:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Sep 2026, 18:19 UTC
- hostname
- –
- first seen
- 19 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 | ShockRust | Blue | NoLimit | no group limit · 161 on average | 33/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 39/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 17/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 7/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 5/1000 |
Quick answers
From the figures on this page.
Population data
What position does TEST SERVER take in the server rankings?
Rank #13,747 on seven-day player hours for TEST SERVER, within the top – of all ranked servers.
How many players does TEST SERVER hold at once?
The current row shows TEST SERVER offline; the last response was 38 days 12 hours ago.
About the server
What is the Rust version on TEST SERVER?
Rust network protocol 2633 and build 162929 on Windows is what TEST SERVER runs. Steam updates your game for you, but the protocol must match to join.
How reliable is TEST SERVER, and is it up?
TEST SERVER is offline at this refresh; the last response came 38 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 19 September 2026.
Where does TEST SERVER sit?
For TEST SERVER, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 91.83.37.40:28015.
Settings and map
What rules and settings are recorded for TEST SERVER?
The name TEST SERVER carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is not running; Valve's anti-cheat is off.
What is the map on TEST SERVER?
TEST SERVER runs a procedural map, which the game generates.
Wipe schedule
On what schedule does TEST SERVER wipe?
A rhythm cannot be read from the wipes of TEST SERVER on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 54 days 8 hours ago.
Tags and filters
Where does TEST SERVER appear among Rust Data lists and filters?
These Rust Data lists include TEST SERVER: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on TEST SERVER?
Read by the game's server browser, the tags TEST SERVER publishes are: gmvanilla (Game mode): Survival in vanilla form; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs162929 (Build): Build number: 162929; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 TEST SERVER?
Enter client.connect 91.83.37.40:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.