This server publishes no banner
Exhibit no. 5,065Acc. 2026.5065
Salty Test #1
Rust server · in the archive since 13 September 2026
Online 194.69.160.182:28015 checked 9m ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
13 Sep Now 28 Sep08:22 29 Sep06:22 1 Oct17:10 · FW 27 Oct00:50 29 Oct08:44
a wipe on recordthe monthly force wipeexpectednow, 29 Oct 2026, 17:45 UTCAll times UTC.
The record of each wipe
-
Thu 29 Oct 202608:44 UTC9h ago
- Peak
- –
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Tue 27 Oct 202600:50 UTC2d ago
- Peak
- 1
- Crowd
- held half
- Lasted
- 2.3 days
- Players before
- 0
-
Thu 1 Oct 202617:10 UTC FW28d ago
- Peak
- 1
- Crowd
- halved by day 9
- Lasted
- 25.3 days
- Players before
- 3
-
Tue 29 Sep 202606:22 UTC30d ago
- Peak
- 1
- Crowd
- held half
- Lasted
- 2.5 days
- Players before
- 0
-
Mon 28 Sep 202608:22 UTC31d ago
- Peak
- 1
- Crowd
- –
- Lasted
- 0.9 days
- Players before
- 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.
The rhythm
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.
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.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
Players
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
Top 23% of all ranked servers. Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Lists and tags
What do the server tags on Salty Test #1 mean?
The game's server browser reads these tags published by Salty Test #1: gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): To join, your game has to be on protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): No region code is set; ^z (Modded): Under Modded: the game is changed by plugins or settings; ^y (Carbon): Plugins run through Carbon here. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.
Which Rust Server History lists and filters include Salty Test #1?
These Rust Server History lists include Salty Test #1: Modded Rust servers: the record. It appears under these filters 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.
The record
Does Salty Test #1 run smoothly?
Across the last 48 hours it averaged 93 server fps; the low was 20. Buildings, deployables and everything else in the world came to as many as 91,914 entities. Up to 8,705 MB of memory was used. What players feel as lag comes from low fps and a climbing entity count.
Which version of Rust does Salty Test #1 run?
The recorded build for Salty Test #1 is Rust network protocol 2635 and build 168909 on Linux. Steam updates your game for you; joining needs the same protocol.
Is Salty Test #1 online, and how reliable is it?
The live count shows Salty Test #1 online right now. The uptime it reports puts the last restart at about 7 hours ago. 167 of 168 hours, or 99% of the time, over the last 7 full days. The first sighting by Rust Server History was on 13 September 2026.
Where is Salty Test #1 located?
There is no region published by Salty Test #1. Rust Server History does not look up where the machine stands; it shows where a server says it is. You will find it at 194.69.160.182:28015.
Wipe history
What does wipe day look like on Salty Test #1?
An average peak of 1 players was drawn by its recent wipes. On the latest wipe, 1 hours after the wipe, the crowd peaked. Above half that peak until the next wipe it stayed in 67% of its recent wipes. The fall below half came by day 9 in those wipes where it didn't hold.
What is the wipe schedule on Salty Test #1?
There is no next wipe to predict on Salty Test #1, which wipes at irregular times. The monthly force wipe comes next on Thursday 5 November at 19:00 UTC, and every Rust server wipes then. 9 hours ago its current world was made.
Player record
How does Salty Test #1 rank against other Rust servers?
Player hours over the last seven days put Salty Test #1 at #5,065: a place in the top 23% of all ranked servers.
How busy is Salty Test #1?
Of its 20 slots, Salty Test #1 currently has 1 filled. The seven-day average stands at 0 players; the peak is 1. An average of 1 players at 10:00 UTC made that the busiest hour of the last 48.
Map and rules
What are the rules and settings on Salty Test #1?
The name of Salty Test #1 carries no gather rate. At 8 players, the group limit matches the game's default. Recorded as survival, with this note: gathering, building and raiding: the standard game. PvP and raiding are enabled. The server browser lists it under Modded, where plugins or settings change the game. Carbon plugins are running. The anti-cheat VAC from Valve is active.
Which map does Salty Test #1 run?
A procedural map of size 4,500 with seed 1337 is what Salty Test #1 runs, generated by the game. From this page you can view the map on RustMaps: the same size and seed give the same map. Under map name, the entry reads: Custom Map.
How to join
How do I join Salty Test #1?
Enter client.connect 194.69.160.182:28015 in the console, opened with F1 in Rust. Launch Rust and join on this page also works: it opens Rust through Steam and connects you.
The label explained
Server tags
What each tag this server publishes means.
Published as mp20,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
mp20
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^z
^y
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.