Rust StatisticsWorking papers on every public Rust server · 96,179 players now

breaking rustories

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 8m ago · 15.204.174.114:28015

Abstract

We describe the public Rust server breaking rustories, reached at 15.204.174.114:28015. At the last check it held 0 of 50 places, against a seven-day mean of 01. It ranks #15,269 of all servers, the top 68%. It last wiped 28d ago; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/500% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,269top 68%
Last wipe28d agono schedule published
Next wipe36d 22hThu 5 Nov, 19:00 UTCfw

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123421:0006:0015:0001:0010:0019:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
01020304021:0006:0015:0001:0010:0019:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 68% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: force wipes only

The next wipe is expected Thursday 5 November, 19:00 UTC, in 6d 22h. The force wipe (high confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak1players, last three wipes
Table 3: Coming wipes, as expected.
When (UTC)InKind
Thu 5 Nov, 19:006d 22hforce wipefw
Thu 3 Dec, 19:0034d 22hforce wipefw
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 4: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 1 Oct, 18:35fw28d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of breaking rustories
Figure 5: The map: Procedural Map, size 4500, seed 5369. Open on RustMaps.
Table 5: The server's published settings.
Address15.204.174.114:28015
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe1 Oct 2026, 18:35 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size4500
Seed5369

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust servers listed live [2] and upcoming Rust wipes [3].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 151 on average75/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average126/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average137/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average44/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 91 on average133/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average348/350

Appendix AQuick answers

From the figures on this page.

Server details

A.1Does breaking rustories perform well?

Its average server fps over the last 48 hours was 29, with a minimum of 3. Its entity count reached a maximum of 137,862, including buildings, deployables and all other world objects. Memory use peaked at 8,224 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What is the location of breaking rustories?

There is no region published for breaking rustories. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 15.204.174.114:28015 is its address.

A.3How reliable is breaking rustories, and is it currently online?

breaking rustories is currently online. Based on the uptime it reports, the last restart occurred about 6 days 12 hours ago. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first observed on 13 September 2026 by Rust Statistics.

A.4What is the Rust version for breaking rustories?

Rust network protocol 2634 and build 166494 is the version that breaking rustories runs, on Linux. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.5When are wipes carried out on breaking rustories?

Once a month, breaking rustories wipes in line with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe occurs, and that is when every Rust server, including this one, next wipes. 28 days 2 hours have passed since the current world was generated.

A.6What happens on breaking rustories when wipe day arrives?

The average busiest point of recent wipes was 1 players. The crowd reached its maximum 35 hours after the latest wipe.

Population

A.7What position does breaking rustories occupy in the ranking of Rust servers?

Ranked by player hours across seven days, breaking rustories holds #15,269, in the top 68% of all ranked servers.

A.8How would you characterise the player activity on breaking rustories?

At this moment 0 players are on breaking rustories, which has 50 slots in total. The seven-day average for this server is 0 players.

Tags and filters

A.9How should the tags on breaking rustories be interpreted?

gmvanilla (Game mode): Survival on vanilla rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs166494 (Build): This server runs game build 166494; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags breaking rustories publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.10Where can breaking rustories be found among the Rust Statistics lists and filters?

The Rust Statistics lists that breaking rustories fits are: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.11What are the settings and rules that govern breaking rustories?

The name of breaking rustories states no gather rate. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means the standard mode, in which you gather, build and raid. Players may raid and fight one another. It appears under Modded in the browser: the game is changed by plugins or settings. Oxide plugins are running. The server has VAC on, Valve's anti-cheat.

A.12What map is in use on breaking rustories?

Size 4,500 and seed 5369 define the procedural, game-generated map on breaking rustories. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

Connection

A.13What steps are required to join breaking rustories?

Press F1 inside Rust to open the console and enter client.connect 15.204.174.114:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2634,gmvanilla,cs166494,ts8,^o^z.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmvanillaGame mode. Survival on vanilla rules.
mp50Max players. 50 slots are available.
ts8Group limit. 8 per team, the value the game sets by default.
v2634Protocol. Joining requires the same game version: protocol 2634.
cs166494Build. This server runs game build 166494.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. The game is altered by plugins or settings, so 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.