On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,405top 69%
Last wipe16d agobiweekly schedule
Next wipe4d 1hSun 1 Nov, 00:37 UTC
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
31/ 100
F
Working its way up from the back of the class: #15,405 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
50/ 100
D
Slows down under load at times: 30 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 175 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
······W
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Sunday 1 November, 00:37 UTC, in 4d 1h.
Every 3 weeks on Sunday at 00:37 UTC · low confidence
usual gap21 daysbetween real wipes
wipe-day peak0players, last three wipes
Coming wipes
4d 1hSun 1 Nov, 00:37 UTC
8d 19hThu 5 Nov, 19:00 UTCFW
25d 1hSun 22 Nov, 00:37 UTC
36d 19hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Sun 11 OctSun 20 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 11 Oct, 00:37 UTC16d ago
0
–
running
0
Sun 20 Sep, 00:44 UTC37d ago
0
–
21 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
In what location does HGNetworks Rust Server (In Dev) sit?
No region is published for HGNetworks Rust Server (In Dev). Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 31.97.14.111:28015.
How reliable is HGNetworks Rust Server (In Dev), and is it up?
Right now, HGNetworks Rust Server (In Dev) is online. According to its reported uptime, the last restart was about 2 days 20 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Does HGNetworks Rust Server (In Dev) perform well?
It averaged 30 server fps over the last 48 hours, with a low of 24. Buildings, deployables and everything else in the world added up to as many as 21,220 entities. At its highest, it used 1,755 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is HGNetworks Rust Server (In Dev) on?
Rust network protocol 2635 and build 167781 on Linux is what HGNetworks Rust Server (In Dev) runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does HGNetworks Rust Server (In Dev) reset?
Its wipe pattern: HGNetworks Rust Server (In Dev) wipes every 3 weeks on Sunday at 00:37 UTC. Expect the next wipe on Sunday 1 November at 00:37 UTC. It has been running its current world for 16 days 22 hours. A fortnightly wipe schedule appears in its tags.
What happens on HGNetworks Rust Server (In Dev) when wipe day arrives?
Recent wipes have peaked at 0 players on average. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does HGNetworks Rust Server (In Dev) place in the wider field of Rust servers?
In the top 69% of all ranked servers, HGNetworks Rust Server (In Dev) sits at #15,405 for player hours over the last seven days.
Is HGNetworks Rust Server (In Dev) a busy server?
HGNetworks Rust Server (In Dev) is showing 0 players right now, with 50 slots in total. A seven-day average of 0 players applies here.
Tags
How should you read the tags on HGNetworks Rust Server (In Dev)?
The game's browser takes its cue from the tags HGNetworks Rust Server (In Dev) has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 HGNetworks Rust Server (In Dev) appear in the Rust Server Score lists and filters?
These Rust Server Score lists count HGNetworks Rust Server (In Dev) among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Rules and settings
What settings and rules apply on HGNetworks Rust Server (In Dev)?
You will find no gather rate in the name of HGNetworks Rust Server (In Dev). With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
HGNetworks Rust Server (In Dev) runs which map?
A procedural map of size 2,200 and seed 6738, generated by the game, is what HGNetworks Rust Server (In Dev) runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How should you connect to HGNetworks Rust Server (In Dev)?
Enter client.connect 31.97.14.111:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^b,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under 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 term to build on. Strongest in uptime (A+); population is the one to work on (F).