Rust StatisticsWorking papers on every public Rust server · 90,952 players now

private events

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 13m ago · 203.16.163.198:26595

Abstract

We describe the public Rust server private events, reached at 203.16.163.198:26595. At the last check it held 0 of 70 places, against a seven-day mean of 1 and a peak of 481. It ranks #3,507 of all servers, the top 16%. It last wiped 3d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/700% full
In the queue0no queue
Seven-day mean1peak 48, 48 h peak 1
Rank2#3,507top 16%
Last wipe3d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
00.250.50.75122:0007:0016:0002:0011:0020:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
010020030040022:0007:0016:0002:0011:0020:00
Figure 2: 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.

4Rank

The server stands in the top 16% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
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
Mon 26 OctFri 23 OctMon 19 Oct
010203040+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 26 Oct, 17:053d ago 48 – running 0
Fri 23 Oct, 14:326d ago 2 held half 3.1 d 0
Mon 19 Oct, 16:5610d ago 1 held half 3.9 d 0
Wed 7 Oct, 13:2322d ago 3 halved by day 1 12.1 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of private events
Figure 5: The map: Procedural Map, size 3500, seed 1862422565. Open on RustMaps.
Table 4: The server's published settings.
Address203.16.163.198:26595
Region–
Max players70
Group limit60 max
Wipe schedule–
Last wipe26 Oct 2026, 17:05 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size3500
Seed1862422565

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and upcoming Rust wipes [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 150 on average62/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average121/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 119 on average112/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average36/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 92 on average119/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average347/350

Appendix AQuick answers

From the figures on this page.

About the server

A.1Does private events perform well?

Its average server fps over the last 48 hours was 121, with a minimum of 79. Buildings, deployables and all other world objects counted together reached a maximum of 69,669 entities. The peak memory usage was 4,475 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What is the location of private events?

No region is published by private events. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 203.16.163.198:26595 is its address.

A.3What is the reliability of private events, and is it online?

private events is currently online. Based on the uptime it reports, the last restart occurred about 37 hours ago. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. Its first appearance in Rust Statistics's records is 13 September 2026.

A.4What version of Rust is run on private events?

private events is running Rust network protocol 2635 and build 168909 on the Linux operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5What schedule does private events follow for wipes?

Prediction of the next wipe is impossible for private events, which wipes irregularly. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 3 days 4 hours ago.

A.6What happens on private events when wipe day arrives?

Recent wipes saw an average peak of 17 players. The crowd reached its maximum 25 hours after the latest wipe. The crowd stayed above half its peak until the next wipe in 67% of recent wipes. Otherwise, a fall below half took place by day 1.

Population

A.7What position does private events occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts private events at #3,507, within the top 16% of ranked servers.

A.8At what level does private events operate in terms of players?

At this moment 0 players are on private events, which has 70 slots in total. Over the last week the count averages 1 players and reaches 48 at its height. Of the last 48 hours, the peak hour falls at 22:00 UTC, with an average of 1 players.

Tags, lists

A.9What is the meaning of the tags on private events?

gmrust (Game mode): This is survival as standard Rust plays; mp70 (Max players): The slot count is 70; ts60 (Group limit): 60 is the maximum team size; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags private events publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can private events be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that private events fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Rules, settings, map

A.11Under what rules and settings does private events operate?

The name of private events states no gather rate. The team limit is 60 players. survival is the game mode here; gather, build and raid: the standard game. Combat and raiding against other players are allowed. It appears under Modded in the browser: the game is changed by plugins or settings. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.

A.12On which map does private events take place?

The game generates private events's procedural map at size 3,500, from seed 1862422565. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.13What is the process for joining private events?

Press F1 inside Rust to open the console and enter client.connect 203.16.163.198:26595. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp70,ptrak,$r?,v2635,gmrust,cs168909,ts60,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp70Max players. The slot count is 70.
ts60Group limit. 60 is the maximum team size.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. The game build is 168909.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.