StatusLive Servers online11,623 Players37,934 Populated2,921 Wiped · 3 h81 Interval5 min Date29 OCT 2026

DWG RG-S5002Server sheetchecked 15m ago

Salty Test #1

Online 194.69.160.182:28015 checked 15m ago

moddedcarbon
Connect
Players now 0/ 20 0% full
7-day average0peak 2
Rank#5,002top 22%
Last wipe2d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.250.50.75108:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Fig. 1Players on Salty Test #1
Fig. 2

Server performance

025507510008:0017:0002:0011:0021:0006: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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 gap2.5 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 00:50 UTC2d ago 1 – running 0
Thu 1 Oct, 17:10 UTC FW27d ago 1 halved by day 9 25.3 days 3
Tue 29 Sep, 06:22 UTC30d ago 1 held half 2.5 days 0
Mon 28 Sep, 08:22 UTC30d ago 1 – 0.9 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 150 on average
71 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
130 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
109 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
37 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
4 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
10 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

What uptime is recorded for Salty Test #1, and is it up?

Right now, Salty Test #1 is recorded as online. About 2 days 5 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 13 September 2026.

What does the recorded performance of Salty Test #1 show?

92 server fps on average over the last 48 hours, and never under 20. Counted at its highest: 91,914 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 8,705 MB. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for Salty Test #1?

No region is published by Salty Test #1. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 194.69.160.182:28015.

What Rust version is recorded for Salty Test #1?

On Linux, Salty Test #1 runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.

Population

What player count is recorded on Salty Test #1?

At the last refresh, Salty Test #1 recorded 0 players across 20 slots. The seven-day mean is 0 players; the peak over the same period is 2. The 48-hour peak falls at 10:00 UTC, averaging 1 players.

What rank has been recorded for Salty Test #1?

Player hours over seven days place Salty Test #1 at #5,002, within the top 22% of ranked servers.

Schedules

What happens on Salty Test #1 on the day of a wipe?

At their busiest, its recent wipes drew 1 players on average. At 1 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 50% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 9.

What wipe schedule has been recorded for Salty Test #1?

There is no next wipe to predict at Salty Test #1, which wipes at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 2 days 6 hours ago.

Rules and settings

Which rules and settings are recorded for Salty Test #1?

Gather rate for Salty Test #1: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Carbon. Anti-cheat: VAC, from Valve, is on.

What is the map for Salty Test #1?

Seed 1337 and size 4,500 define the procedural map Salty Test #1 generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The name of the map reads: Custom Map.

Filters

Where does Salty Test #1 appear among the Rust Graphs lists and filters?

These Rust Graphs lists include Salty Test #1: Modded Rust servers. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

Which meaning is attached to each tag on Salty Test #1?

gmrust (Game mode): Standard survival, as Rust plays; mp20 (Max players): The slot count is 20; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): The plugin framework is Carbon are the tags Salty Test #1 publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Joining the server

By what method do you join Salty Test #1?

In Rust, press F1 and type client.connect 194.69.160.182:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp20
Max players The slot count is 20.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Mods and access

^z
Modded The game is changed by plugins or settings; the listing is Modded.
^y
Carbon The plugin framework is Carbon.

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.

KeyTag string decoded