Offline EU 66.51.97.65:28085 checked 9d ago
ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU
Connect
srv = rust.server("66.51.97.65:28086")
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 best
Top 69% of all ranked servers, top 88% in EU, and #378 of the duo servers (top 89%). Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Sunday 1 November, 13:41 UTC, in 3d 23h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 3d 23h | Sun 1 Nov, 13:41 UTC | wipe |
| 1 | 8d 4h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 17d 23h | Sun 15 Nov, 13:41 UTC | wipe |
| 3 | 31d 23h | Sun 29 Nov, 13:41 UTC | wipe |
| 4 | 36d 4h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 6, 3 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 13:41 UTC24d ago | 6 | NaN | running | 3 |
| 1 | Fri 2 Oct, 00:15 UTC26d ago | 3 | held half | 2.6 days | 0 |
| 2 | Sat 19 Sep, 10:39 UTC39d ago | 7 | halved by day 2 | 12.6 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 1586544950
- map
- Procedural Map
- size
- 4500
- seed
- 1586544950
Server
srv.info()- address
- 66.51.97.65:28085
- region
- EU
- max players
- 200
- group limit
- duo
- wipe schedule
- biweekly
- last wipe
- 4 Oct 2026, 13:41 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | EU RustChimera 2X|Solo/Duo|50% UPKEEP|SHARED BP|Biweekly | EU · duo · 2x · biweekly · 3 on average | 2/60 |
| 1 | ![DUO] MINSK / RUST | X2 | TP | ECONOMICS | EU · duo · 2x · biweekly · 2 on average | 3/100 |
| 2 | [EU] POTG - Solo/Duo | Raid Hours | 2x | 50% | Bi-weekly | EU · duo · 2x · biweekly · 1 on average | 0/100 |
| 3 | WARBANDITS.GG EU 2X |Solo/Duo|X2 JUST WIPED | EU · duo · 2x · weekly · 208 on average | 529/300 |
| 4 | Magic Rust #5 — Modded 2x (Solo/Duo) | Pyccкий | EU · duo · 2x · weekly · 117 on average | 52/100 |
| 5 | Magic Rust #26 — Vanilla 2x (Solo/Duo) | Pyccкий | EU · duo · 2x · weekly · 98 on average | 28/200 |
Quick answers
From the figures on this page.
Population data
What position does ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU take in the server rankings?
Player hours over the last seven days: #15,253 for ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU, #2,580 in Europe, within the top 69% of the ranked set. The duo group places it at #378.
How full does ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU run?
Offline now for ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU, with the last sample 9 days 20 hours ago.
Server data
What is the Rust version on ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU?
Rust network protocol 2634 and build 167781 on Linux is what ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU runs. The protocol has to match before you can join, and Steam does the updating.
Is ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU up, and what does its uptime show?
ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU is offline at this refresh; the last response came 9 days 20 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU hosted?
In Europe, ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU lists itself, using the EU tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 66.51.97.65:28085 is its address.
Settings and map
Which rules apply on ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU, and what settings?
Gather sits at 2x, read from the server's own name: ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU. Up to 2 players may share a group (duo). Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU loaded?
The game generates the map on ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU: procedural, size 4,500, seed 1586544950. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU wipe, and how often?
Too few wipes are on record for ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU to confirm its schedule, so the tag drives the prediction. On Sunday 1 November at 13:41 UTC the next wipe is due. A new world was started 24 days ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.
What is wipe day on ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU like?
Recent wipes averaged 5 players at their peak. The crowd on the latest wipe topped out 3 hours after it began. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. In the wipes where it did not hold, half was lost by day 2.
Lists and tags
Where does ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU appear among Rust Data lists and filters?
The Rust Data lists that ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU fits are: Rust servers with a duo group limit, EU Rust servers, Modded Rust servers and 2x Rust servers. Under these filters on the server list, it is listed: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Every two weeks; Gather rate: 2x.
Which meanings do the tags on ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU hold?
The game's server browser reads these tags from ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): Slot count: 200; ts2 (Group limit): The team cap is 2; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): The cycle is fourteen days; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; EU (Europe): The server browser files it under Europe. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to ZEROHOUR EU 2X SOLO ONLY | LOOT + | OFFLINE RAID ALERTS | CU?
In Rust, F1 opens the console: type client.connect 66.51.97.65:28085. Launch Rust on this page does the same by opening the game through Steam and connecting.