Working its way up from the back of the class: #11,963 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
19/ 100
F
Lost ground: down 7,365 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (D); momentum 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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 54% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 17 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 12:32 UTC26d ago
3
–
running
2
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
WHA_RUST_Server leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 133.88.116.44:28015 is the address to use.
How dependable is WHA_RUST_Server, and is it online at the moment?
At this moment, WHA_RUST_Server is offline; the last time it was seen was 21 days 18 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 20 September 2026.
Which Rust version is WHA_RUST_Server running?
You will find WHA_RUST_Server on Rust network protocol 2634 and build 166652, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does WHA_RUST_Server wipe, and how often?
WHA_RUST_Server 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. 26 days 19 hours have passed since this world was made.
What happens on WHA_RUST_Server when wipe day arrives?
Across its recent wipes, the busiest moments averaged 3 players. Peak numbers came 17 hours into the latest wipe.
Population
Where does WHA_RUST_Server sit among Rust servers?
Over the last seven days, WHA_RUST_Server has #11,963 for player hours, in the top 54% of all ranked servers.
How many players does WHA_RUST_Server usually have?
WHA_RUST_Server is offline at the moment; the last time it was seen was 21 days 18 hours ago.
Tags and filters
What do WHA_RUST_Server's tags stand for?
You'll see WHA_RUST_Server tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under 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 WHA_RUST_Server appear in the Rust Server Score lists and filters?
These Rust Server Score lists count WHA_RUST_Server among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does WHA_RUST_Server enforce, and what are its settings?
You will find no gather rate in the name of WHA_RUST_Server. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
WHA_RUST_Server runs which map?
The game generates the procedural map on WHA_RUST_Server at size 4,000 with seed 24994. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join WHA_RUST_Server?
Enter client.connect 133.88.116.44:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under 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 standing (D); momentum is the one to work on (F).