Offline 97.96.54.22:28015 checked 33d ago
Poonzzi staging test
Connect
srv = rust.server("97.96.54.22: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 best
Top 57% 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 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 24 Sep, 00:32 UTC33d ago | 2 | 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
- 97.96.54.22:28015
- region
- –
- max players
- 3
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 00:32 UTC
- hostname
- –
- first seen
- 24 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 · 511 on average | 615/700 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 340 on average | 42/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 337 on average | 85/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 316 on average | 335/400 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 280 on average | 148/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 261 on average | 139/225 |
Quick answers
From the figures on this page.
Player counts
What position does Poonzzi staging test take in the server rankings?
Player hours over seven days put Poonzzi staging test at #12,574, in the top 57% of the ranked set.
How many players does Poonzzi staging test hold at once?
Offline now for Poonzzi staging test, with the last sample 33 days 18 hours ago.
Server data
What is the Rust version on Poonzzi staging test?
Rust network protocol 2633 and build 165542 on Windows is what Poonzzi staging test runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Poonzzi staging test, and is it online now?
Offline now for Poonzzi staging test, last seen 33 days 18 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 24 September 2026.
Which location does Poonzzi staging test run from?
No region is published by Poonzzi staging test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 97.96.54.22:28015.
Map and rules
Which settings and rules does Poonzzi staging test run?
The name Poonzzi staging 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 base game, where you gather, build and raid. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.
What is the map on Poonzzi staging test?
The game generates its map: procedural, on Poonzzi staging test.
Wipes and dates
When does Poonzzi staging test wipe, and on what schedule?
The record for Poonzzi staging test holds too few wipes to show a rhythm. 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 33 days 21 hours ago.
On Poonzzi staging test, what happens on wipe day?
Recent wipes averaged 2 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does Poonzzi staging test appear among Rust Data lists and filters?
On Rust Data, Poonzzi staging test appears in these lists: Rust community servers, unfiltered. It appears under these filters 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 Poonzzi staging test?
The game's server browser reads these tags from Poonzzi staging test: gmrust (Game mode): Survival play, standard Rust; mp3 (Max players): Slot count: 3; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165542 (Build): Build number: 165542; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into Poonzzi staging test?
In Rust, F1 opens the console: type client.connect 97.96.54.22:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.