Rust StatisticsWorking papers on every public Rust server · 61,093 players now

Savage Sands

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 11h ago · 89.43.208.247:28015

Abstract

We describe the public Rust server Savage Sands, reached at 89.43.208.247:28015. It is offline at the last check, against a seven-day mean of 0 and a peak of 21. It ranks #6,912 of all servers, the top 31%. It last wiped 14d ago.

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 2, 48 h peak 2
Rank2#6,912top 31%
Last wipe14d agono schedule published
Next wipe3–no rhythm it keeps

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
00.511.5212:0015:0018:0021:0000:0000: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
05010015020012:0015:0018:0021:0000:0000: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 31% 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
12.5k5k7.5k10k20 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: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap6.6 daysbetween real wipes
On rhythm0%of its recent wipes
Wipe-day peak1players, last three wipes
Crowd held100%of its cycles kept half the crowd
Wed 14 OctTue 13 OctThu 1 Oct
00.511.52+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, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Wed 14 Oct, 22:3214d ago 1 – running 0
Tue 13 Oct, 18:0815d ago 1 – 1.2 d 0
Thu 1 Oct, 18:09fw27d ago 2 held half 12 d 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 Savage Sands
Figure 5: The map: Custom Map, size 5000, seed 1411653045.
Table 4: The server's published settings.
Address89.43.208.247:28015
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe14 Oct 2026, 22:32 UTC
Hostname–
First seen13 Sep 2026
MapCustom Map
Size5000
Seed1411653045

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 149 on average159/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average132/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average189/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average78/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average10/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average23/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Is the performance of Savage Sands smooth?

The server fps averaged 114 over the last 48 hours, never dropping below 96. The highest number of entities it carried was 155,456, comprising buildings, deployables and all other objects. Its highest memory usage was 4,128 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2In which location is Savage Sands based?

A region is not published by Savage Sands. Rust Statistics does not look up the machine's location; it shows where the server says it is. 89.43.208.247:28015 is its address.

A.3What is the online status and reliability of Savage Sands?

Savage Sands is currently offline, with the last sighting 11 hours ago. The uptime it reports indicates a restart about 1 hours ago. Its uptime over the last full days (7 days) was 88%, with 147 of 168 hours online. It was first observed on 13 September 2026 by Rust Statistics.

A.4What is the Rust version for Savage Sands?

Rust network protocol 2635 and build 168909 is the version that Savage Sands runs, on Linux. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5When are wipes carried out on Savage Sands?

With irregular wipe times, Savage Sands offers no next wipe to predict. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 14 days 12 hours have passed since the current world was generated.

A.6What characterises wipe day on Savage Sands?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 0 hours after the latest wipe. For 100% of recent wipes, the population did not fall below half the peak before the next wipe.

Population

A.7What is the rank of Savage Sands among Rust servers?

Ranked by player hours across seven days, Savage Sands holds #6,912, in the top 31% of all ranked servers.

A.8How would you characterise the player activity on Savage Sands?

Savage Sands is not online now; 11 hours have passed since it was last seen. The peak over seven days is 2, against an average of 0. The busiest hour of the last 48 is 21:00 UTC, averaging 2 players.

Tags, lists

A.9What do the tags associated with Savage Sands signify?

Tags from Savage Sands, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp50 (Max players): It offers 50 slots; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game. 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 Savage Sands be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Savage Sands fits are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.11Under what rules and settings does Savage Sands operate?

No gather rate appears in the name of Savage Sands. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.

A.12What is the map for Savage Sands?

Size 5,000 and seed 1411653045 define the procedural, game-generated map on Savage Sands. Because size and seed determine the map, RustMaps can show it, linked from this page. Under map name, it gives Custom Map.

Connection

A.13What steps are required to join Savage Sands?

Enter client.connect 89.43.208.247:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp50Max players. It offers 50 slots.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. Modded listing: plugins or settings modify the game.

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 server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.