Offline 153.66.117.113:28015 checked 22d ago
[US] Event Rust
Connect
srv = rust.server("153.66.117.113:28016")
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. 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 best
Top 62% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 6 Oct, 23:25 UTC22d ago | 1 | NaN | running | 0 |
| 1 | Tue 6 Oct, 12:40 UTC22d ago | 1 | NaN | 0.4 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 153.66.117.113:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Oct 2026, 23:25 UTC
- hostname
- –
- first seen
- 6 Oct 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 | Friendly Seattle: No KOS | Chill | Noob Friendly | NA · groups of 8+ · biweekly · 41 on average | 45/100 |
| 1 | [US] Enardo - Random Farming - Small One Grid | OneGrid | NA · groups of 8+ · 29 on average | 40/50 |
| 2 | [NA] Willjum's Solo Only | Thursday Wipes | NA · groups of 8+ · weekly · 26 on average | 12/100 |
| 3 | Rust Degens - US Vanilla | Fridays | NA · groups of 8+ · weekly · 15 on average | 2/150 |
| 4 | [NA] Willjum's Casual Solo/Duo Monthly | NA · groups of 8+ · monthly · 15 on average | 10/175 |
| 5 | Hempville 420 No Kos Low Decay / Limited PvP | NA · groups of 8+ · monthly · 7 on average | 13/90 |
Quick answers
From the figures on this page.
Population data
How does [US] Event Rust compare in the rankings?
Player hours over seven days put [US] Event Rust at #13,774, in the top 62% of the ranked set.
How many players does [US] Event Rust hold at once?
[US] Event Rust returns no live count at this refresh, having last been seen 22 days 3 hours ago.
About the server
What is the Rust version on [US] Event Rust?
Version Rust network protocol 2634 and build 166652 on Windows is reported by [US] Event Rust. Joining needs the same protocol on your game; Steam handles the update.
How reliable is [US] Event Rust, and is it online now?
[US] Event Rust is offline at this refresh; the last response came 22 days 3 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 6 October 2026.
Which location does [US] Event Rust run from?
No region tag is published by [US] Event Rust, though its name points to North America. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 153.66.117.113:28015.
Map and rules
Which rules apply on [US] Event Rust, and what settings?
The name [US] Event Rust carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has [US] Event Rust selected?
A procedural map runs on [US] Event Rust, generated by the game.
Wipe data
When does [US] Event Rust wipe, and how often?
A rhythm cannot be read from the wipes of [US] Event Rust on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 22 days 4 hours ago.
On [US] Event Rust, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does [US] Event Rust appear among Rust Data lists and filters?
On Rust Data, [US] Event Rust appears in these lists: Modded Rust servers and North America Rust servers. Under these filters on the server list, it is listed: Region: North America; Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on [US] Event Rust?
These tags are published by [US] Event Rust and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to [US] Event Rust?
In Rust, F1 opens the console: type client.connect 153.66.117.113:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.