Rust Data

rustdata.spaceservers194.69.160.182:28017.ipynb

Run all rust-data · live

‹ All servers

Online 194.69.160.182:28015 checked 9m ago

Salty Test #1

moddedcarbon

Connect

srv = rust.server("194.69.160.182:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/20 # 0% full
7-day average 0 # peak 2
rank #5,036 # top 23%
last wipe 2h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75112:0021:0006:0015:0001:0010:00Wiped Thu 29 Oct, 08:44 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
025507510012:0021:0006:0015:0001:0010: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap2.4 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
crowd held67%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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 29 Oct, 08:44 UTC2h ago NaN NaN running 0
1 Tue 27 Oct, 00:50 UTC2d ago 1 held half 2.3 days 0
2 Thu 1 Oct, 17:10 UTC FW27d ago 1 halved by day 9 25.3 days 3
3 Tue 29 Sep, 06:22 UTC30d ago 1 held half 2.5 days 0
4 Mon 28 Sep, 08:22 UTC31d ago 1 NaN 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.

display(srv.map, srv.info())

Map

4500 · seed 1337
Map of Salty Test #1
map
Custom Map
size
4500
seed
1337

Server

srv.info()
address
194.69.160.182:28015
region
–
max players
20
group limit
8, the default
wipe schedule
–
last wipe
29 Oct 2026, 08:44 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
RAIDABLE BASES | ZOMBIES | XP/SKILLS | BOSSES | QUESTS | RAIDING NPCS EVENTS: Armored Train, Convoy, Sputnik, Junkyard Showdown, Gas Station, Contributions FEATURES: Enchants, Custom Weapons, Jet Packs, Summonable Heli & Bradley, Anti-Grub, Custom Maps, Farm Enchants, Skins, Personal Portals, Virtual Quarries, Unbreakable Minis, Kits, Vote Rewards, Virtual Backpack, Personal Recycler, Stacking Chests, Auto-Looting WHY PLAY HERE? • Progress through 15 unique skill paths including mining, raiding, farming, and more, with gather rates scaling from x1 to x5 before tea or pie bonuses. • Raid more than 300 unique NPC bases. • Defend your own base against raiding NPC attacks. • Survive nightly zombie hordes and take on unique bosses. • Complete 100+ quests and take part in story-driven server-wide contributions. • Summon Patrol Helicopters and Bradley APCs right at front of your base. • Explore fresh custom maps every wipe. • Use a 16-enchant system on clothing, weapons, and tools to build your own playstyle. • Access custom weapons like the MLRS Rocket Launcher or an M249 with double magazine size. • Use enchanted farm equipment like plots, beehives, and chicken coops with fixed stats unaffected by the environment. • Enjoy weekly skin updates, a large custom skin collection, and the ability to request skins you want added. • Use the teleport hub system and personal placed portals to travel around the map with ease. • Play with full anti-grub protection across events, monuments and regural PVE activities.

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 149 on average154/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average120/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average186/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average72/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average11/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average23/1000

Quick answers

From the figures on this page.

Player counts

How does Salty Test #1 compare in the rankings?

Over the last seven days Salty Test #1 sits at #5,036 on player hours, in the top 23% of ranked servers.

How full does Salty Test #1 run?

Salty Test #1 reports 0 players at this refresh, with 20 slots configured. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 12:00 UTC, averaging 1 players.

Server facts

What does performance look like on Salty Test #1?

The 48-hour average is 92 server fps, with a low of 20. The entity count peaked at 91,914, covering buildings, deployables and the rest of the world. Memory peaked at 8,705 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is Salty Test #1 on?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Salty Test #1. Joining needs the same protocol on your game; Steam handles the update.

Is Salty Test #1 up, and what does its uptime show?

The current sample puts Salty Test #1 online. Count back 1 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is Salty Test #1 hosted?

For Salty Test #1, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 194.69.160.182:28015.

Settings and map

Which settings and rules does Salty Test #1 run?

The name Salty Test #1 carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.

What is the map on Salty Test #1?

Salty Test #1 runs a procedural map of size 4,500 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.

Wipe schedule

On what schedule does Salty Test #1 wipe?

Salty Test #1 wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 2 hours ago, and that is the one in play.

What is wipe day on Salty Test #1 like?

Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 1 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 67% of the time. In the wipes where it did not hold, half was lost by day 9.

Tags and filters

Which lists on Rust Data hold Salty Test #1, and which filters?

The Rust Data lists that Salty Test #1 fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.

Which meanings do the tags on Salty Test #1 hold?

These tags are published by Salty Test #1 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): 20 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join Salty Test #1?

Enter client.connect 194.69.160.182:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp20
Max players 20 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^z
Modded Plugins or settings alter the game, so it sits under Modded.
^y
Carbon The plugin framework in use 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.

Rust Data 61,573 players 11,733 servers online