Rust Server Analytics 79,533 players11,830 servers
All servers
Drill-through Server detail

private events

Online 203.16.163.198:26595 checked 12m ago

Drill-through
FilterServeris private events
Attributes
moddedoxide
Last refreshed
Players now 0/ 70
7-day average 1 peak 48
Rank #3,503 top 16%
Last wipe 2d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
02040608015:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
010020030040015:0000:0009:0019:0004:0013:00

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
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 16% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap3.9 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak17players, last three wipes
crowd held67%else halves by day 1

The first 48 hours of its last wipes

Mon 26 OctFri 23 OctMon 19 Oct
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 48, 25 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 17:05 UTC2d ago 48 – running 0
Fri 23 Oct, 14:32 UTC5d ago 2 held half 3.1 days 0
Mon 19 Oct, 16:56 UTC9d ago 1 held half 3.9 days 0
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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
ShockRust | Blue | NoLimit no group limit · 149 on average 189 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 130 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 119 on average 54 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average 77 / 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 46 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 85 on average 254 / 700

Quick answers

from the figures on this page

Wipe cycle

On what cycle does private events wipe?

With irregular wipe times, private events offers no next wipe to predict. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world now in play was created 2 days 21 hours ago.

Wipe day on private events: what should you expect?

The average busiest count over recent wipes is 17 players. The highest player count on the latest wipe arrived 25 hours in. The crowd stayed above half that peak until the next wipe in 67% of recent wipes. By day 1 it had fallen below half where the hold failed.

Server details

In which region does private events sit?

No region is published by private events. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. The address of the server is 203.16.163.198:26595.

What Rust build does private events run?

On Linux, private events runs Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam handles the update.

Is private events up, and how steady is its uptime?

private events reports online at the current check. The uptime it reports puts the last restart at about 30 hours ago. Of 168 hours in the last 7 full days, 167 were up: 99%. It entered Rust Server Analytics records on 13 September 2026.

Is performance on private events stable?

Over 48 hours the average held at 123 server fps, and the minimum was 79. Entity count reached 69,669, covering buildings, deployables and the rest of the world. At its highest, memory use was 4,475 MB. Players experience lag as low fps combined with a rising entity count.

Tags

How should the tags on private events be read?

gmrust (Game mode): Rust survival, standard ruleset; mp70 (Max players): 70 slots in total; ts60 (Group limit): The cap is 60 players per team; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded are the tags private events publishes, and the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Where does private events appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include private events: Modded Rust servers: live data. These filters 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 3 days.

Population

Where does private events sit among Rust servers?

Player hours for the last seven days place private events at #3,503, in the top 16% of the ranked field.

How many players does private events carry?

Population at the current refresh: 0 players on private events, against 70 slots. Seven-day figures: an average of 1 players and a peak of 48. The 48-hour peak window is 19:00 UTC, at an average of 29 players.

Map and rules

What are the settings on private events, and its rules?

Gather rate is not mentioned in the name of private events. The cap on group membership is 60 players. It runs survival, the standard game: gather, build, raid. Raiding and PvP combat are available. Plugins or settings modify the game, and it is listed as Modded. The plugin framework is Oxide. The server runs with VAC, Valve's anti-cheat, enabled.

The map on private events: which one is it?

A procedural map of size 3,500 with seed 1862422565, generated by the game, runs on private events. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Connection

How can a player join private events?

In the Rust console (F1), enter client.connect 203.16.163.198:26595. Launch Rust on this page also works, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp70,ptrak,$r?,v2635,gmrust,cs168909,ts60,^o^z

Game

gmrust
Game mode Rust survival, standard ruleset.
mp70
Max players 70 slots in total.
ts60
Group limit The cap is 60 players per team.
v2635
Protocol To join, your game version must match protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code A region code is not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it sits under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.