On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak –
Rank#15,341top 69%
Last wipe27d agono schedule published
Next wipe7d 2hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 10 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,341 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
83/ 100
B+
Mostly smooth: 50 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 216 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
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
7d 2hThu 5 Nov, 19:00 UTCFW
35d 2hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 18 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 20:59 UTCFW27d ago
1
–
running
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
hitosetserver001 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 160.251.143.180:28015.
How reliable is hitosetserver001, and is it up?
The server is up: hitosetserver001 is online now. The uptime it reports puts the last restart at about 5 days 16 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Is hitosetserver001 smooth to play on?
It never fell below 31 server fps in the last 48 hours, averaging 50. At its peak, it held 154,763 entities, including buildings, deployables and all else in the world. Memory use reached up to 5,415 MB. When fps is low and entities climb, that is lag to players.
On what Rust version does hitosetserver001 sit?
Rust network protocol 2634 and build 166586 on Linux is what hitosetserver001 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does hitosetserver001 wipe its map?
hitosetserver001 wipes with the force wipe and at no other time. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 27 days 19 hours.
What should you expect from wipe day on hitosetserver001?
Recent wipes have peaked at 1 players on average. 18 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does hitosetserver001 place in the wider field of Rust servers?
Over the last seven days, hitosetserver001 has #15,341 for player hours, in the top 69% of all ranked servers.
How many players does hitosetserver001 usually have?
Right now, 0 players are on hitosetserver001, which has 10 slots. For the last seven days, the average number of players was 0.
Tags
What do hitosetserver001's tags stand for?
You'll see hitosetserver001 tagged with gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Its slot count is 10; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166586 (Build): This runs on build 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does hitosetserver001 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include hitosetserver001: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does hitosetserver001 enforce, and what are its settings?
You will find no gather rate in the name of hitosetserver001. The default of 8 players applies as the group cap. 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. You are covered by VAC, Valve's anti-cheat.
hitosetserver001 runs which map?
hitosetserver001 runs a game-generated procedural map at size 5,000, seed 244772856. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to hitosetserver001?
To connect, start Rust, press F1, and type client.connect 160.251.143.180:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersIts slot count is 10.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166586
BuildThis runs on build 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).