Rust PopulationField survey · Rust servers
Observing 65,587 players 11,740 servers 3,350 with someone on 201 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 5,003habitat unknownfirst seen 13 Sep 2026

Salty Test #1

Online 194.69.160.182:28015 checked 8m ago

moddedcarbon

Measurements

Players now
0/ 20
0% full
7-day average
0
peak 1
Rank
#5,003
top 22%
Last wipe
15h ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

AveragePeakWipe
00.250.50.75100:0009:0019:0004:0013:0022:00Wiped Thu 29 Oct, 08:44 UTCWIPE

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

Server fpsWipe
025507510000:0009:0019:0004:0013:0022: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.

Obs. 3 · standing

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.

Obs. 4 · the wipe cycle

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.

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

Log · wipes seen

Wipes

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

Field questions

Quick answers

from the figures on this page

Population

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

Over the past week it ranks #5,003 for player hours, which puts Salty Test #1 in the top 22% of all ranked servers.

How busy is Salty Test #1?

Of its 20 slots, Salty Test #1 is using 0 right now. We counted an average of 0 players in the past week, with 1 at the busiest. In the last 48 hours the peak hour came at 10:00 UTC, averaging 1 players.

Lists and 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): The game mode is standard Rust survival; mp20 (Max players): You can join up to 20 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): The region code is left blank; ^z (Modded): Plugins or settings change the game; it is listed under Modded; ^y (Carbon): The plugin framework Carbon runs on this server. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include Salty Test #1?

These Rust Population lists include Salty Test #1: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.

Wipe notes

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

The busiest point of its recent wipes averaged 1 players. Peak came 1 hours into the latest wipe. In 67% of recent wipes, half the peak was held until the next wipe. By day 9 it had fallen below half, in the cases where it did not hold.

What is the wipe schedule on Salty Test #1?

No next wipe can be predicted for Salty Test #1, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 15 hours ago.

Map and rules

Which map does Salty Test #1 run?

The map on Salty Test #1 is procedural, made by the game at size 4,500 from seed 1337. The map follows from its size and seed, and RustMaps shows it from this page. You will see the map named Custom Map.

What are the rules and settings on Salty Test #1?

Nothing in Salty Test #1's name says how gather works. No limit is set beyond the standard 8 players per group. survival is what it runs, the usual game, where you gather, build and raid. Fighting and raiding between players is allowed. The server browser files it under Modded, where plugins or settings alter the game. Carbon plugins are in use here. The anti-cheat VAC from Valve is enabled.

Server details

Which version of Rust does Salty Test #1 run?

Rust network protocol 2635 and build 168909 on Linux is what Salty Test #1 uses. The protocol must match for you to join, and Steam updates it for you.

Does Salty Test #1 run smoothly?

The last 48 hours saw an average of 95 server fps, with 75 as the lowest. Entities peaked at 91,914, including buildings, deployables and everything else. Up to 8,705 MB of memory was used. Lag, as players feel it, is low fps combined with a climbing entity count.

Is Salty Test #1 online, and how reliable is it?

Salty Test #1 is up and running at the moment. The uptime it reports suggests a restart roughly 13 hours ago. It was up 99% of the time over the last 7 full days, 167 out of 168 hours. On 13 September 2026, Rust Population saw it for the first time.

Where is Salty Test #1 located?

Nothing published by Salty Test #1 states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. Connect at 194.69.160.182:28015.

Getting in

How do I join Salty Test #1?

To connect directly, open Rust's console with F1 and type client.connect 194.69.160.182:28015; or press Launch Rust on this page and Steam opens Rust and joins for you.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp20
Max players You can join up to 20 slots.
ts8
Group limit This is the game default: at most 8 per team.
v2635
Protocol The protocol is 2635; a different version will not connect.
cs168909
Build This server runs game build 168909.
ptrak
Networking RakNet is the network layer here, as standard for the game.
$r?
Region code The region code is left blank.

Mods and access

^z
Modded Plugins or settings change the game; it is listed under Modded.
^y
Carbon The plugin framework Carbon runs on this server.

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.