Offline 66.51.97.59:28080 checked 27d ago
PVE - Gingaluvin
Connect
srv = rust.server("66.51.97.59:28081")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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()Next wipe Thursday 5 November, 19:00 UTC, in 7d 13h. # The 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
4000 · seed 8151
- map
- Procedural Map
- size
- 4000
- seed
- 8151
Server
srv.info()- address
- 66.51.97.59:28080
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 18 Sep 2026, 17:33 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 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 36/300 |
| 1 | [US] RustEZ Scourge PvE | Zombies | No Raiding | No Killing | NA · groups of 8+ · monthly · 50 on average | 39/200 |
| 2 | [US] RustEZ Survival PvE | No Decay | No Raiding | No Killing | NA · groups of 8+ · monthly · 39 on average | 34/200 |
| 3 | [坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖 | EA · groups of 8+ · monthly · 35 on average | 39/100 |
| 4 | 1[PvE]Тульский|Русский|Classic+Ивенты | EU · groups of 8+ · monthly · 35 on average | 7/200 |
| 5 | Zombie Land PVE Monthly | Raids | Skills | Custom Maps | NA · groups of 14+ · monthly · 34 on average | 43/100 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does PVE - Gingaluvin rank?
Player hours over seven days put PVE - Gingaluvin at #15,970, in the top 69% of the ranked set.
What population does PVE - Gingaluvin carry?
Offline now for PVE - Gingaluvin, with the last sample 27 days 5 hours ago.
Server data
What is the Rust version on PVE - Gingaluvin?
Rust network protocol 2633 and build 164530 on Linux is what PVE - Gingaluvin runs. Steam updates your game for you, but the protocol must match to join.
Is PVE - Gingaluvin up, and what does its uptime show?
The latest sample has PVE - Gingaluvin offline, with a last sighting 27 days 5 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 18 September 2026.
Which location does PVE - Gingaluvin run from?
For PVE - Gingaluvin, 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 66.51.97.59:28080.
Map and rules
Which rules apply on PVE - Gingaluvin, and what settings?
No gather rate appears in the name: PVE - Gingaluvin. The group limit sits at the default of 8 players. Recorded as pve, no combat between players. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has PVE - Gingaluvin selected?
Size 4,000, seed 8151: the procedural map on PVE - Gingaluvin, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
On what schedule does PVE - Gingaluvin wipe?
The next wipe for PVE - Gingaluvin is an estimate, drawn from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 40 days 11 hours ago. A monthly wipe schedule is published in its tags.
Tags and filters
Where does PVE - Gingaluvin appear among Rust Data lists and filters?
These Rust Data lists include PVE - Gingaluvin: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Which meanings do the tags on PVE - Gingaluvin hold?
Read by the game's server browser, the tags PVE - Gingaluvin publishes are: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; 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; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^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.
Connecting
What is the way to join PVE - Gingaluvin?
The manual route: launch Rust, F1, then client.connect 66.51.97.59:28080. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.