Fig. 1Players on JHUSKERRG-S8835-01 · Sheet 1 of 10
Fig. 2
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S8835-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 40% of all ranked servers, and #179 of the solo servers (top 81%). Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S8835-03 · Sheet 3 of 10
Schedule
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 5h.
The force wipe · high confidence
usual gap2 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
crowd held33%else halves by day 1
Coming wipes
8d 5hThu 5 Nov, 19:00 UTCFW
36d 5hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 22 OctTue 20 OctWed 14 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
ScheduleExpected wipesRG-S8835-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 22:07 UTC15h ago
–
–
running
0
Thu 22 Oct, 23:18 UTC5d ago
1
halved by day 1
5 days
0
Tue 20 Oct, 22:36 UTC7d ago
1
held half
2 days
0
Wed 14 Oct, 22:02 UTC13d ago
1
halved by day 1
6 days
0
Mon 12 Oct, 23:40 UTC15d ago
1
–
1.9 days
0
Sun 11 Oct, 01:57 UTC17d ago
1
–
1.9 days
0
Fri 2 Oct, 23:57 UTC25d ago
1
halved by day 2
8.1 days
0
Thu 1 Oct, 00:51 UTC27d ago
1
–
2 days
0
Wed 30 Sep, 00:19 UTC28d ago
1
–
1 days
0
Thu 24 Sep, 21:42 UTC33d ago
1
halved by day 2
5.1 days
0
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.
Table 1Wipe logRG-S8835-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is JHUSKER online, and what uptime has been recorded?
JHUSKER is up at this moment. About 14 hours ago is when it last restarted, measured from the uptime it reports. 168 of 168 hours up over the last 7 full days, which is 100% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
2.
Is JHUSKER stable in the figures recorded?
60 server fps on average over the last 48 hours, and never under 54. Counted at its highest: 70,231 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,128 MB. Players feel low fps and a climbing entity count as lag.
3.
In which location is JHUSKER hosted?
A region is not published by JHUSKER. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 66.51.99.44:28055 is its address.
4.
On which Rust version is JHUSKER running?
Rust network protocol 2635 and build 168909 on Linux: that is what JHUSKER runs. To join, your game must be on the same protocol; Steam handles the update.
Counts
5.
What does the population history show for JHUSKER?
Current player count on JHUSKER: 0, of 50 slots. The seven-day mean is 0 players; the peak over the same period is 1. The 48-hour peak falls at 23:00 UTC, averaging 1 players.
6.
What rank has been recorded for JHUSKER?
Player hours over seven days place JHUSKER at #8,835, within the top 40% of ranked servers. Ranked #179 among solo servers.
Wipe data
7.
What is recorded on JHUSKER on wipe day?
An average of 1 players was recorded at the busiest point of its recent wipes. At 0 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 33% of its recent wipes stayed above half that peak. On the wipes where it did not hold, the crowd dropped below half by day 1.
8.
Which times and days are wipes plotted at on JHUSKER?
Once a month, with the force wipe, is when JHUSKER wipes. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The current world has been in use since 15 hours ago. Its tags give a wipe schedule of one wipe per month.
Map and rules
9.
Which rules and settings are recorded for JHUSKER?
No gather rate is stated in the name of JHUSKER. One player per group: no teams. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. Listed as Modded in the server browser: the game is changed by plugins or settings. The plugin count is Oxide. VAC is on: that is Valve's anti-cheat.
10.
What is the map for JHUSKER?
Seed 62023032 and size 2,500 define the procedural map JHUSKER generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Lists and filters
11.
Where does JHUSKER appear among the Rust Graphs lists and filters?
On Rust Graphs, JHUSKER is placed in these lists: Modded Rust servers and Solo Rust servers: group limit 1. On the server list, these filters bring it up: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Monthly; Last wipe: In the last 24 hours.
12.
On JHUSKER, what is meant by each tag?
gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): 50 player slots; ts1 (Group limit): Team size is capped at 1; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^m (Monthly): Monthly wipes, on Facepunch's force wipe; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded are the tags JHUSKER publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Connect
13.
By what method do you join JHUSKER?
In Rust, press F1 and type client.connect 66.51.99.44:28055 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.
NotesAnswered from the figuresRG-S8835-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^m,gmrust,cs168909,ts1,^o^z
Game
gmrust
Game modeStandard survival, as Rust plays.
mp50
Max players50 player slots.
ts1
Group limitTeam size is capped at 1.
v2635
ProtocolYour game must match protocol 2635 to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeThe region code field is empty.
Wipe schedule
^m
MonthlyMonthly wipes, on Facepunch's force wipe.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
