Station XX-15432 · no signal
Maxs Events
Offline 131.153.158.236:28195 checked 6d ago
- Players now
- 0/ 30
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,432
- top 69%
- Last wipe
- 19d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 30 slots
- Motion · 24 h
- M –not enough readings
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 19.8 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 9 Oct, 09:57 UTC19d ago | – | – | – | – | running | 0 |
| Sat 19 Sep, 13:59 UTC39d ago | M0.0■steady | 0 | – | 19.8 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Maxs Events?
The procedural map on Maxs Events is size 4,500 with seed 1337, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on Maxs Events?
The name of Maxs Events gives no gather rate. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on Maxs Events?
Maxs Events is not responding at this moment and is offline, last seen 6 days 6 hours ago. The population averaged 0 players over the past week.
How does Maxs Events rank against other Rust servers?
On player hours for the past week, Maxs Events sits at #15,432, which puts it inside the top 69% of every ranked server.
Server facts
How reliably does Maxs Events stay online?
No contact with Maxs Events right now, and the last recorded contact was 6 days 6 hours ago. 2 of 168 hours in the last 7 full days were up time, 1% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
Where in the world is Maxs Events hosted?
A region is not published by Maxs Events. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 131.153.158.236:28195.
What build of Rust does Maxs Events use?
Rust network protocol 2634 and build 167398 on Linux is what Maxs Events runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on Maxs Events?
0 players, on average, was the busiest crowd at its recent wipes.
On what timetable does Maxs Events run its wipes?
On record so far are too few of Maxs Events's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 19 days 4 hours is how long the current world has been running.
Server tags
What do the server tags on Maxs Events mean?
These are the tags Maxs Events publishes for the browser to read: gmvanilla (Game mode): You'll find vanilla survival here; mp30 (Max players): Slots: 30; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167398 (Build): It runs game build 167398; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Maxs Events appear?
The Rust Server Trends lists that take in Maxs Events are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Connecting
How do you connect to Maxs Events?
Enter client.connect 131.153.158.236:28195 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.