Online 66.51.99.44:28055 checked 10m ago
JHUSKER
Connect
srv = rust.server("66.51.99.44:28056")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 17 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 bestTop 40% of all ranked servers, and #178 of the solo servers (top 81%). Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 15h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 15h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 15h | Thu 3 Dec, 19:00 UTC | FW 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 | Tue 27 Oct, 22:07 UTC5h ago | NaN | NaN | running | 0 |
| 1 | Thu 22 Oct, 23:18 UTC5d ago | 1 | halved by day 1 | 5 days | 0 |
| 2 | Tue 20 Oct, 22:36 UTC7d ago | 1 | held half | 2 days | 0 |
| 3 | Wed 14 Oct, 22:02 UTC13d ago | 1 | halved by day 1 | 6 days | 0 |
| 4 | Mon 12 Oct, 23:40 UTC15d ago | 1 | NaN | 1.9 days | 0 |
| 5 | Sun 11 Oct, 01:57 UTC17d ago | 1 | NaN | 1.9 days | 0 |
| 6 | Fri 2 Oct, 23:57 UTC25d ago | 1 | halved by day 2 | 8.1 days | 0 |
| 7 | Thu 1 Oct, 00:51 UTC27d ago | 1 | NaN | 2 days | 0 |
| 8 | Wed 30 Sep, 00:19 UTC28d ago | 1 | NaN | 1 days | 0 |
| 9 | Thu 24 Sep, 21:42 UTC33d ago | 1 | halved by day 2 | 5.1 days | 0 |
| 10 | Mon 14 Sep, 15:49 UTC43d ago | 1 | halved by day 4 | 10.2 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
2500 · seed 62023032
- map
- Procedural Map
- size
- 2500
- seed
- 62023032
Server
srv.info()- address
- 66.51.99.44:28055
- region
- –
- max players
- 50
- group limit
- solo
- wipe schedule
- monthly
- last wipe
- 27 Oct 2026, 22:07 UTC
- hostname
- –
- first seen
- 13 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 | 404 RUST SOLO | ВС | ДЛЯ НОВИЧКОВ 25.10 | EU · solo · monthly · 5 on average | 3/400 |
| 1 | 404 RUST SOLO | СБ | ДЛЯ НОВИЧКОВ 24.10 | EU · solo · monthly · 3 on average | 1/400 |
| 2 | 404 RUST SOLO | ВТ | ДЛЯ НОВИЧКОВ 27.10 | EU · solo · monthly · 3 on average | 1/400 |
| 3 | 404 RUST SOLO | ПН | ДЛЯ НОВИЧКОВ 26.10 | EU · solo · monthly · 3 on average | 4/400 |
| 4 | 404 RUST SOLO | ЧТ | ДЛЯ НОВИЧКОВ 22.10 | EU · solo · monthly · 2 on average | 0/400 |
| 5 | 404 RUST SOLO | ПТ | ДЛЯ НОВИЧКОВ 23.10 | EU · solo · monthly · 2 on average | 0/400 |
Quick answers
From the figures on this page.
Population
What position does JHUSKER take in the server rankings?
Player hours over seven days put JHUSKER at #8,825, in the top 40% of the ranked set. The solo group places it at #178.
How many players does JHUSKER hold at once?
Current row: 0 players on JHUSKER, against 50 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 23:00 UTC is the busiest, at 1 players.
Server facts
How well does JHUSKER perform?
The 48-hour average is 60 server fps, with a low of 54. Buildings, deployables and all else in the world took the count as high as 70,231 entities. A high of 3,128 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is JHUSKER on?
Version Rust network protocol 2635 and build 168909 on Linux is reported by JHUSKER. The protocol has to match before you can join, and Steam does the updating.
How reliable is JHUSKER, and is it up?
Online is the state at the latest refresh for JHUSKER. The uptime it reports puts the last restart about 3 hours ago. 168 of 168 hours up over the last 7 full days, or 100%. Rust Data logged it first on 13 September 2026.
Where does JHUSKER sit?
No region is published by JHUSKER. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 66.51.99.44:28055.
Map and rules
What rules and settings are recorded for JHUSKER?
You will not find a gather rate in the string JHUSKER. No teams here: solo only. Recorded as survival, 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.
What is the map on JHUSKER?
Size 2,500, seed 62023032: the procedural map on JHUSKER, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does JHUSKER wipe, and how often?
Once a month JHUSKER wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 5 hours ago, and that is the one in play. The tags list wipes as monthly.
What is wipe day on JHUSKER like?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 33% of recent wipes. In the wipes where it did not hold, half was lost by day 1.
Tags, lists
Which Rust Data filters and lists contain JHUSKER?
The Rust Data lists that JHUSKER fits are: Modded Rust servers and Solo Rust servers, group limit 1. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Monthly; Last wipe: In the last 24 hours.
How should you read the server tags on JHUSKER?
Read by the game's server browser, the tags JHUSKER publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts1 (Group limit): Team size tops out at 1; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^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.
Connecting
What is the way into JHUSKER?
In Rust, F1 opens the console: type client.connect 66.51.99.44:28055. Launch Rust on this page does the same by opening the game through Steam and connecting.