On the class lists: D (47), with population over 48 hours and no performance mark.
Players now1/ 1001% full
7-day average0peak 2
Rank#6,091top 27%
Last wipe7d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
73/ 100
B−
Holds a respectable place: #6,091 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: 149 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
66/ 100
C+
Climbing fast: up 1,960 places this week.
A fair term, with more to come.
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 27% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
··WF···
·······
·······
··WW···
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap6.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2.5
The first 48 hours of its last wipes
Thu 22 OctWed 21 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 6 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 05:02 UTC7d ago
2
–
running
0
Wed 21 Oct, 17:42 UTC7d ago
2
–
0.5 days
0
Thu 1 Oct, 18:03 UTCFW27d ago
3
halved by day 2
20 days
0
Wed 30 Sep, 17:12 UTC28d ago
3
–
1 days
0
Fri 18 Sep, 08:06 UTC40d ago
8
halved by day 3
12.4 days
1
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
SCUF | RUST x0.5 | Events leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 31.163.205.44:28015.
Is SCUF | RUST x0.5 | Events up, and how steady is its uptime?
Right now, SCUF | RUST x0.5 | Events is online. According to its reported uptime, the last restart was about 2 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does SCUF | RUST x0.5 | Events perform well?
The average over the last 48 hours was 149 server fps, and it never went below 91. At its peak, it held 74,828 entities, including buildings, deployables and all else in the world. At its highest, it used 2,857 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does SCUF | RUST x0.5 | Events sit?
The server SCUF | RUST x0.5 | Events is on Rust network protocol 2635 and build 168909 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does SCUF | RUST x0.5 | Events reset?
There is no next wipe to predict on SCUF | RUST x0.5 | Events, as it wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 7 days have passed since this world was made.
What happens on SCUF | RUST x0.5 | Events when wipe day arrives?
Recent wipes have peaked at 2 players on average. The crowd on the latest wipe was largest 6 hours after it began. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 2.5.
Player count
What position does SCUF | RUST x0.5 | Events hold in the rankings?
Over the last seven days, SCUF | RUST x0.5 | Events has #6,091 for player hours, in the top 27% of all ranked servers.
How many players does SCUF | RUST x0.5 | Events usually have?
SCUF | RUST x0.5 | Events is showing 1 players right now, with 100 slots in total. It peaked at 2 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 16:00 UTC, with an average of 2 players.
Tags
What is meant by the tags on SCUF | RUST x0.5 | Events?
The game's browser takes its cue from the tags SCUF | RUST x0.5 | Events has set: gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): 100 slots are available; 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; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^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. 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 SCUF | RUST x0.5 | Events?
These Rust Server Score lists count SCUF | RUST x0.5 | Events among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
How is SCUF | RUST x0.5 | Events set up, and what rules does it keep?
Going by its name, SCUF | RUST x0.5 | Events runs 0.5x gather. 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. Oxide plugins are running on it. By its own description it is vanilla: facepunch's own version, with no changed rates, kits or rules. VAC, Valve's anti-cheat, is enabled.
SCUF | RUST x0.5 | Events runs which map?
The game generates the procedural map on SCUF | RUST x0.5 | Events at size 3,500 with seed 943512430. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto SCUF | RUST x0.5 | Events?
Enter client.connect 31.163.205.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 asmp100,ptrak,$r?,v2635,^v,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max players100 slots are available.
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.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).