Rust Data

rustdata.spaceservers160.251.169.111:28017.ipynb

Run all rust-data · live

‹ All servers

Online 160.251.169.111:28015 checked 7m ago

RustServer_25919

moddedoxide

Connect

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

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 1 # peak 4
rank #3,659 # top 16%
last wipe 10d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123400:0009:0019:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020000:0009:0019:0003:0012:0021:00

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 19 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 16% 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 gap11.7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak3players, last three wipes
crowd held50%else halves by day 1

The first 48 hours of its last wipes

Mon 19 OctThu 8 OctSat 26 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 1 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 19 Oct, 14:18 UTC10d ago 3 NaN running 2
1 Thu 8 Oct, 14:50 UTC21d ago 3 held half 11 days 0
2 Sat 26 Sep, 03:42 UTC33d ago 2 halved by day 1 12.5 days 1

# 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

3000 · seed 15754
Map of RustServer_25919
map
Procedural Map
size
3000
seed
15754
Open on RustMaps

Server

srv.info()
address
160.251.169.111:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
19 Oct 2026, 14:18 UTC
hostname
–
first seen
19 Sep 2026

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 average35/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average130/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 120 on average63/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average20/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 93 on average60/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average256/310

Quick answers

From the figures on this page.

Population data

What position does RustServer_25919 take in the server rankings?

Over the last seven days RustServer_25919 sits at #3,659 on player hours, in the top 16% of ranked servers.

How full does RustServer_25919 run?

Current row: 0 players on RustServer_25919, against 50 slots. Over the last seven days it averaged 1 players and peaked at 4. The 48-hour sample puts the busiest hour at 14:00 UTC, averaging 2 players.

About the server

How smoothly does RustServer_25919 run?

Server fps over the last 48 hours averages 167; the floor is 129. The entity count peaked at 47,353, covering buildings, deployables and the rest of the world. The memory field tops out at 3,241 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is RustServer_25919 on?

Rust network protocol 2635 and build 168909 on Linux is what RustServer_25919 runs. The protocol has to match before you can join, and Steam does the updating.

Is RustServer_25919 up, and what does its uptime show?

The current sample puts RustServer_25919 online. A restart about 4 days 22 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 19 September 2026.

Where does RustServer_25919 sit?

No region is published by RustServer_25919. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 160.251.169.111:28015.

Rules, settings, map

Which settings and rules does RustServer_25919 run?

The name RustServer_25919 carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has RustServer_25919 selected?

Size 3,000, seed 15754: the procedural map on RustServer_25919, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

When does RustServer_25919 wipe, and on what schedule?

No next wipe can be predicted for RustServer_25919, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 10 days 8 hours ago.

On RustServer_25919, what happens on wipe day?

Recent wipes averaged 3 players at their peak. The crowd on the latest wipe topped out 1 hours after it began. Half the peak or more was held to the next wipe in 50% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags, lists

Which lists on Rust Data hold RustServer_25919, and which filters?

The Rust Data lists that RustServer_25919 fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on RustServer_25919?

The game's server browser reads these tags from RustServer_25919: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way to join RustServer_25919?

Enter client.connect 160.251.169.111: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 mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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 71,129 players 11,757 servers online