RUST METRICSFlight deck · live data
Data live Servers11,595 Players34,229 Populated2,837 Fresh wipes 3 h65 Scan5 min
‹ All servers66.51.99.44:28055
Online Full Queue Fresh wipe Wipe due No query

JHUSKER

Online 66.51.99.44:28055 checked 10m ago

solo monthly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Wed 03:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 60 SERVER FPS

Server fps

48 h low 54 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 29,110 ×1000

Entities

48 h range 26,953–70,231 · memory 1,326 MB
1239 ET SINCE RESTART 05:00

Uptime

5 h 0 min since its last restart, at the last reading
7-day average0peak 1
Rank#8,831top 40%
Last wipe6h agomonthly schedule
Next wipe8d 14hThu 5 Nov, 19:00 UTC FW
Memory1,326MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75105:0014:0023:0009:0018:0003:00Wiped Tue 27 Oct, 22:07 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
02040608005:0014:0023:0009:0018:0003:00Wiped Tue 27 Oct, 22:07 UTCWIPE

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 40% of all ranked servers, and #178 of the solo servers (top 81%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 14h. 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

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 14hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC36d 14hFW

The first 48 hours of its last wipes

Thu 22 OctTue 20 OctWed 14 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 22:07 UTC6h 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

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on JHUSKER when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 33% of recent wipes. It fell below half by day 1 when it didn't.

What wipe timing does JHUSKER follow?

The only wipe for JHUSKER is the force wipe, once a month. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 6 hours ago. Its tags carry a monthly wipe schedule.

Lists and filters

Which tags does JHUSKER carry, and what do they mean?

Tags published by JHUSKER, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts1 (Group limit): Team cap: 1; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show JHUSKER?

Rust Metrics lists featuring JHUSKER: Modded Rust servers, checked live and Solo-only Rust servers. Reading: server list filters. It comes up under Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Monthly; Last wipe: In the last 24 hours.

Population

Where does JHUSKER sit in the rankings?

Player hours over seven days put JHUSKER at #8,831, in the top 40% of all ranked servers. The solo group places it at #178.

What player count does JHUSKER carry?

Current headcount on JHUSKER: 0 players, 50 slots available. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 23:00 UTC, 1 players on average.

Operator and location

Where does JHUSKER sit?

No region comes from JHUSKER. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 66.51.99.44:28055.

What Rust version is JHUSKER on?

Reading: JHUSKER, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

How does JHUSKER perform?

Reading: 60 server fps on average across the last 48 hours. It never dropped below 54. Reading: 70,231 entities at the highest. That covers buildings, deployables and everything else. Reading: 3,128 MB of memory at the highest. Expect lag when fps falls and entities climb.

What is the uptime on JHUSKER, and is it online?

JHUSKER reports online. Status: normal. Reading: uptime. About 5 hours ago it restarted, on its own count. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does JHUSKER enforce, and what are its settings?

Check: gather rate. The name JHUSKER does not state one. Solo play only. Teams are not allowed. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is JHUSKER on?

Check: map. Procedural, size 2,500, seed 62023032, generated by the game on JHUSKER. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

What do you do to join JHUSKER?

Check: join. Open Rust, press F1, then enter client.connect 66.51.99.44:28055. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^m,gmrust,cs168909,ts1,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts1
Group limit Team cap: 1.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock game.

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.