Offline 31.76.104.81:28015 checked 27d ago
Staging Plugin Test
Connect
srv = rust.server("31.76.104.81: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 bestTop 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 16:52 UTC27d ago | 1 | NaN | running | 0 |
# 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
- 31.76.104.81:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 16:52 UTC
- hostname
- –
- first seen
- 1 Oct 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 · 157 on average | 103/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 125/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 97/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 27/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
Quick answers
From the figures on this page.
Population
How does Staging Plugin Test compare in the rankings?
Rank #15,790 on seven-day player hours for Staging Plugin Test, within the top 68% of all ranked servers.
What population does Staging Plugin Test carry?
Offline now for Staging Plugin Test, with the last sample 27 days 2 hours ago.
Server facts
Which Rust version is Staging Plugin Test on?
Rust network protocol 2634 and build 166493 on Windows is what Staging Plugin Test runs. Joining needs the same protocol on your game; Steam handles the update.
Is Staging Plugin Test up, and what does its uptime show?
The latest sample has Staging Plugin Test offline, with a last sighting 27 days 2 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 1 October 2026.
Which location does Staging Plugin Test run from?
No region is published by Staging Plugin Test. 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 31.76.104.81:28015.
Settings and map
What rules and settings are recorded for Staging Plugin Test?
The name Staging Plugin Test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has Staging Plugin Test selected?
Staging Plugin Test runs a procedural map, which the game generates.
Wipe schedule
When does Staging Plugin Test wipe, and on what schedule?
A rhythm cannot be read from the wipes of Staging Plugin Test on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 27 days 4 hours ago, and that is the one in play.
On Staging Plugin Test, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 2 hours in.
Tags and filters
Which lists on Rust Data hold Staging Plugin Test, and which filters?
These Rust Data lists include Staging Plugin Test: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Staging Plugin Test hold?
The game's server browser reads these tags from Staging Plugin Test: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166493 (Build): Recorded game build: 166493; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into Staging Plugin Test?
In Rust, F1 opens the console: type client.connect 31.76.104.81:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.