On the class lists: F (26), with population over 48 hours and no performance mark.
Players now0/ 10000% full
7-day average0peak –
Rank#15,388top 70%
Last wipe79d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 1,000 on average. Plenty of space to grow.
Standingrank on player hours
30/ 100
F
Working its way up from the back of the class: #15,388 on player hours.
Uptimehours on the list, last 48
27/ 100
F
Attendance needs work: on the list only 13 of the last 48 hours.
Performanceserver fps, last 48 hours
99/ 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
49/ 100
D
Slipped a little: down 158 places this week. Nothing a good wipe can't fix.
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 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 70% 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
No region is published for Die Jedi Scum. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 64.31.32.2:28015.
How dependable is Die Jedi Scum, and is it online at the moment?
The server is down: Die Jedi Scum is offline now, with the last sighting 34 hours ago. The uptime it reports puts the last restart at about 22 hours ago. It was up 92% of the time over the last 7 full days, 154 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Does Die Jedi Scum perform well?
The average over the last 48 hours was 60 server fps, and it never went below 56. At its peak, it held 82,725 entities, including buildings, deployables and all else in the world. At its highest, it used 2,102 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is Die Jedi Scum running?
You will find Die Jedi Scum on Rust network protocol 2632 and build 161125, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does Die Jedi Scum reset?
Die Jedi Scum has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 79 days 18 hours.
Player numbers
Where does Die Jedi Scum place in the wider field of Rust servers?
In the top 70% of all ranked servers, Die Jedi Scum sits at #15,388 for player hours over the last seven days.
How many players does Die Jedi Scum usually have?
Die Jedi Scum is offline at the moment; the last time it was seen was 34 hours ago. For the last seven days, the average number of players was 0.
Tags
What do Die Jedi Scum's tags stand for?
You'll see Die Jedi Scum tagged with gmrust (Game mode): Survival in the standard Rust style; mp1000 (Max players): 1,000 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2632 (Protocol): The game protocol is 2632, so your game must match that version to join; cs161125 (Build): This runs on build 161125; 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): 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.
Which Rust Server Score filters and lists feature Die Jedi Scum?
These Rust Server Score lists count Die Jedi Scum among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does Die Jedi Scum enforce, and what are its settings?
Nothing in the name of Die Jedi Scum states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server does not run VAC, Valve's anti-cheat.
Die Jedi Scum runs which map?
A procedural map of size 3,750 and seed 571006982, generated by the game, is what Die Jedi Scum runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
What is the way to join Die Jedi Scum?
To connect, start Rust, press F1, and type client.connect 64.31.32.2:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://qonix.co.
Server tags
what each one means
Published asmp1000,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1000
Max players1,000 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2632
ProtocolThe game protocol is 2632, so your game must match that version to join.
cs161125
BuildThis runs on build 161125.
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
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 term to build on. Strongest in performance (A+); population is the one to work on (F).