Rust HeatmapInfrared · players
IR live Players61,343 Servers11,769 Warm3,535 Fresh wipes · 3h127 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 1° now Linear · 0–50° · slots

Savage Sands

Online 89.43.208.247:28015 checked 5m ago

moddedoxide
Sp1 · players now 1/ 50
2% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 2°
Mon 23:00flare: a wipe in that hourWed 00:00
0
7-day average
peak 2
#6,957
rank
top 31%
13d ago
last wipe
no schedule published
–
next wipe
no rhythm it keeps
UTC checked 5m ago

Li2Players

AveragePeak
00.511.5223:0004:0009:0014:0019:0000:00

Hourly average and peak, UTC.

Li3Server performance

05010015020023:0004:0009:0014:0019: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.

Li4Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Bx1Wipe 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.

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

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
Wed 14 Oct, 22:32 UTC13d ago 1 – running 0
Tue 13 Oct, 18:08 UTC15d ago 1 – 1.2 days 0
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 157 on average
85 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
133 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 116 on average
78 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 91 on average
67 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 88 on average
20 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 84 on average
9 / 1000

LogQuick answers

from the figures on this page

Wipe schedule

What does wipe day look like on Savage Sands?

The average peak across its recent wipes is 1 players. 0 hours into the latest wipe, player numbers topped out. Half the peak was held until the next wipe in 100% of its recent wipes.

What is the wipe schedule on Savage Sands?

Wipes come at irregular times on Savage Sands, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. 13 days 23 hours ago the server made the world it is on now.

Population

How busy is Savage Sands?

Savage Sands currently has 1 of its 50 slots filled. A seven-day average of 0 players, with a peak of 2. Its busiest point in the last 48 hours was 21:00 UTC, averaging 2 players.

How does Savage Sands rank against other Rust servers?

Ranked #6,957 on seven-day player hours, Savage Sands is in the top 31% of all ranked servers.

Settings and rules

Which map does Savage Sands run?

Savage Sands runs a procedural map of size 5,000 with seed 1411653045, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map. The map is called Custom Map.

What are the rules and settings on Savage Sands?

A gather rate is not given in the name Savage Sands. Groups can contain up to 8 players, the default in the game. The server runs survival, standard play: gathering, building and raiding. Combat between players and raiding are both possible. In the server browser it is Modded, meaning plugins or settings modify the game. Oxide plugins are in use. VAC is on, which is Valve's anti-cheat.

Location and uptime

Which version of Rust does Savage Sands run?

The build on Savage Sands is Rust network protocol 2635 and build 168909, running on Linux. Steam updates your game for you, and the protocol has to match for you to join.

Is Savage Sands online, and how reliable is it?

Right now Savage Sands shows as online. The uptime it reports puts the last restart at about 23 hours ago. 168 of 168 hours up over the last 7 full days, which is 100%. It first appears in Rust Heatmap records on 13 September 2026.

Where is Savage Sands located?

A region is not published for Savage Sands. Rust Heatmap shows the location a server states. It does not look up the machine's location. You can reach it at 89.43.208.247:28015.

Does Savage Sands run smoothly?

Average server fps over the last 48 hours was 115; it never dropped below 96. Entities peaked at 155,456, counting buildings, deployables and all the rest of the world. The highest memory use was 4,128 MB. Lag, as players experience it, comes from low fps and a rising entity count.

Lists and filters

Which Rust Heatmap lists and filters include Savage Sands?

The Rust Heatmap lists that Savage Sands fits are: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

What do the server tags on Savage Sands mean?

gmrust (Game mode): Rust survival, standard rules; mp50 (Max players): The slot count is 50; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): No region code is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): The game is changed by settings or plugins, so it sits under Modded are the tags Savage Sands publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.

Connect

How do I join Savage Sands?

Press F1 in Rust to open the console, then enter client.connect 89.43.208.247:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.

KeyServer tags

what each one means

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

Game

gmrust
Game mode Rust survival, standard rules.
mp50
Max players The slot count is 50.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol The server runs game protocol 2635, so your game has to match it.
cs168909
Build Build 168909.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded The game is changed by settings or plugins, 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.