On the class lists: C+ (68), with population over 48 hours and no performance mark.
Players now31/ 5062% full
7-day average12peak 43
Rank#867top 4%
Last wipe118d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
23/ 100
F
A quiet classroom so far: 12 of 50 on average. Plenty of space to grow.
Standingrank on player hours
96/ 100
A+
Well up the rankings: #867 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 60 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
55/ 100
C−
Moving up: up 83 places this week.
A steady term.
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
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 4% 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
You'll find no region listed by ShockRust | Fight. Rust Server Score takes the server's word for its location and does not trace the hardware. 185.207.214.212:35200 is the address to use.
Is ShockRust | Fight up, and how steady is its uptime?
The server is up: ShockRust | Fight is online now. About 16 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Does ShockRust | Fight perform well?
The average over the last 48 hours was 60 server fps, and it never went below 58. Up to 5,289 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 1,252 MB of memory. Players feel lag when fps drops and entities pile up.
Which Rust version is ShockRust | Fight running?
Rust network protocol 2556 and build 104046 on Linux is what ShockRust | Fight runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does ShockRust | Fight wipe its map?
The record holds too few of ShockRust | Fight's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 118 days 18 hours have passed since this world was made.
Player numbers
What position does ShockRust | Fight hold in the rankings?
In the top 4% of all ranked servers, ShockRust | Fight sits at #867 for player hours over the last seven days.
How many players does ShockRust | Fight usually have?
With 50 slots available, ShockRust | Fight currently has 31 players. Averaging 12 players over seven days, it peaked at 43. The highest average in the last 48 hours came at 14:00 UTC, with 31 players.
Tags
How should you read the tags on ShockRust | Fight?
You'll see ShockRust | Fight tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 slots; v2556 (Protocol): The game protocol is 2556, so your game must match that version to join; cs104046 (Build): Build number: 104046; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does ShockRust | Fight appear in the Rust Server Score lists and filters?
These Rust Server Score lists count ShockRust | Fight among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Players now: At least 10; Average players: 10+ on average.
Rules and settings
What settings and rules apply on ShockRust | Fight?
You will find no gather rate in the name of ShockRust | Fight. It publishes no limit on group size. You get survival 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. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map ShockRust | Fight uses?
A procedural map of size 1,500 and seed 1337, generated by the game, is what ShockRust | Fight runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.
How to join
What is the way to join ShockRust | Fight?
Enter client.connect 185.207.214.212:35200 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?,v2556,gmrust,cs104046,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 slots.
v2556
ProtocolThe game protocol is 2556, so your game must match that version to join.
cs104046
BuildBuild number: 104046.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it 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 steady term. Strongest in performance (A+); population is the one to work on (F).