Working its way up from the back of the class: #16,685 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
48/ 100
D
Slipped a little: down 574 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
Where in the world is NoHazzy PVE (In Development)?
No region is published for NoHazzy PVE (In Development). The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 65.75.203.17:28015.
How dependable is NoHazzy PVE (In Development), and is it online at the moment?
You cannot join now: NoHazzy PVE (In Development) is offline, last seen 28 days 1 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is NoHazzy PVE (In Development) running?
The server NoHazzy PVE (In Development) is on Rust network protocol 2633 and build 163207 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does NoHazzy PVE (In Development) wipe, and how often?
NoHazzy PVE (In Development) has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 54 days 17 hours.
Population
What position does NoHazzy PVE (In Development) hold in the rankings?
In the top 70% of all ranked servers, NoHazzy PVE (In Development) sits at #16,685 for player hours over the last seven days.
What does the population on NoHazzy PVE (In Development) look like?
It has been 28 days 1 hours since NoHazzy PVE (In Development) was last seen, and it is offline right now.
Lists and filters
How should you read the tags on NoHazzy PVE (In Development)?
You'll see NoHazzy PVE (In Development) tagged with gmvanilla (Game mode): Survival, vanilla style; mp15 (Max players): The server holds 15 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs163207 (Build): Build number: 163207; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. 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 NoHazzy PVE (In Development) appear in the Rust Server Score lists and filters?
These Rust Server Score lists count NoHazzy PVE (In Development) among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
What settings and rules apply on NoHazzy PVE (In Development)?
You will find no gather rate in the name of NoHazzy PVE (In Development). 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. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
NoHazzy PVE (In Development) runs which map?
The game generates the procedural map on NoHazzy PVE (In Development) at size 2,200 with seed 549. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to NoHazzy PVE (In Development)?
To connect, start Rust, press F1, and type client.connect 65.75.203.17:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://discord.com/invite/nohazzy.
Server tags
what each one means
Published asmp15,ptrak,$r?,v2633,gmvanilla,cs163207,ts8,^z,^y
Game
gmvanilla
Game modeSurvival, vanilla style.
mp15
Max playersThe server holds 15 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163207
BuildBuild number: 163207.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: Carbon.
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 momentum (D); standing is the one to work on (F).