Rust Data

rustdata.spaceservers89.43.208.247:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 89.43.208.247:28015 checked 1h ago

Savage Sands

moddedoxide

Connect

srv = rust.server("89.43.208.247:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 2
rank #6,896 # top 31%
last wipe 14d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5202:0007:0012:0017:0022:0000:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020002:0007:0012:0017:0022:0000:00

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 31% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

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

The first 48 hours of its last wipes

Wed 14 OctTue 13 OctThu 1 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 14 Oct, 22:32 UTC14d ago 1 NaN running 0
1 Tue 13 Oct, 18:08 UTC15d ago 1 NaN 1.2 days 0
2 Thu 1 Oct, 18:09 UTC FW27d ago 2 held half 12 days 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.

display(srv.map, srv.info())

Map

5000 · seed 1411653045
Map of Savage Sands
map
Custom Map
size
5000
seed
1411653045

Server

srv.info()
address
89.43.208.247:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
14 Oct 2026, 22:32 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 155 on average34/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average135/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average34/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average28/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average4/1000

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Savage Sands rank?

Player hours over seven days put Savage Sands at #6,896, in the top 31% of the ranked set.

How full does Savage Sands run?

The current row shows Savage Sands offline; the last response was 1 hours ago. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 21:00 UTC, averaging 2 players.

Server data

How well does Savage Sands perform?

Averaged over 48 hours: 116 server fps, never under 96. The entity count peaked at 155,456, covering buildings, deployables and the rest of the world. A high of 4,128 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on Savage Sands?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Savage Sands. Joining needs the same protocol on your game; Steam handles the update.

Is Savage Sands up, and what does its uptime show?

Offline now for Savage Sands, last seen 1 hours ago. The uptime it reports puts the last restart about 1 hours ago. Over the last 7 full days the hours up number 147 of 168, 88%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Savage Sands sit?

For Savage Sands, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 89.43.208.247:28015.

Map and rules

What rules and settings are recorded for Savage Sands?

You will not find a gather rate in the string Savage Sands. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

What is the map on Savage Sands?

Size 5,000, seed 1411653045: the procedural map on Savage Sands, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.

Wipes and dates

When does Savage Sands wipe, and on what schedule?

Irregular wipe times on Savage Sands leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 14 days 2 hours ago, and that is the one in play.

On Savage Sands, what happens on wipe day?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Tags, lists

Which lists on Rust Data hold Savage Sands, and which filters?

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

How should you read the server tags on Savage Sands?

These tags are published by Savage Sands and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

How can I connect to Savage Sands?

The manual route: launch Rust, F1, then client.connect 89.43.208.247:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players The server lists 50 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change 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.

Rust Data 43,056 players 11,700 servers online