Offline 203.16.163.41:20000 checked 43d ago
Bungulators
Connect
srv = rust.server("203.16.163.41:20001")
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
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 203.16.163.41:20000
- region
- –
- max players
- 9
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Sep 2026, 19:23 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 143/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 189/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 10/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Bungulators rank?
Over the last seven days Bungulators sits at #15,470 on player hours, in the top – of ranked servers.
What population does Bungulators carry?
Bungulators returns no live count at this refresh, having last been seen 43 days 5 hours ago.
Server facts
What Rust version does Bungulators run?
Rust network protocol 2633 and build 163493 on Linux is what Bungulators runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Bungulators, and is it online now?
Offline now for Bungulators, last seen 43 days 5 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.
In which location is Bungulators hosted?
There is no region published for Bungulators. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 203.16.163.41:20000 is its address.
Rules, settings, map
Which settings and rules does Bungulators run?
The name Bungulators carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Bungulators selected?
Bungulators runs a procedural map, which the game generates.
Wipe schedule
When does Bungulators wipe, and how often?
A rhythm cannot be read from the wipes of Bungulators on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 49 days 15 hours ago.
Lists and tags
Where does Bungulators appear among Rust Data lists and filters?
These Rust Data lists include Bungulators: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Bungulators?
Read by the game's server browser, the tags Bungulators publishes are: gmrust (Game mode): Survival play, standard Rust; mp9 (Max players): The server lists 9 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163493 (Build): Recorded game build: 163493; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into Bungulators?
Enter client.connect 203.16.163.41:20000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.