Rust Data

rustdata.spaceservers160.251.205.126:28017.ipynb

Run all rust-data · live

‹ All servers

Online 160.251.205.126:28015 checked 8m ago

316Rust_Server

moddedoxide

Connect

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

Right now

srv.summary()
players now 0/30 # 0% full
7-day average 0 # peak 2
rank #5,432 # top 24%
last wipe 27d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5222:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020022:0007:0016:0002:0011:0020: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 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 24% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak5players, last three wipes

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 12 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 15:05 UTC27d ago 5 NaN running 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 1997891973
Map of 316Rust_Server
map
Procedural Map
size
4000
seed
1997891973
Open on RustMaps

Server

srv.info()
address
160.251.205.126:28015
region
–
max players
30
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 15:05 UTC
hostname
–
first seen
13 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 · 150 on average62/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average121/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 119 on average112/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average36/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 92 on average119/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average347/350

Quick answers

From the figures on this page.

Player counts

How does 316Rust_Server compare in the rankings?

Player hours over seven days put 316Rust_Server at #5,432, in the top 24% of the ranked set.

How many players does 316Rust_Server hold at once?

Current row: 0 players on 316Rust_Server, against 30 slots. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 05:00 UTC is the busiest, at 2 players.

About the server

How smoothly does 316Rust_Server run?

Averaged over 48 hours: 114 server fps, never under 90. The entity count peaked at 97,763, covering buildings, deployables and the rest of the world. The memory field tops out at 4,952 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does 316Rust_Server run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by 316Rust_Server. Steam updates your game for you, but the protocol must match to join.

Is 316Rust_Server up, and what does its uptime show?

The current sample puts 316Rust_Server online. Count back 5 days 17 hours from its reported uptime to get the last restart. 156 of 168 hours up over the last 7 full days, or 93%. Rust Data logged it first on 13 September 2026.

Where does 316Rust_Server sit?

No region is published by 316Rust_Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 160.251.205.126:28015 is its address.

Rules, settings, map

Which rules apply on 316Rust_Server, and what settings?

The name 316Rust_Server carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

What is the map on 316Rust_Server?

Size 4,000, seed 1997891973: the procedural map on 316Rust_Server, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does 316Rust_Server wipe, and on what schedule?

The record for 316Rust_Server holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 6 hours ago.

On 316Rust_Server, what happens on wipe day?

Recent wipes averaged 5 players at their peak. 12 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which Rust Data filters and lists contain 316Rust_Server?

The Rust Data lists that 316Rust_Server fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meanings do the tags on 316Rust_Server hold?

The game's server browser reads these tags from 316Rust_Server: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): 30 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way to join 316Rust_Server?

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

Game

gmrust
Game mode Rust survival in its standard form.
mp30
Max players 30 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 90,952 players 11,834 servers online