Rust Data

rustdata.spaceservers160.251.169.135:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 160.251.169.135:28015 checked 11h ago

RustServer_6109

moddedoxide

Connect

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

Right now

srv.summary()
players now 1/50 # 2% full
7-day average 1 # peak 4
rank #3,419 # top 15%
last wipe 12h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.511.5206:0013:0021:0003:0010:0017:00Wiped Thu 29 Oct, 15:37 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
05010015020006:0013:0021:0003:0010:0017:00Wiped Thu 29 Oct, 15:37 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 8 Oct. 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
12.5k5k7.5k10k8 Oct12 Oct17 Oct21 Oct26 Oct30 Oct

Top 15% 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 gap1.8 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sun 11 OctSat 10 OctThu 8 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 29 Oct, 15:37 UTC13h ago NaN NaN running 0
1 Sun 11 Oct, 02:42 UTC19d ago 1 held half 18.5 days 1
2 Sat 10 Oct, 01:23 UTC20d ago 2 NaN 1.1 days 1
3 Thu 8 Oct, 05:27 UTC21d ago 2 NaN 1.8 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

4000 · seed 1337
Map of RustServer_6109
map
Custom Map
size
4000
seed
1337

Server

srv.info()
address
160.251.169.135:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
29 Oct 2026, 16:57 UTC
hostname
–
first seen
8 Oct 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 · 151 on average32/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average124/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 123 on average0/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average9/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average30/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average50/200

Quick answers

From the figures on this page.

Population

How does RustServer_6109 compare in the rankings?

Player hours over seven days put RustServer_6109 at #3,419, in the top 15% of the ranked set.

What population does RustServer_6109 carry?

RustServer_6109 returns no live count at this refresh, having last been seen 11 hours ago. Over the last seven days it averaged 1 players and peaked at 4. Peak hour in the last 48 hours: 10:00 UTC, mean 2 players.

Server data

How smoothly does RustServer_6109 run?

The 48-hour average is 45 server fps, with a low of 32. Entity numbers reached 126,282, and that includes buildings, deployables and the rest. Memory peaked at 3,940 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does RustServer_6109 run?

Rust network protocol 2635 and build 168909 on Linux is what RustServer_6109 runs. Steam updates your game for you, but the protocol must match to join.

How reliable is RustServer_6109, and is it online now?

RustServer_6109 is offline at this refresh; the last response came 11 hours ago. Count back 6 minutes from its reported uptime to get the last restart. Over the last 7 full days the hours up number 161 of 168, 96%. Its earliest recorded date in Rust Data is 8 October 2026.

In which location is RustServer_6109 hosted?

No region is published by RustServer_6109. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 160.251.169.135:28015.

Settings and map

What rules and settings are recorded for RustServer_6109?

No gather rate appears in the name: RustServer_6109. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. 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_6109 loaded?

RustServer_6109 runs a procedural map of size 4,000 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.

Wipes and dates

When does RustServer_6109 wipe, and on what schedule?

No next wipe can be predicted for RustServer_6109, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 12 hours ago.

What is wipe day on RustServer_6109 like?

Recent wipes averaged 2 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.

Lists and tags

Where does RustServer_6109 appear among Rust Data lists and filters?

On Rust Data, RustServer_6109 appears in these lists: 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 24 hours.

Which meanings do the tags on RustServer_6109 hold?

These tags are published by RustServer_6109 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 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): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

How can I connect to RustServer_6109?

Enter client.connect 160.251.169.135: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 Survival play, standard Rust.
mp50
Max players 50 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 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 Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 39,956 players 11,624 servers online