Salty Test #1
Online 194.69.160.182:28015 checked 9m ago
Server instruments
last reading Fri 00:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 75 · below 20 is lag, below 10 is badEntities
48 h range 69,319–91,914 · memory 5,522 MBUptime
15 h 0 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server 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.
Rank
daily · 1 is bestTop 22% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 29 Oct, 08:44 UTC17h ago | – | – | running | 0 |
| Tue 27 Oct, 00:50 UTC3d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 15/500
- 135/100
- 32/225
- 8/700
- 38/700
- 143/200
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on Salty Test #1?
An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 1 hours. Until the next wipe, the crowd stayed above half that peak in 67% of its recent wipes. It fell below half by day 9 when it didn't.
When does Salty Test #1 wipe?
No next wipe can be predicted for Salty Test #1, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 17 hours ago.
Tags
Which tags does Salty Test #1 carry, and what do they mean?
These are the tags Salty Test #1 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Salty Test #1 appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Salty Test #1: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.
Occupancy
Where does Salty Test #1 sit in the rankings?
Ranking for Salty Test #1: #5,001 on seven-day player hours, top 22% of all ranked servers.
What player count does Salty Test #1 carry?
Current headcount on Salty Test #1: 0 players, 20 slots available. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 10:00 UTC, 1 players on average.
Server details
Which location does Salty Test #1 run from?
No region tag on Salty Test #1. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 194.69.160.182:28015.
What Rust version is Salty Test #1 on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by Salty Test #1. To get in, your game needs the same protocol; Steam applies the update.
How does Salty Test #1 perform?
Over the last 48 hours the average was 95 server fps; the floor was 75. Peak entity count: 91,914. Buildings, deployables and all else included. Reading: 8,705 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
Is Salty Test #1 up, and how often does it stay up?
Reading: online. Salty Test #1 answers right now. Check: restart. The uptime it reports puts the last restart about 15 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Settings and map
What settings and rules apply on Salty Test #1?
Check: gather rate. The name Salty Test #1 does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. Check: anti-cheat. VAC, Valve's system, is on.
What map is Salty Test #1 on?
Check: map. Procedural, size 4,500, seed 1337, generated by the game on Salty Test #1. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Read the map name: Custom Map.
Join
How do you connect to Salty Test #1?
Press F1 in Rust and enter client.connect 194.69.160.182:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.