Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players74,965 Active3,733 Wipes · 3 h252 48 h

Station XX-5084 · recording

Salty Test #1

Online 194.69.160.182:28015 checked 11m ago

moddedcarbon
Connect
Players now
1/ 20
5% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 2
Rank
#5,084
top 23%
Last wipe
5h ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-5084 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
1of 20 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−1into Wed 19:00 UTC
Peak · 48 h
1most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
00.250.50.75115:0000:0009:0017:0003:0012:00Wiped Thu 29 Oct, 08:44 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
025507510015:0000:0009:0017:0003:0012:00Wiped Thu 29 Oct, 08:44 UTCWIPE

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
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 23% 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
2.4 daysbetween real wipes
on rhythm
50%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
67%else halves by day 9

The first 48 hours of its last wipes

Tue 27 OctThu 1 OctTue 29 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 29 Oct, 08:44 UTC5h ago – – – – running 0
Tue 27 Oct, 00:50 UTC2d ago M0.0rising 1 held half 2.3 days 0
Thu 1 Oct, 17:10 UTC FW27d ago M0.3falling 1 halved by day 9 25.3 days 3
Tue 29 Sep, 06:22 UTC30d ago M0.0rising 1 held half 2.5 days 0
Mon 28 Sep, 08:22 UTC31d ago M0.0rising 1 – 0.9 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
192/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
121/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 119 on average
0/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average
80/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
36/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 85 on average
277/ 700
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Salty Test #1?

Generated by the game, the map on Salty Test #1 is procedural, size 4,500 with seed 1337. From this page you can look at it on RustMaps, since the same size and seed give the same map. You will find the map named Custom Map.

Which settings and rules apply on Salty Test #1?

You will find no gather rate in the name of Salty Test #1. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Carbon. Anti-cheat is on: VAC, from Valve.

Player counts

What is the current population on Salty Test #1?

1 of the 20 slots on Salty Test #1 are filled right now. The seven-day average is 0 players, with a peak of 2. The busiest point in the last 48 hours came at 10:00 UTC, averaging 1 players.

How does Salty Test #1 rank against other Rust servers?

On player hours for the past week, Salty Test #1 sits at #5,084, which puts it inside the top 23% of every ranked server.

Operator and location

How reliably does Salty Test #1 stay online?

As recorded now, Salty Test #1 is running. The uptime it reports puts its last restart about 3 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.

Does Salty Test #1 hold a steady tick rate?

Across the last 48 hours it averaged 92 server fps, with a floor of 20. The world held up to 91,914 entities at its peak, buildings and deployables included. It reached a ceiling of 8,705 MB of memory. Low fps together with a growing entity count is what players experience as lag.

Where in the world is Salty Test #1 hosted?

No region is published by Salty Test #1. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 194.69.160.182:28015.

What build of Rust does Salty Test #1 use?

Rust network protocol 2635 and build 168909 on Linux is what Salty Test #1 runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on Salty Test #1?

The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 1 hours after the wipe. The crowd stayed above half that peak until the next wipe in 67% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 9.

How often does Salty Test #1 wipe, and on which days?

No next wipe can be predicted for Salty Test #1, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 5 hours.

Tags

What do the server tags on Salty Test #1 mean?

The game's server browser reads the tags Salty Test #1 publishes: gmrust (Game mode): Survival in standard Rust; mp20 (Max players): Slots: 20; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Salty Test #1 appear?

These Rust Server Trends lists include Salty Test #1: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.

How to join

What steps get you onto Salty Test #1?

You can connect by pressing F1 in Rust and typing client.connect 194.69.160.182:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp20,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players Slots: 20.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.