Skip to the page
Network live 11,824 servers online 96,179 players aboard 529 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

Salty Test #2

Online 194.69.160.182:28025 checked 12m ago

moddedcarbon
Tracking number · connect
Wipe progress · wiped 4d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 20 players now 0% full
07-day averagepeak 1
#11,446ranktop 51%
4d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
0123421:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC.

Server performance

02040608021:0006:0015:0001:0010:0019: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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

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.

1.3 daysusual gapbetween real wipes
25%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 1

The first 48 hours of its last wipes

Wed 30 SepTue 29 SepMon 28 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, 0 hours in.

Wipes

every wipe as a delivery, newest first
  1. Sat 24 Oct, 23:13 UTC 00:13 UK · 4d ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Thu 22 Oct, 15:15 UTC 16:15 UK · 7d ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    –
    Players before
    1
  3. Wed 21 Oct, 16:07 UTC 17:07 UK · 8d ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    –
    Players before
    0
  4. Tue 20 Oct, 18:08 UTC 19:08 UK · 9d ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    –
    Players before
    1
  5. Mon 19 Oct, 15:49 UTC 16:49 UK · 10d ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    –
    Players before
    0
  6. Fri 16 Oct, 21:19 UTC 22:19 UK · 12d ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    –
    Players before
    0
  7. Thu 15 Oct, 13:55 UTC 14:55 UK · 14d ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    –
    Players before
    0
  8. Wed 30 Sep, 17:00 UTC 18:00 UK · 29d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    14.9 days
    Players before
    1
  9. Tue 29 Sep, 09:24 UTC 10:24 UK · 30d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    1.3 days
    Players before
    0
  10. Mon 28 Sep, 13:00 UTC 14:00 UK · 31d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    0.8 days
    Players before
    0
Show all 13 wipes
  1. Tue 22 Sep, 16:16 UTC 17:16 UK · 37d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    5.9 days
    Players before
    0
  2. Mon 21 Sep, 21:35 UTC 22:35 UK · 37d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    0.8 days
    Players before
    0
  3. Mon 21 Sep, 01:59 UTC 02:59 UK · 38d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    0.8 days
    Players before
    1

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.

Similar parcels

Similar servers

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

  1. ShockRust | Blue | NoLimitno group limit · 151 on average 75 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average 126 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average 137 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average 44 / 700
  5. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 91 on average 133 / 700
  6. RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average 348 / 350
Help desk

Quick answers

From the figures on this page.

Player activity

Where does Salty Test #2 place among Rust servers?

Over the past seven days, Salty Test #2 has climbed to #11,446 for player hours, putting it in the top 51% of all ranked servers.

What is the current population on Salty Test #2?

At the moment 0 players are on Salty Test #2, which has 20 slots. The seven-day figures show an average of 0 players and a peak of 1.

Rules and settings

On what map does Salty Test #2 take place?

Size 4,000 and seed 1337 define the procedural map Salty Test #2 runs, generated by the game. You can see the map on RustMaps from this page, since one size and seed give one map. Its name for the map: Custom Map.

Which settings and rules apply on Salty Test #2?

You will not find a gather rate in the name of Salty Test #2. 8 players is the group limit, since the game's default applies. It runs survival, gather, build and raid, as the standard game goes. Fighting and raiding between players is allowed. Because plugins or settings change the game, it is filed under Modded in the server browser. Plugins come from Carbon. The VAC anti-cheat from Valve is enabled.

Operator and location

In which region is Salty Test #2 based?

There is no region published for Salty Test #2. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. 194.69.160.182:28025 is its address.

How smoothly does Salty Test #2 run?

Averaged over the last 48 hours, server fps was 59, with a low of 43. The world held as many as 90,000 entities: buildings, deployables and the rest. The highest memory reading was 4,908 MB. What players call lag is the mix of low fps and an entity count that keeps climbing.

Is Salty Test #2 up, and how good is its uptime?

You can find Salty Test #2 online at present. About 4 days 18 hours ago is when it last restarted, judged by the uptime it gives. It was up 167 of 168 hours over the last 7 full days, 99% of the time. 17 September 2026 is when Rust Wipe Tracker first recorded it.

On what Rust version does Salty Test #2 operate?

On Linux, Salty Test #2 runs Rust network protocol 2635 and build 169075. The same protocol is required to join, and Steam takes care of updating it.

Map resets

How does Salty Test #2 handle its wipe days?

1 players is the average peak across its recent wipes. After 0 hours the latest wipe's crowd hit its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Where that did not hold, it dropped below half by day 1.

When does Salty Test #2 wipe? What schedule does it follow?

Salty Test #2 wipes when it chooses, not on a fixed rhythm, so there is no next wipe to predict. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. The world it is running was made 4 days 20 hours.

Tags and filters

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

You will find Salty Test #2 on the following Rust Wipe Tracker lists: Modded Rust servers. These are the filters that bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

What is the meaning of the server tags on Salty Test #2?

gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): The server has 20 slots; ts8 (Group limit): Team limit: 8, the standard default; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs169075 (Build): It runs game build 169075; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): No region code is set; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; ^y (Carbon): The plugin framework here is Carbon are the tags Salty Test #2 publishes, and the server browser takes them as read. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

Getting started

What steps do you take to join Salty Test #2?

Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 194.69.160.182:28025.

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp20
Max players The server has 20 slots.
ts8
Group limit Team limit: 8, the standard default.
v2635
Protocol Protocol 2635 is required; a different version can't join.
cs169075
Build It runs game build 169075.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code No region code is set.

Mods and access

^z
Modded The game is changed by plugins or settings, hence the Modded listing.
^y
Carbon The plugin framework here 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.