Event
Offline 178.63.84.126:28035 checked 3d ago
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 7 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 18d 15h. The force wipe
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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
Quick answers
Tags and listings
Where does Event appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Event are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks.
How should you read the tags on Event?
The server browser shows these tags for Event: gmrust (Game mode): Survival, as standard Rust does it; mp50 (Max players): The slot count is 50; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): This server runs build 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty; ^m (Monthly): Facepunch's force wipe is when this server wipes each month; ^z (Modded): The Modded category fits: plugins or settings are in play; ^y (Carbon): This server relies on Carbon for plugins. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What location is Event in?
No region comes from Event. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 178.63.84.126:28035.
What's the uptime like for Event?
The server Event is not reachable at the moment; the last sighting was 3 days 15 hours ago. It was up 1% of the time over the last full 7 days, 1 of 168 hours. 7 October 2026 is when Rust Going Deep first saw it.
What Rust version is Event on?
On Linux, Event runs Rust network protocol 2634 and build 167781. The protocol must match to join; Steam will update your game.
Wipe schedule
What schedule does Event follow for wipes?
The next wipe on Event is calculated from the force wipe. All Rust servers wipe at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world has been running since 10 days 12 hours ago. The tags list wipes scheduled every month.
Map and rules
What settings are in place on Event?
Its name does not state a gather rate for Event. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Carbon. VAC is on: Valve's anti-cheat is active.
What's the map on Event?
A game-generated procedural map of size 2,500 with seed 12345 is in play on Event. RustMaps can display it from this page because the same size and seed yield the same map.
Player stats
What's the population like on Event?
Right now Event is offline, with its last appearance 3 days 15 hours ago. Over the past week it has drawn 0 players on average.
What's Event's rank among Rust servers?
Over the last seven days, Event is #15,861 by player hours, among the top 72% of all ranked servers.
Join info
How do you get into Event?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 178.63.84.126:28035.