On the class lists: D (48), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#8,824top 40%
Last wipe11h agomonthly schedule
Next wipe8d 9hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
60/ 100
C
Working its way up from the back of the class: #8,824 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 60 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 196 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
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.
Rank
daily · 1 is best
RankRank in region
Top 40% of all ranked servers, and #178 of the solo servers (top 81%). Ranked on player hours over the last seven days.
Attendance: the wipe record
11 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
···W···
··WWW··
······W
W·W····
·W·W···
·W·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 9h.
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 9hThu 5 Nov, 19:00 UTCFW
36d 9hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 22 OctTue 20 OctWed 14 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 22:07 UTC11h 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
JHUSKER leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 66.51.99.44:28055.
Is JHUSKER up, and how steady is its uptime?
The server is up: JHUSKER is online now. The uptime it reports puts the last restart at about 9 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does JHUSKER run?
The average over the last 48 hours was 60 server fps, and it never went below 54. Up to 70,231 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 3,128 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is JHUSKER running?
The server JHUSKER is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does JHUSKER wipe its map?
JHUSKER wipes with the force wipe and at no other time. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 11 hours. Its tags list a monthly wipe schedule.
What should you expect from wipe day on JHUSKER?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 33% of its recent wipes. In the other wipes it slipped under half by day 1.
Player numbers
Where does JHUSKER sit among Rust servers?
In the top 40% of all ranked servers, JHUSKER sits at #8,824 for player hours over the last seven days. It comes #178 among servers in the solo group.
How many players does JHUSKER usually have?
With 50 slots available, JHUSKER currently has 0 players. Averaging 0 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 23:00 UTC, averaging 1 players.
Tags and filters
What do JHUSKER's tags stand for?
You'll see JHUSKER tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts1 (Group limit): A team can hold 1 players at most; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does JHUSKER appear in the Rust Server Score lists and filters?
Rust Server Score lists that include JHUSKER: Modded Rust servers, graded and Solo Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Monthly; Last wipe: In the last 24 hours.
Server rules
What settings and rules apply on JHUSKER?
You will find no gather rate in the name of JHUSKER. No teams are allowed: it is solo only. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map JHUSKER uses?
A procedural map of size 2,500 and seed 62023032, generated by the game, is what JHUSKER runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join JHUSKER?
To connect, start Rust, press F1, and type client.connect 66.51.99.44:28055. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^m,gmrust,cs168909,ts1,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts1
Group limitA team can hold 1 players at most.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).