Station XX-16685 · no signal
NoHazzy PVE (In Development)
Offline 65.75.203.17:28015 checked 28d ago
- Players now
- 0/ 15
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,685
- top 70%
- Last wipe
- 55d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 15 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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 pageServer rules
Which map is running on NoHazzy PVE (In Development)?
The procedural map on NoHazzy PVE (In Development) is size 2,200 with seed 549, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on NoHazzy PVE (In Development)?
The name of NoHazzy PVE (In Development) gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on NoHazzy PVE (In Development)?
No players are recorded on NoHazzy PVE (In Development) at this moment; it is offline, and the last sighting was 28 days 21 hours ago.
How does NoHazzy PVE (In Development) rank against other Rust servers?
Over the last seven days, NoHazzy PVE (In Development) recorded enough player hours to reach #16,685 worldwide, placing it in the top 70% of all ranked servers.
Server details
How reliably does NoHazzy PVE (In Development) stay online?
No contact with NoHazzy PVE (In Development) right now, and the last recorded contact was 28 days 21 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does NoHazzy PVE (In Development) run from?
Nothing about a region comes from NoHazzy PVE (In Development). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 65.75.203.17:28015.
Which Rust version is NoHazzy PVE (In Development) running?
Rust network protocol 2633 and build 163207 on Linux is what NoHazzy PVE (In Development) runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
How often does NoHazzy PVE (In Development) wipe, and on which days?
On record so far are too few of NoHazzy PVE (In Development)'s wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 55 days 14 hours.
Lists and tags
What do the server tags on NoHazzy PVE (In Development) mean?
Tags published by NoHazzy PVE (In Development) and read by the game's server browser include gmvanilla (Game mode): Survival in vanilla mode; mp15 (Max players): The server has 15 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs163207 (Build): It runs game build 163207; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 NoHazzy PVE (In Development) appear?
The Rust Server Trends lists that take in NoHazzy PVE (In Development) are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Connecting
What steps get you onto NoHazzy PVE (In Development)?
To join, enter client.connect 65.75.203.17:28015 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. https://discord.com/invite/nohazzy is where its website lives.
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.