Rust StatisticsWorking papers on every public Rust server · 75,264 players now

Maxs Events

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 5m ago · 194.54.88.56:28195

Abstract

We describe the public Rust server Maxs Events, reached at 194.54.88.56:28195. At the last check it held 0 of 30 places, against a seven-day mean of 0 and a peak of 161. It ranks #5,028 of all servers, the top 23%. It last wiped 20d ago.

Keywordsmodded carbon

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/300% full
In the queue0no queue
Seven-day mean0peak 16
Rank2#5,028top 23%
Last wipe20d agono schedule published
Next wipe3–too few wipes seen yet

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
0123423:0008:0017:0003:0012:0021: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
05010015020023:0008:0017:0003:0012:0021: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 23% 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: too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap19.8 daysbetween real wipes
Wipe-day peak6players, last three wipes
Crowd held0%else halves by day 2
Fri 9 OctSat 19 Sep
02.557.510+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 1, 1 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 9 Oct, 09:5720d ago 1 – running 0
Sat 19 Sep, 13:5940d ago 10 halved by day 2 19.8 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 Maxs Events
Figure 5: The map: Procedural Map, size 4500, seed 1. Open on RustMaps.
Table 4: The server's published settings.
Address194.54.88.56:28195
Region–
Max players30
Group limit8, the default
Wipe schedule–
Last wipe9 Oct 2026, 09:57 UTC
Hostname–
First seen17 Sep 2026
MapProcedural Map
Size4500
Seed1

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [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 average36/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 · 120 on average71/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average30/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 92 on average74/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average293/310

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of Maxs Events smooth?

Over the past 48 hours, it ran at an average of 124 server fps, with a low of 110. Buildings, deployables and all other world objects counted together reached a maximum of 125,324 entities. Its highest memory usage was 6,466 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What is the location of Maxs Events?

A region is not published by Maxs Events. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 194.54.88.56:28195.

A.3What is the online status and reliability of Maxs Events?

Maxs Events is online at this time. The uptime it reports indicates a restart about 5 days 18 hours ago. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. Its first appearance in Rust Statistics's records is 17 September 2026.

A.4What version of Rust is run on Maxs Events?

Rust network protocol 2635 and build 168909 is the version that Maxs Events runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.5On what cycle does Maxs Events wipe?

There are not yet enough recorded wipes for Maxs Events to reveal its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 20 days 12 hours have passed since the current world was generated.

A.6How would you describe wipe day on Maxs Events?

The average busiest point of recent wipes was 6 players. The peak on the latest wipe came 1 hours after it began. For 0% of recent wipes, the population did not fall below half the peak before the next wipe. Otherwise, a fall below half took place by day 2.

Population

A.7How does Maxs Events compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts Maxs Events at #5,028, within the top 23% of ranked servers.

A.8How would you characterise the player activity on Maxs Events?

At this moment 0 players are on Maxs Events, which has 30 slots in total. The peak over seven days is 16, against an average of 0.

Tags, lists

A.9How should the tags on Maxs Events be interpreted?

Tags from Maxs Events, read by the game's server browser, are gmvanilla (Game mode): This is survival in its vanilla form; mp30 (Max players): It offers 30 slots; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; ^y (Carbon): This server uses Carbon for its plugins. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.10Where can Maxs Events be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Maxs Events fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Settings and map

A.11Which settings and rules are in force on Maxs Events?

No gather rate appears in the name of Maxs Events. At 8 players, the group limit equals the game's default. The mode is survival, which means gather, build and raid: the standard game. Players may raid and fight one another. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Carbon on this server. The server has VAC on, Valve's anti-cheat.

A.12On which map does Maxs Events take place?

Size 4,500 and seed 1 define the procedural, game-generated map on Maxs Events. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

How to join

A.13What is the process for joining Maxs Events?

Press F1 inside Rust to open the console and enter client.connect 194.54.88.56:28195. 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 mp30,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmvanillaGame mode. This is survival in its vanilla form.
mp30Max players. It offers 30 slots.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. This server runs game build 168909.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.
Mods and access
^zModded. The game is altered by plugins or settings, so it is listed as Modded.
^yCarbon. This server uses Carbon for its plugins.

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 servers by player count. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.