Offline 104.28.24.176:28015 checked 5d ago
Local PvE: Pandora
Connect
srv = rust.server("104.28.24.176: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 63% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 9 Oct, 06:42 UTC20d ago | 1 | NaN | running | 0 |
| 1 | Sat 26 Sep, 13:39 UTC32d ago | 0 | NaN | 12.7 days | 0 |
| 2 | Fri 25 Sep, 18:28 UTC33d ago | 0 | NaN | 0.8 days | 1 |
# 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
- 104.28.24.176:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 06:42 UTC
- hostname
- –
- first seen
- 23 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 · 150 on average | 74/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 105/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 36/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Player counts
How does Local PvE: Pandora compare in the rankings?
Over the last seven days Local PvE: Pandora sits at #14,003 on player hours, in the top 63% of ranked servers.
What population does Local PvE: Pandora carry?
Local PvE: Pandora returns no live count at this refresh, having last been seen 5 days 16 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
What Rust version does Local PvE: Pandora run?
Rust network protocol 2635 and build 168909 on Linux is what Local PvE: Pandora runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Local PvE: Pandora, and is it online now?
Local PvE: Pandora is offline at this refresh; the last response came 5 days 16 hours ago. 3 of 168 hours up over the last 7 full days, or 2%. Rust Data logged it first on 23 September 2026.
Where does Local PvE: Pandora sit?
There is no region published for Local PvE: Pandora. Rust Data does not look up where the machine stands; it shows where a server says it is. 104.28.24.176:28015 is its address.
Settings and map
Which rules apply on Local PvE: Pandora, and what settings?
No gather rate appears in the name: Local PvE: Pandora. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. The VAC field reads off.
Which map has Local PvE: Pandora selected?
Local PvE: Pandora runs a procedural map, which the game generates.
Wipe schedule
When does Local PvE: Pandora wipe, and how often?
Local PvE: Pandora wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 20 days ago.
What is wipe day on Local PvE: Pandora like?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 1 hours in.
Tags and filters
Which Rust Data filters and lists contain Local PvE: Pandora?
These Rust Data lists include Local PvE: Pandora: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Local PvE: Pandora hold?
Read by the game's server browser, the tags Local PvE: Pandora publishes are: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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
How can I connect to Local PvE: Pandora?
In Rust, F1 opens the console: type client.connect 104.28.24.176:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.