On the class lists: F (24), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak 1
Rank#14,818top 67%
Last wipe27d agomonthly schedule
Next wipe7d 7hThu 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 40 on average. Plenty of space to grow.
Standingrank on player hours
33/ 100
F
Working its way up from the back of the class: #14,818 on player hours.
Uptimehours on the list, last 48
38/ 100
F
Attendance needs work: on the list only 18 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 216 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 307 places this week.
A term to build on.
Strongest in performance (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
No five-minute samples in the last two hours.
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 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
···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 7h.
The force wipe · high confidence
usual gap4.8 daysbetween real wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 1
Coming wipes
7d 7hThu 5 Nov, 19:00 UTCFW
35d 7hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 1 OctSun 27 Sep
Players each hour, from the hour of the wipe. The latest peaked at 3, 10 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 23:20 UTCFW27d ago
3
–
running
0
Sun 27 Sep, 04:02 UTC32d ago
3
halved by day 1
4.8 days
3
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
The White shark leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 103.15.237.141:22919 is the address to use.
How reliable is The White shark, and is it up?
You cannot join now: The White shark is offline, last seen 30 hours ago. About 46 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 150 of 168 hours, or 89% of the time. It was first seen by Rust Server Score on 26 September 2026.
Is The White shark smooth to play on?
The average over the last 48 hours was 216 server fps, and it never went below 203. Up to 49,119 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 4,264 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is The White shark running?
Rust network protocol 2635 and build 167781 on Linux is what The White shark runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does The White shark reset?
The White shark 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. 27 days 11 hours have passed since this world was made. Its tags list a monthly wipe schedule.
What should you expect from wipe day on The White shark?
The average peak on its recent wipes was 3 players. 10 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player count
What position does The White shark hold in the rankings?
In the top 67% of all ranked servers, The White shark sits at #14,818 for player hours over the last seven days.
Is The White shark a busy server?
The last sighting of The White shark was 30 hours ago, and it is offline right now. Averaging 0 players over seven days, it peaked at 1.
Tags and filters
What do The White shark's tags stand for?
The game's browser takes its cue from the tags The White shark has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $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; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. 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 The White shark appear in the Rust Server Score lists and filters?
Rust Server Score lists that include The White shark: Modded Rust servers, graded. You can find it under these server-list filters: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
What settings and rules apply on The White shark?
Nothing in the name of The White shark states a gather rate. 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. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. VAC, Valve's anti-cheat, is enabled.
Which map is in play on The White shark?
The White shark runs a game-generated procedural map at size 3,000, seed 50000. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to The White shark?
To connect, start Rust, press F1, and type client.connect 103.15.237.141:22919. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,^m,^v,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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
^o
OxidePlugin framework: Oxide (uMod).
^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 performance (A+); population is the one to work on (F).