Offline 109.252.110.184:28015 checked 5d ago
zhekatop
Connect
srv = rust.server("109.252.110.184: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 69% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 17:55 UTC5d ago | 0 | NaN | running | 0 |
| 1 | Sat 17 Oct, 21:53 UTC11d ago | 1 | NaN | 5.8 days | 1 |
# 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
- 109.252.110.184:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 17:55 UTC
- hostname
- –
- first seen
- 17 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 180/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 177/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 87/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 237/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 233/700 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does zhekatop rank?
Rank #15,344 on seven-day player hours for zhekatop, within the top 69% of all ranked servers.
How many players does zhekatop hold at once?
The current row shows zhekatop offline; the last response was 5 days 20 hours ago. Over the last seven days it averaged 0 players.
About the server
Which Rust version is zhekatop on?
Version Rust network protocol 2634 and build 167781 on Windows is reported by zhekatop. Joining needs the same protocol on your game; Steam handles the update.
Is zhekatop up, and what does its uptime show?
Offline now for zhekatop, last seen 5 days 20 hours ago. Over the last 7 full days the hours up number 2 of 168, 1%. Its earliest recorded date in Rust Data is 17 October 2026.
Which location does zhekatop run from?
There is no region published for zhekatop. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 109.252.110.184:28015.
Settings and map
Which rules apply on zhekatop, and what settings?
You will not find a gather rate in the string zhekatop. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has zhekatop loaded?
zhekatop runs a procedural map, which the game generates.
Wipe data
When does zhekatop wipe, and how often?
Too few wipes are on record for zhekatop to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 5 days 21 hours ago.
What is wipe day on zhekatop like?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Where does zhekatop appear among Rust Data lists and filters?
On Rust Data, zhekatop appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on zhekatop?
The game's server browser reads these tags from zhekatop: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into zhekatop?
In Rust, F1 opens the console: type client.connect 109.252.110.184:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.