Offline 77.52.17.66:28015 checked 17d ago
RUST: DEADLINE x10
Connect
srv = rust.server("77.52.17.66: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
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 77.52.17.66:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 14:53 UTC
- hostname
- –
- first seen
- 11 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 | Atlas - EU 10x | No BPs | Kits | Shop | EU · groups of 20+ · 10x · weekly · 341 on average | 443/500 |
| 1 | Atlas - US 10x | No BPs | Kits | Shop | NA · groups of 30+ · 10x · weekly · 178 on average | 134/150 |
| 2 | TemplarGaming 10x Swift Loot++|PvP|MyMini|SkinBox|x10 JUST WIPE | NA · groups of 8+ · 10x · weekly · 178 on average | 71/200 |
| 3 | KRAKEN | X10 | EU | KITS | RP | FPS+ | EU · groups of 14+ · 10x · weekly · 150 on average | 169/400 |
| 4 | [LATAM] LUNARUST X10 | 21/10 Wipe | SA · groups of 8+ · 10x · weekly · 82 on average | 1/100 |
| 5 | HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop] | EU · groups of 8+ · 10x · biweekly · 77 on average | 98/150 |
Quick answers
From the figures on this page.
Population
What position does RUST: DEADLINE x10 take in the server rankings?
Over the last seven days RUST: DEADLINE x10 sits at #13,623 on player hours, in the top 62% of ranked servers.
How full does RUST: DEADLINE x10 run?
RUST: DEADLINE x10 returns no live count at this refresh, having last been seen 17 days 4 hours ago.
Server facts
What is the Rust version on RUST: DEADLINE x10?
The build is Rust network protocol 2634 and build 166652 on Windows, run by RUST: DEADLINE x10. The protocol has to match before you can join, and Steam does the updating.
How reliable is RUST: DEADLINE x10, and is it up?
The latest sample has RUST: DEADLINE x10 offline, with a last sighting 17 days 4 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 11 October 2026.
Which location does RUST: DEADLINE x10 run from?
There is no region published for RUST: DEADLINE x10. Rust Data does not look up where the machine stands; it shows where a server says it is. 77.52.17.66:28015 is its address.
Rules, settings, map
What rules and settings are recorded for RUST: DEADLINE x10?
The name carries the figure: RUST: DEADLINE x10 runs 10x gather. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has RUST: DEADLINE x10 loaded?
The game generates its map: procedural, on RUST: DEADLINE x10.
Wipe data
When does RUST: DEADLINE x10 wipe, and on what schedule?
The record for RUST: DEADLINE x10 holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 23 days 22 hours ago, and that is the one in play.
Tags, lists
Which Rust Data filters and lists contain RUST: DEADLINE x10?
These Rust Data lists include RUST: DEADLINE x10: Modded Rust servers and 10x Rust servers: the live sample. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 10x.
Which meanings do the tags on RUST: DEADLINE x10 hold?
These tags are published by RUST: DEADLINE x10 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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
What is the way to join RUST: DEADLINE x10?
In Rust, F1 opens the console: type client.connect 77.52.17.66:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.