Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO G SRV11,814online PAX72,000playing OCC3,646with players WIPED 3H206
MODModded traffic
Callsign

SLT5067=

Salty Test #1

Online 194.69.160.182:28015 checked 8m ago

moddedcarbon
Clearance · join
Players now 1/ 20 5% full
7-day average0peak 2
Rank#5,067top 23%
Last wipe4h agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

AveragePeakWipe
00.250.50.75114:0023:0008:0016:0002:0011:00Wiped Thu 29 Oct, 08:44 UTCWIPE

Hourly average and peak, UTC.

Server performance

Server fpsWipe
025507510014:0023:0008:0016:0002:0011: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.

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.

Flight plan

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.4 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
crowd held67%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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 08:44 UTC4h ago – – running 0
Tue 27 Oct, 00:50 UTC2d ago 1 held half 2.3 days 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 UTC31d 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign SHC102no group limit · 149 on average ShockRust | Blue | NoLimit
    Players 169/500
  2. 02MOD
    Callsign STR581EU · groups of 8+ · weekly · 128 on average МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
    Players 128/100
  3. 03MOD
    Callsign RUS021EU · groups of 16+ · monthly · 94 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
    Players 81/700
  4. 04MOD
    Callsign RST016EU · groups of 12+ · weekly · 88 on average RustSpain.com | EU Main
    Players 23/200
  5. 05MOD
    Callsign RUS021EU · groups of 16+ · monthly · 84 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
    Players 25/1000
  6. 06MOD
    Callsign RUS029EU · groups of 16+ · monthly · 84 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10
    Players 265/700
ATIS · this server

Quick answers

From the figures on this page.

Tags

Where does Salty Test #1 appear in Rust Tracker lists and filters?

On Rust Tracker, Salty Test #1 sits in these lists: Modded servers, tracked live. These filters surface it 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 should you read the tags on Salty Test #1?

Listed for the server browser to read, Salty Test #1 publishes these tags: gmrust (Game mode): Standard survival mode for Rust; mp20 (Max players): 20 slots on this server; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset; ^z (Modded): Under Modded: the game is changed by plugins or settings; ^y (Carbon): Carbon is installed — a plugin framework. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Times

What happens on Salty Test #1 on wipe day?

The average peak across recent wipes: 1 players. The peak on the latest wipe came 1 hours after it. The crowd stayed above half the peak until the next wipe in 67% of recent wipes. The fall below half came by day 9 where it did not hold.

Which wipe times are confirmed for Salty Test #1?

Wipe times at Salty Test #1 are irregular, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. Its world went live 4 hours.

Server Details

What is the uptime on Salty Test #1, and is it online?

Tracking shows Salty Test #1 online as of now. About 2 hours ago it restarted last, based on reported uptime. 167 of 168 hours up over the last 7 full days: 99% uptime. The first sighting by Rust Tracker was 13 September 2026.

Which Rust version is confirmed on Salty Test #1?

Rust network protocol 2635 and build 168909 is the build on Salty Test #1; the platform is Linux. Steam updates it for you; your game must share the protocol to join.

How smoothly does Salty Test #1 run?

For the last 48 hours it averaged 92 server fps; the floor was 20. Peak entity count: 91,914, covering buildings, deployables and all else in the world. It drew as much as 8,705 MB of memory. A climbing entity count and low fps are what register as lag for players.

What location is Salty Test #1 hosted in?

Region: none published by Salty Test #1. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 194.69.160.182:28015.

Player Count

How many players are on Salty Test #1 right now?

Tracking Salty Test #1: 1 of 20 slots filled. Over seven days: average 0, peak 2 players. Busiest window in 48 hours: 10:00 UTC, 1 players on average.

How does Salty Test #1 compare in the rankings?

On player hours over seven days, Salty Test #1 ranks #5,067, inside the top 23% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on Salty Test #1?

No gather rate appears in Salty Test #1's name. The game's default applies: groups can have up to 8 players. It runs survival, gather, build and raid: the standard game. Players can raid and fight each other here. The server browser lists it under Modded, where plugins or settings change the game. The plugin count stands at Carbon. On: VAC, Valve's anti-cheat.

Which map is loaded on Salty Test #1?

Generated by the game from seed 1337, the procedural map on Salty Test #1 measures 4,500. Same size, same seed, same map. RustMaps shows it, linked from this page. Read the name of its map: Custom Map.

How to Join

How do you get onto Salty Test #1?

To connect: start Rust, press F1, enter client.connect 194.69.160.182:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp20
Max players 20 slots on this server.
ts8
Group limit Team limit is 8, the game default.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code The region code is unset.

Mods and access

^z
Modded Under Modded: the game is changed by plugins or settings.
^y
Carbon Carbon is installed — a plugin framework.

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.