Online 194.54.88.56:28195 checked 12m ago
Maxs Events
Connect
srv = rust.server("194.54.88.56:28196")
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 bestTop 23% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 9 Oct, 09:57 UTC20d ago | 1 | NaN | running | 0 |
| 1 | Sat 19 Sep, 13:59 UTC40d ago | 10 | halved by day 2 | 19.8 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
4500 · seed 1
- map
- Procedural Map
- size
- 4500
- seed
- 1
Server
srv.info()- address
- 194.54.88.56:28195
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 09:57 UTC
- hostname
- –
- first seen
- 17 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 | 102/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 157/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 61/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 188/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 344/350 |
Quick answers
From the figures on this page.
Population data
What position does Maxs Events take in the server rankings?
Player hours over seven days put Maxs Events at #5,024, in the top 23% of the ranked set.
What population does Maxs Events carry?
Maxs Events reports 0 players at this refresh, with 30 slots configured. Over the last seven days it averaged 0 players and peaked at 16.
Server facts
How well does Maxs Events perform?
Server fps over the last 48 hours averages 123; the floor is 91. Entity numbers reached 125,324, and that includes buildings, deployables and the rest. The memory field tops out at 6,466 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is Maxs Events on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Maxs Events. Steam updates your game for you, but the protocol must match to join.
How reliable is Maxs Events, and is it up?
Maxs Events reports itself online at the current refresh. The uptime it reports puts the last restart about 5 days 15 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 17 September 2026.
In which location is Maxs Events hosted?
For Maxs Events, no region is published. 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 194.54.88.56:28195.
Rules, settings, map
Which rules apply on Maxs Events, and what settings?
You will not find a gather rate in the string Maxs Events. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Anti-cheat status: VAC on.
What is the map on Maxs Events?
The game generates the map on Maxs Events: procedural, size 4,500, seed 1. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does Maxs Events wipe, and how often?
A rhythm cannot be read from the wipes of Maxs Events on record, which are too few. 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 20 days 9 hours ago.
What is wipe day on Maxs Events like?
The average peak over recent wipes is 6 players. The crowd on the latest wipe topped out 1 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 2.
Tags and filters
Which lists on Rust Data hold Maxs Events, and which filters?
The Rust Data lists that Maxs Events fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Maxs Events hold?
These tags are published by Maxs Events and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp30 (Max players): 30 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to Maxs Events?
Enter client.connect 194.54.88.56:28195 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.