On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,262top 69%
Last wipe28d agono schedule published
Next wipe6d 18hThu 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 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,262 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
48/ 100
D
Needs to work on its frame rate: 29 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
50/ 100
D
Holding steady: down 137 places this week.
A term to build on.
Strongest in uptime (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 69% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···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 6d 18h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
6d 18hThu 5 Nov, 19:00 UTCFW
34d 18hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 35 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:35 UTCFW28d ago
1
–
running
0
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 breaking rustories. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 15.204.174.114:28015.
How dependable is breaking rustories, and is it online at the moment?
You can join now: breaking rustories is online. About 6 days 16 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 143 of 168 hours, or 85% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does breaking rustories perform well?
It averaged 29 server fps over the last 48 hours, with a low of 3. Up to 137,862 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 8,224 MB. When fps is low and entities climb, that is lag to players.
What Rust version is breaking rustories on?
You will find breaking rustories on Rust network protocol 2634 and build 166494, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does breaking rustories wipe its map?
The force wipe each month is the only wipe breaking rustories takes. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 28 days 6 hours have passed since this world was made.
What happens on breaking rustories when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 35 hours into the latest wipe.
Population
Where does breaking rustories sit among Rust servers?
In the top 69% of all ranked servers, breaking rustories sits at #15,262 for player hours over the last seven days.
What does the population on breaking rustories look like?
Right now, 0 players are on breaking rustories, which has 50 slots. A seven-day average of 0 players applies here.
Tags and filters
What is meant by the tags on breaking rustories?
gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): Its slot count is 50; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): Build number: 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags breaking rustories publishes, and the game's server browser reads them. 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 breaking rustories appear in the Rust Server Score lists and filters?
These Rust Server Score lists count breaking rustories among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does breaking rustories enforce, and what are its settings?
Nothing in the name of breaking rustories states a gather rate. With no change from the game default, groups take up to 8 players. You get survival 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map breaking rustories uses?
A procedural map of size 4,500 and seed 5369, generated by the game, is what breaking rustories runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto breaking rustories?
To connect, start Rust, press F1, and type client.connect 15.204.174.114:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmvanilla,cs166494,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max playersIts slot count is 50.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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 uptime (A+); population is the one to work on (F).