Offline 162.244.125.185:28015 checked 41d ago
Void's Vibe Coding - Script Testing
Connect
srv = rust.server("162.244.125.185:28016")
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, measured since 17 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 16h. # 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
4500 · seed 1646099129
- map
- Procedural Map
- size
- 4500
- seed
- 1646099129
Server
srv.info()- address
- 162.244.125.185:28015
- region
- –
- max players
- 350
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 4 Sep 2026, 13:49 UTC
- hostname
- –
- first seen
- 13 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 · 53 on average | 56/300 |
| 1 | [US] RustEZ Scourge PvE | Zombies | No Raiding | No Killing | NA · groups of 8+ · monthly · 50 on average | 63/200 |
| 2 | [US] RustEZ Survival PvE | No Decay | No Raiding | No Killing | NA · groups of 8+ · monthly · 39 on average | 44/200 |
| 3 | [坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖 | EA · groups of 8+ · monthly · 35 on average | 30/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 | 50/100 |
Quick answers
From the figures on this page.
Player counts
How does Void's Vibe Coding - Script Testing compare in the rankings?
Over the last seven days Void's Vibe Coding - Script Testing sits at #15,490 on player hours, in the top 69% of ranked servers.
What population does Void's Vibe Coding - Script Testing carry?
Offline now for Void's Vibe Coding - Script Testing, with the last sample 41 days 1 hours ago.
About the server
What Rust version does Void's Vibe Coding - Script Testing run?
Rust network protocol 2633 and build 164530 on Windows is what Void's Vibe Coding - Script Testing runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Void's Vibe Coding - Script Testing, and is it online now?
Offline now for Void's Vibe Coding - Script Testing, last seen 41 days 1 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 13 September 2026.
Where does Void's Vibe Coding - Script Testing sit?
There is no region published for Void's Vibe Coding - Script Testing. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 162.244.125.185:28015.
Settings and map
What rules and settings are recorded for Void's Vibe Coding - Script Testing?
The name Void's Vibe Coding - Script Testing carries no gather rate. 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. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Void's Vibe Coding - Script Testing loaded?
The game generates the map on Void's Vibe Coding - Script Testing: procedural, size 4,500, seed 1646099129. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does Void's Vibe Coding - Script Testing wipe, and how often?
An estimate from the force wipe gives Void's Vibe Coding - Script Testing's next wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 54 days 12 hours ago, and that is the one in play. The tags list wipes as monthly.
Lists and tags
Where does Void's Vibe Coding - Script Testing appear among Rust Data lists and filters?
On Rust Data, Void's Vibe Coding - Script Testing appears in these lists: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: 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 Void's Vibe Coding - Script Testing hold?
Read by the game's server browser, the tags Void's Vibe Coding - Script Testing publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp350 (Max players): Slot count: 350; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): Build number: 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): The plugin framework in use is 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 into Void's Vibe Coding - Script Testing?
Enter client.connect 162.244.125.185:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.