Online 104.254.131.178:50002 checked 13m ago
Hyperlkl
Connect
srv = rust.server("104.254.131.178:50004")
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 12 Oct. 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
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
4000 · seed 65188
- map
- Procedural Map
- size
- 4000
- seed
- 65188
Server
srv.info()- address
- 104.254.131.178:50002
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 21:09 UTC
- hostname
- –
- first seen
- 12 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 · 161 on average | 32/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 41/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 28/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 9/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 8/1000 |
Quick answers
From the figures on this page.
Population
How does Hyperlkl compare in the rankings?
Over the last seven days Hyperlkl sits at #15,411 on player hours, in the top 69% of ranked servers.
What population does Hyperlkl carry?
Hyperlkl reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players.
Server data
How smoothly does Hyperlkl run?
Server fps over the last 48 hours averages 91; the floor is 74. The entity count peaked at 93,247, covering buildings, deployables and the rest of the world. Memory peaked at 5,087 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does Hyperlkl run?
The build is Rust network protocol 2634 and build 167584 on Linux, run by Hyperlkl. Steam updates your game for you, but the protocol must match to join.
How reliable is Hyperlkl, and is it up?
Hyperlkl reports itself online at the current refresh. A restart about 15 days 1 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. Rust Data logged it first on 12 October 2026.
Where does Hyperlkl sit?
For Hyperlkl, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 104.254.131.178:50002 is its address.
Map and rules
What rules and settings are recorded for Hyperlkl?
You will not find a gather rate in the string Hyperlkl. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Hyperlkl selected?
Size 4,000, seed 65188: the procedural map on Hyperlkl, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
On what schedule does Hyperlkl wipe?
A rhythm cannot be read from the wipes of Hyperlkl 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 15 days 5 hours ago.
Tags and filters
Which lists on Rust Data hold Hyperlkl, and which filters?
On Rust Data, Hyperlkl appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Hyperlkl hold?
The game's server browser reads these tags from Hyperlkl: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167584 (Build): The server runs build 167584; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 Hyperlkl?
In Rust, F1 opens the console: type client.connect 104.254.131.178:50002. Launch Rust on this page does the same by opening the game through Steam and connecting.