Offline 5.227.27.65:28015 checked 19d ago
PixelRush
Connect
srv = rust.server("5.227.27.65: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 61% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 20:02 UTC20d ago | 1 | NaN | running | 0 |
| 1 | Wed 7 Oct, 20:42 UTC21d ago | 1 | NaN | 1 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
- 5.227.27.65:28015
- region
- –
- max players
- 15
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 20:02 UTC
- hostname
- –
- first seen
- 7 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 · 157 on average | 102/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 128/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 98/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 30/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does PixelRush rank?
Over the last seven days PixelRush sits at #13,607 on player hours, in the top 61% of ranked servers.
How full does PixelRush run?
PixelRush returns no live count at this refresh, having last been seen 19 days 3 hours ago.
Server facts
What Rust version does PixelRush run?
Rust network protocol 2634 and build 167058 on Windows is what PixelRush runs. Steam updates your game for you, but the protocol must match to join.
How reliable is PixelRush, and is it online now?
PixelRush is offline at this refresh; the last response came 19 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 7 October 2026.
Where does PixelRush sit?
There is no region published for PixelRush. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 5.227.27.65:28015.
Map and rules
Which rules apply on PixelRush, and what settings?
The name PixelRush carries no gather rate. No custom cap; the default of 8 players per group stands. 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 PixelRush selected?
PixelRush runs a procedural map, which the game generates.
Wipes and dates
When does PixelRush wipe, and how often?
A rhythm cannot be read from the wipes of PixelRush 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. The world it runs now was generated 20 days 1 hours ago.
On PixelRush, what happens on wipe day?
The average peak over recent wipes is 1 players. 1 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does PixelRush appear among Rust Data lists and filters?
The Rust Data lists that PixelRush fits are: 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 PixelRush hold?
These tags are published by PixelRush and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp15 (Max players): The server lists 15 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): Recorded game build: 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join PixelRush?
Enter client.connect 5.227.27.65:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.