Salty Test #1
Online 194.69.160.182:28015 checked 8m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server performance
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.
Li4Rank
daily · 1 is bestTop 23% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 29 Oct, 08:44 UTC34m 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on Salty Test #1?
Its recent wipes drew an average peak of 1 players. The crowd on the latest wipe reached its peak 1 hours in. Above half the peak until the next wipe: that held in 67% of its recent wipes. It fell below half by day 9 when it did not hold.
What is the wipe schedule on Salty Test #1?
Wipes come at irregular times on Salty Test #1, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 34 minutes ago.
Population
How busy is Salty Test #1?
The current population of Salty Test #1 is 0, against 20 slots. The average across the last seven days is 0 players; the peak reached 2. Its busiest point in the last 48 hours was 10:00 UTC, averaging 1 players.
How does Salty Test #1 rank against other Rust servers?
Player hours over seven days put Salty Test #1 at #5,007, in the top 23% of ranked servers.
Map and rules
Which map does Salty Test #1 run?
The map on Salty Test #1 is procedural, size 4,500 with seed 1337, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map. You play on a map named OilPoint.SZ2.
What are the rules and settings on Salty Test #1?
No gather rate appears in the name Salty Test #1. The group limit is 8 players, which is the game's default. survival is the game mode, gather, build and raid in the standard game. You can fight other players and raid their bases. In the server browser it is Modded, meaning plugins or settings modify the game. Carbon plugins run on this server. VAC is on, which is Valve's anti-cheat.
Server details
Which version of Rust does Salty Test #1 run?
Rust network protocol 2635 and build 169621 on Linux is what Salty Test #1 runs. Your game must run the same protocol to join, and Steam takes care of updating it.
Is Salty Test #1 online, and how reliable is it?
The server is up at the moment: Salty Test #1 is online. About 2 days 6 hours ago is when it last restarted, by its own uptime figure. 167 of 168 hours up over the last 7 full days, which is 99%. Rust Heatmap has had it on record since 13 September 2026.
Where is Salty Test #1 located?
Nothing about a region comes from Salty Test #1. Rust Heatmap shows the location a server states. It does not look up the machine's location. To connect, use 194.69.160.182:28015.
Does Salty Test #1 run smoothly?
It averaged 92 server fps over the last 48 hours, with a low of 20. The world held as many as 91,914 entities, buildings and deployables included. At its peak it held 8,705 MB of memory. Lag, as players experience it, comes from low fps and a rising entity count.
Tags
Which Rust Heatmap lists and filters include Salty Test #1?
These Rust Heatmap lists include Salty Test #1: Modded Rust servers, by live population. Filtering the list by Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours brings it up.
What do the server tags on Salty Test #1 mean?
gmrust (Game mode): Rust survival, standard rules; mp20 (Max players): The slot count is 20; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Your game must match protocol 2635 to get in; cs169621 (Build): Build 169621; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code is blank; ^z (Modded): Listed as Modded, since settings or plugins change the game; ^y (Carbon): Carbon provides the plugin framework here are the tags Salty Test #1 publishes, and the server browser reads them. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
How to join
How do I join Salty Test #1?
Press F1 in Rust to open the console, then enter client.connect 194.69.160.182:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.