Online 203.16.163.198:26595 checked 7m ago
private events
Connect
srv = rust.server("203.16.163.198:26596")
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 best
Top 16% 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 48, 25 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 17:05 UTC3d ago | 48 | NaN | running | 0 |
| 1 | Fri 23 Oct, 14:32 UTC6d ago | 2 | held half | 3.1 days | 0 |
| 2 | Mon 19 Oct, 16:56 UTC10d ago | 1 | held half | 3.9 days | 0 |
| 3 | Wed 7 Oct, 13:23 UTC22d ago | 3 | halved by day 1 | 12.1 days | 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
3500 · seed 1862422565
- map
- Procedural Map
- size
- 3500
- seed
- 1862422565
Server
srv.info()- address
- 203.16.163.198:26595
- region
- –
- max players
- 70
- group limit
- 60 max
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 17:05 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 · 151 on average | 78/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 | 131/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 42/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 91 on average | 135/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Population data
How does private events compare in the rankings?
Player hours over seven days put private events at #3,510, in the top 16% of the ranked set.
What population does private events carry?
The sample now reads 0 players for private events, out of 70 slots. Over the last seven days it averaged 1 players and peaked at 48. The 48-hour sample puts the busiest hour at 21:00 UTC, averaging 1 players.
Server facts
What does performance look like on private events?
Server fps over the last 48 hours averages 121; the floor is 79. The entity count peaked at 69,669, covering buildings, deployables and the rest of the world. Memory peaked at 4,475 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on private events?
Version Rust network protocol 2635 and build 168909 on Linux is reported by private events. Joining needs the same protocol on your game; Steam handles the update.
How reliable is private events, and is it up?
Online is the state at the latest refresh for private events. The uptime it reports puts the last restart about 36 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does private events sit?
There is no region published for private events. 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 203.16.163.198:26595.
Map and rules
What rules and settings are recorded for private events?
The name private events carries no gather rate. 60 players is the maximum per group. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has private events selected?
private events runs a procedural map of size 3,500 with seed 1862422565, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does private events wipe, and on what schedule?
No next wipe can be predicted for private events, which wipes at irregular times. 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 3 days 3 hours ago.
What is wipe day on private events like?
Recent wipes averaged 17 players at their peak. 25 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 67% of the time. Otherwise the crowd fell below half by day 1.
Tags, lists
Which lists on Rust Data hold private events, and which filters?
On Rust Data, private events appears in these lists: 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; Last wipe: In the last week.
Which meanings do the tags on private events hold?
Read by the game's server browser, the tags private events publishes are: gmrust (Game mode): Rust survival in its standard form; mp70 (Max players): Slot count: 70; ts60 (Group limit): No team may exceed 60; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not 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 to join private events?
Enter client.connect 203.16.163.198:26595 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.