Station XX-8786 · no signal
HugoServ
Offline 37.4.252.247:27015 checked 6d ago
- Players now
- 0/ 40
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #8,786
- top 40%
- Last wipe
- 9d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 40 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 40% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 16 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 19 Oct, 15:10 UTC9d ago | M0.0■steady | 1 | – | running | 1 | |
| Sat 3 Oct, 15:41 UTC25d ago | M0.0■steady | 0 | – | 16 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on HugoServ?
A procedural map runs on HugoServ, generated by the game.
Which settings and rules apply on HugoServ?
You will find no gather rate in the name of HugoServ. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched off.
Player counts
What is the current population on HugoServ?
A reading taken now finds HugoServ offline; the most recent activity was 6 days 14 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 1.
How does HugoServ rank against other Rust servers?
Over the last seven days, HugoServ recorded enough player hours to reach #8,786 worldwide, placing it in the top 40% of all ranked servers.
Server details
How reliably does HugoServ stay online?
As recorded now, HugoServ is not reachable, the last contact having been 6 days 14 hours ago. It was up 5% of the time across the last 7 full days: 9 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.
Which region does HugoServ run from?
Nothing about a region comes from HugoServ. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 37.4.252.247:27015.
Which Rust version is HugoServ running?
On Linux, HugoServ runs Rust network protocol 2634 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on HugoServ?
0 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
How often does HugoServ wipe, and on which days?
The rhythm of HugoServ cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 9 days 22 hours.
Server tags
What do the server tags on HugoServ mean?
The game's server browser reads the tags HugoServ publishes: gmrust (Game mode): You'll find standard Rust survival here; mp40 (Max players): Slots: 40; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does HugoServ appear?
You will find HugoServ on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How to join
What steps get you onto HugoServ?
To join, enter client.connect 37.4.252.247:27015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.