Rust Server TrendsSeismic network · station log
Recording Stations11,701 Players54,561 Active3,263 Wipes · 3 h144 48 h

Station XX-6912 · no signal

Savage Sands

Offline 89.43.208.247:28015 checked 10h ago

moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 2
Rank
#6,912
top 31%
Last wipe
14d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-6912 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+2into Tue 21:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5211:0014:0017:0021:0000:0000:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020011:0014:0017:0021:0000: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.

Channel 3 · rank movement

Rank

daily · 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.

Expected events

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 gap
6.6 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
100%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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 14 Oct, 22:32 UTC14d ago M0.0rising 1 – running 0
Tue 13 Oct, 18:08 UTC15d ago M0.0rising 1 – 1.2 days 0
Thu 1 Oct, 18:09 UTC FW27d ago M0.3rising 2 held half 12 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 149 on average
130/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
122/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
192/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
73/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
10/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
17/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Savage Sands?

Generated by the game, the map on Savage Sands is procedural, size 5,000 with seed 1411653045. Size and seed produce the same map, so RustMaps can show it from this page. Its map carries the name Custom Map.

Which settings and rules apply on Savage Sands?

No gather rate appears in the name of Savage Sands. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on Savage Sands?

Savage Sands is not responding at this moment and is offline, last seen 10 hours ago. Averaged across the last seven days the population was 0 players, reaching a peak of 2. The busiest point in the last 48 hours came at 21:00 UTC, averaging 2 players.

How does Savage Sands rank against other Rust servers?

On player hours for the past week, Savage Sands sits at #6,912, which puts it inside the top 31% of every ranked server.

Server details

How reliably does Savage Sands stay online?

As recorded now, Savage Sands is not reachable, the last contact having been 10 hours ago. Going by the uptime figure it reports, it restarted about 1 hours ago. 147 of 168 hours in the last 7 full days were up time, 88% of the total. 13 September 2026 is when Rust Server Trends first recorded it.

How well does Savage Sands perform under load?

The 48-hour average is 115 server fps; 96 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 155,456. Its highest memory use was 4,128 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does Savage Sands run from?

Nothing about a region comes from Savage Sands. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 89.43.208.247:28015.

What build of Rust does Savage Sands use?

Rust network protocol 2635 and build 168909 on Linux is what Savage Sands runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on Savage Sands?

The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

On what timetable does Savage Sands run its wipes?

There is no next wipe to predict at Savage Sands, since its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 14 days 11 hours.

Server tags

What do the server tags on Savage Sands mean?

Tags published by Savage Sands and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Savage Sands appear?

These Rust Server Trends lists include Savage Sands: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

What steps get you onto Savage Sands?

To join, enter client.connect 89.43.208.247:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players 50 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.