Rust Data

rustdata.spaceservers46.174.48.131:28016.ipynb

Run all rust-data · live

‹ All servers

Online 46.174.48.131:28015 checked 6m ago

ZONE_51

moddedoxide

Connect

srv = rust.server("46.174.48.131:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak 1
rank #9,021 # top 41%
last wipe 3d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123406:0015:0000:0010:0019:0004:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020006:0015:0000:0010:0019:0004: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 10 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
15k10k15k20k10 Oct14 Oct17 Oct21 Oct24 Oct28 Oct

Top 41% 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 gap7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 2

The first 48 hours of its last wipes

Sat 24 OctTue 13 OctSat 10 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 Sat 24 Oct, 13:22 UTC3d ago 1 NaN running 0
1 Tue 13 Oct, 20:28 UTC14d ago 1 halved by day 2 10.7 days 0
2 Sat 10 Oct, 12:00 UTC17d ago 1 held half 3.4 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 ZONE_51
map
Procedural Map
size
4000
seed
1337
Open on RustMaps

Server

srv.info()
address
46.174.48.131:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
24 Oct 2026, 14:03 UTC
hostname
–
first seen
10 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 · 158 on average60/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average121/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average57/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average29/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average4/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average9/1000

Quick answers

From the figures on this page.

Player counts

What position does ZONE_51 take in the server rankings?

Player hours over seven days put ZONE_51 at #9,021, in the top 41% of the ranked set.

How many players does ZONE_51 hold at once?

The sample now reads 0 players for ZONE_51, out of 100 slots. Over the last seven days it averaged 0 players and peaked at 1.

Server facts

How smoothly does ZONE_51 run?

Averaged over 48 hours: 99 server fps, never under 60. The entity count peaked at 91,299, covering buildings, deployables and the rest of the world. Memory peaked at 3,522 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does ZONE_51 run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by ZONE_51. The protocol has to match before you can join, and Steam does the updating.

Is ZONE_51 up, and what does its uptime show?

Online is the state at the latest refresh for ZONE_51. The uptime it reports puts the last restart about 3 days 13 hours ago. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 10 October 2026.

Which location does ZONE_51 run from?

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

Rules, settings, map

Which rules apply on ZONE_51, and what settings?

The name ZONE_51 carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

What is the map on ZONE_51?

The game generates the map on ZONE_51: procedural, size 4,000, seed 1337. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

When does ZONE_51 wipe, and on what schedule?

Irregular wipe times on ZONE_51 leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 3 days 15 hours ago, and that is the one in play.

On ZONE_51, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. Otherwise the crowd fell below half by day 2.

Tags and filters

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

On Rust Data, ZONE_51 appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

How should you read the server tags on ZONE_51?

Read by the game's server browser, the tags ZONE_51 publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.

Join steps

How can I connect to ZONE_51?

The manual route: launch Rust, F1, then client.connect 46.174.48.131:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://m.vk.ru/ is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players The server lists 100 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework: 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 33,161 players 11,582 servers online