Offline 57.138.66.51:28025 checked 5d ago
HalliBoyz3
Connect
srv = rust.server("57.138.66.51:28027")
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 18 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 47% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 18 Oct, 21:09 UTC8d ago | 1 | NaN | running | 1 |
| 1 | Wed 7 Oct, 18:11 UTC20d ago | 1 | held half | 11.1 days | 0 |
| 2 | Sat 3 Oct, 20:56 UTC23d ago | 2 | held half | 3.9 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
3500 · seed 484012
- map
- Procedural Map
- size
- 3500
- seed
- 484012
Server
srv.info()- address
- 57.138.66.51:28025
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 21:09 UTC
- hostname
- –
- first seen
- 18 Sep 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 · 163 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 111 on average | 189/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 31/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 85 on average | 170/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 59/1000 |
Quick answers
From the figures on this page.
Player counts
How does HalliBoyz3 compare in the rankings?
Player hours over seven days put HalliBoyz3 at #10,292, in the top 47% of the ranked set.
How full does HalliBoyz3 run?
The current row shows HalliBoyz3 offline; the last response was 5 days 15 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
Which Rust version is HalliBoyz3 on?
Rust network protocol 2634 and build 167058 on Windows is what HalliBoyz3 runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is HalliBoyz3, and is it up?
The latest sample has HalliBoyz3 offline, with a last sighting 5 days 15 hours ago. 33 of 168 hours up over the last 7 full days, or 20%. Rust Data logged it first on 18 September 2026.
In which location is HalliBoyz3 hosted?
For HalliBoyz3, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 57.138.66.51:28025.
Settings and map
Which rules apply on HalliBoyz3, and what settings?
No gather rate appears in the name: HalliBoyz3. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has HalliBoyz3 loaded?
The game generates the map on HalliBoyz3: procedural, size 3,500, seed 484012. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does HalliBoyz3 wipe?
No next wipe can be predicted for HalliBoyz3, which wipes at irregular times. 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 8 days 22 hours ago.
What is wipe day on HalliBoyz3 like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags and filters
Which lists on Rust Data hold HalliBoyz3, and which filters?
The Rust Data lists that HalliBoyz3 fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on HalliBoyz3?
The game's server browser reads these tags from HalliBoyz3: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167058 (Build): Recorded game build: 167058; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to HalliBoyz3?
In Rust, F1 opens the console: type client.connect 57.138.66.51:28025. Launch Rust on this page does the same by opening the game through Steam and connecting.