On the class lists: F (31), with population over 48 hours and no performance mark.
Players now1/ 333% full
7-day average1peak 1
Rank#7,280top 33%
Last wipe26d agomonthly schedule
Next wipe7d 3hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
25/ 100
F
A quiet classroom so far: 1 of 3 on average. Plenty of space to grow.
Standingrank on player hours
67/ 100
C+
Working its way up from the back of the class: #7,280 on player hours.
Uptimehours on the list, last 48
6/ 100
F
Attendance needs work: on the list only 3 of the last 48 hours.
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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (C+); uptime 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 best
RankRank in region
Top 33% 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h.
The 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
huascar leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 190.107.51.219:28015.
How reliable is huascar, and is it up?
At this moment, huascar is offline; the last time it was seen was 35 hours ago. For the last 6 full days, it was up 16 of 144 hours, or 11% of the time. The first sighting by Rust Server Score was on 22 October 2026.
On what Rust version does huascar sit?
The server huascar is on Rust network protocol 2635 and build 168909 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does huascar reset?
The next wipe on huascar is a projection from the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 26 days 17 hours. Its tags record that it wipes monthly.
Population
Where does huascar place in the wider field of Rust servers?
Over the last seven days, huascar has #7,280 for player hours, in the top 33% of all ranked servers.
Is huascar a busy server?
huascar is offline at the moment; the last time it was seen was 35 hours ago. It peaked at 1 and averaged 1 players over the last seven days. Over the last 48 hours, the peak hour was 03:00 UTC, averaging 1 players.
Tags
What do huascar's tags stand for?
gmvanilla (Game mode): You play vanilla survival here; mp3 (Max players): Its slot count is 3; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags huascar publishes, and the game's server browser reads them. 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.
Which lists and filters on Rust Server Score show huascar?
Rust Server Score lists that include huascar: Modded Rust servers, graded. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
What settings and rules apply on huascar?
You will find no gather rate in the name of huascar. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in 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. The plugin count runs to Carbon. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
Which map is in play on huascar?
A procedural map, generated by the game, is what huascar runs.
How to join
How do you get onto huascar?
To connect, start Rust, press F1, and type client.connect 190.107.51.219:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp3,ptrak,$r?,v2635,^z,^y,^m,^v,gmvanilla,cs168909,ts8
Game
gmvanilla
Game modeYou play vanilla survival here.
mp3
Max playersIts slot count is 3.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is 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 standing (C+); uptime is the one to work on (F).