private events
Online 203.16.163.198:26595 checked 9m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 16% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts 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
every wipe as a delivery, newest first-
Mon 26 Oct, 17:05 UTC 17:05 UK · 3d agoWipe delivered
- Peak
- 48
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Fri 23 Oct, 14:32 UTC 15:32 UK · 6d agoWipe delivered
- Peak
- 2
- Crowd
- held half
- Lasted
- 3.1 days
- Players before
- 0
-
Mon 19 Oct, 16:56 UTC 17:56 UK · 10d agoWipe delivered
- Peak
- 1
- Crowd
- held half
- Lasted
- 3.9 days
- Players before
- 0
-
Wed 7 Oct, 13:23 UTC 14:23 UK · 22d agoWipe delivered
- Peak
- 3
- Crowd
- halved by day 1
- Lasted
- 12.1 days
- Players before
- 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- ShockRust | Blue | NoLimit 102 / 500
- МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 127 / 100
- RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 157 / 225
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 61 / 700
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 188 / 700
- RustSpain.com | EU Main 344 / 350
Quick answers
From the figures on this page.
Player count
Where does private events place among Rust servers?
A seven-day player-hours count places private events at #3,506: the top 16% of every ranked server.
How many players are on private events right now?
The current count is 0 players on 70 slots for private events. Averaged over the past week: 1 players, peaking at 48. The busiest hour over the last 48 hours was 20:00 UTC, averaging 14 players.
Map and rules
Which map is active on private events?
Size 3,500 and seed 1862422565 define the procedural map private events runs, generated by the game. You can see the map on RustMaps from this page, since one size and seed give one map.
What are the rules on private events, and what settings does it run?
The name of private events gives no gather rate. A group holds no more than 60 players. survival is the mode, gather and build and raid: the standard game. Raiding and PvP are both on. Plugins or settings alter the game on this one, which sits under Modded in the server browser. Oxide supplies the plugins. VAC, Valve's anti-cheat, is switched on.
Server details
What location does private events run from?
No region is published by private events. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. The address to connect to is 203.16.163.198:26595.
Does private events perform well?
Averaged over the last 48 hours, server fps was 121, with a low of 79. The world held as many as 69,669 entities: buildings, deployables and the rest. Memory use peaked at 4,475 MB. Lag, to players, means low fps alongside an entity count on the rise.
What is the uptime of private events, and is it online?
You can find private events online at present. Its reported uptime suggests a restart roughly 35 hours ago. It was up 167 of 168 hours over the last 7 full days, 99% of the time. 13 September 2026 is when Rust Wipe Tracker first recorded it.
What Rust version is private events using?
Rust network protocol 2635 and build 168909 on Linux is what private events runs. Steam keeps your game updated; it has to be on the same protocol to join.
Map resets
How does private events handle its wipe days?
At their busiest, its recent wipes drew an average of 17 players. 25 hours after the latest wipe, the crowd reached its peak. Until the next wipe, the crowd stayed over half the peak in 67% of recent cases. In the other cases it sank under half by day 1.
On what schedule does private events reset its map?
There is no next wipe to predict for private events: it wipes at irregular times. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. You are playing a world created 3 days 2 hours.
Server tags
On Rust Wipe Tracker, which lists and filters is private events part of?
The Rust Wipe Tracker lists that include private events are: Modded Rust servers. These are the filters that bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the tags on private events?
The game's server browser picks up these private events tags: gmrust (Game mode): Survival in standard Rust; mp70 (Max players): It holds 70 slots; ts60 (Group limit): The team limit is 60; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): The region code is unset; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.
How to join
What is the process to join private events?
Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 203.16.163.198:26595.