Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO O SRV11,877online PAX95,616playing OCC4,087with players WIPED 3H149
MODModded traffic
Callsign

HGN15383=

HGNetworks Rust Server (In Dev)

Online 31.97.14.111:28015 checked 14m ago

biweekly wipes moddedoxide
Clearance · join
Players now 0/ 50 0% full
7-day average0peak –
Rank#15,383top 70%
Last wipe16d agobiweekly schedule
Next wipe4d 5hSun 1 Nov, 00:37 UTC
Track history

Players

AveragePeak
0123419:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

01020304019:0004:0013:0023:0008:0017:00

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
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Flight plan

Wipe schedule

fixed weekdays
ETD · next wipe

Next wipe Sunday 1 November, 00:37 UTC, in 4d 5h.

Every 3 weeks on Sunday at 00:37 UTC · low confidence

usual gap21 daysbetween real wipes
wipe-day peak0players, last three wipes

Coming wipes

  1. 4d 5hSun 1 Nov, 00:37 UTC
  2. 9d 0hThu 5 Nov, 19:00 UTCFW
  3. 25d 5hSun 22 Nov, 00:37 UTC
  4. 37d 0hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Sun 11 OctSun 20 Sep
01234+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign STT017NA · groups of 8+ · biweekly · 36 on average Friendly Seattle: No KOS | Chill | Noob Friendly
    Players 36/100
  2. 02MOD
    Callsign EVN020EA · groups of 10+ · biweekly · 19 on average [JP]初心者PVPサーバー|RaidTime・ Events
    Players 3/100
  3. 03MOD
    Callsign EVN210EU · groups of 50+ · biweekly · 9 on average СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10
    Players 12/200
  4. 04MOD
    Callsign ACD001EU · groups of 8+ · biweekly · 7 on average RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ
    Players 16/200
  5. 05MOD
    Callsign EMP021groups of 8+ · biweekly · 5 on average Rust Empires II - Roleplay/RP friendly, Cities, PVE, No KOS out
    Players 6/50
  6. 06MOD
    Callsign ESP016EU · groups of 16+ · biweekly · 5 on average [ESP][PVE] PACIFIC WORLD (WIPED 15/10/2026)
    Players 8/50
ATIS · this server

Quick answers

From the figures on this page.

Tags

Where does HGNetworks Rust Server (In Dev) appear in Rust Tracker lists and filters?

On Rust Tracker, HGNetworks Rust Server (In Dev) sits in these lists: Modded servers, tracked live. On the server list, these filters bring it up: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

How should you read the tags on HGNetworks Rust Server (In Dev)?

The game's server browser reads these tags from HGNetworks Rust Server (In Dev): gmrust (Game mode): Standard survival mode for Rust; mp50 (Max players): Capacity: 50 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs167781 (Build): The game build is 167781; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set; ^b (Biweekly): A wipe every fortnight; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

What should you expect on HGNetworks Rust Server (In Dev) when wipe day lands?

Recent wipes averaged a peak of 0 players. The peak on the latest wipe came 0 hours after it.

When does HGNetworks Rust Server (In Dev) wipe?

At HGNetworks Rust Server (In Dev) the wipes follow a every 3 weeks on Sunday at 00:37 UTC rhythm. Sunday 1 November at 00:37 UTC is when the next wipe falls due. Its world went live 16 days 18 hours. A two-weekly wipe schedule is published in its tags.

Server Details

How reliable is HGNetworks Rust Server (In Dev), and is it online now?

Tracking shows HGNetworks Rust Server (In Dev) online as of now. The uptime it reports puts the last restart about 2 days 16 hours ago. 168 of 168 hours up over the last 7 full days: 100% uptime. The first sighting by Rust Tracker was 13 September 2026.

Which Rust version is confirmed on HGNetworks Rust Server (In Dev)?

Rust network protocol 2635 and build 167781 on Linux is what HGNetworks Rust Server (In Dev) runs. To join, your game must be on the same protocol; Steam handles the update.

What is performance like on HGNetworks Rust Server (In Dev)?

For the last 48 hours it averaged 30 server fps; the floor was 24. Peak entity count: 21,132, covering buildings, deployables and all else in the world. Memory peaked at 1,755 MB. Lag, as players experience it, comes from low fps and a rising entity count.

Which location is HGNetworks Rust Server (In Dev) in?

No region is published by HGNetworks Rust Server (In Dev). Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 31.97.14.111:28015.

Population

How many players are on HGNetworks Rust Server (In Dev) right now?

Slots 50; players on board 0: that is HGNetworks Rust Server (In Dev) now. Across the past seven days, 0 players on average.

What rank does HGNetworks Rust Server (In Dev) carry among Rust servers?

Seven-day player hours put HGNetworks Rust Server (In Dev) at #15,383, within the top 70% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on HGNetworks Rust Server (In Dev)?

The name of HGNetworks Rust Server (In Dev) carries no gather rate. The game's default applies: groups can have up to 8 players. It runs survival, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins run on it. On: VAC, Valve's anti-cheat.

Which map is confirmed for HGNetworks Rust Server (In Dev)?

The map on HGNetworks Rust Server (In Dev) is procedural, size 2,200, seed 6738, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map.

Connect

Which steps join HGNetworks Rust Server (In Dev)?

Open the console in Rust with F1 after starting the game, then type client.connect 31.97.14.111:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.

Transponder codes

Server tags

What each one means.

Published as mp50,ptrak,$r?,v2635,^b,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Standard survival mode for Rust.
mp50
Max players Capacity: 50 slots.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs167781
Build The game build is 167781.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly A wipe every fortnight.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).
^z
Modded Under Modded: the game is changed by plugins or settings.

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.