Rust Data

rustdata.spaceservers5.83.170.184:12401.ipynb

Run all rust-data · live

‹ All servers

Online 5.83.170.184:12400 checked 7m ago

Shadow_3MK

Connect

srv = rust.server("5.83.170.184:12401")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,348 # top 69%
last wipe 15d ago # no schedule published
next wipe – # no rhythm it keeps
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123422:0007:0016:0000:0009:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02.557.51022:0007:0016:0000:0009:0019: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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% 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 gap14.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Tue 13 OctThu 1 OctSun 13 Sep
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 13 Oct, 15:10 UTC15d ago 3 NaN running 0
1 Thu 1 Oct, 17:50 UTC FW27d ago 0 NaN 11.9 days 0
2 Sun 13 Sep, 20:10 UTC45d ago 1 halved by day 1 17.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

2000 · seed 56789000
Map of Shadow_3MK
map
Procedural Map
size
2000
seed
56789000
Open on RustMaps

Server

srv.info()
address
5.83.170.184:12400
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
13 Oct 2026, 15:10 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
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 553 on average573/675
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average364/525
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 297 on average42/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 296 on average44/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 272 on average119/200
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average136/300

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Shadow_3MK rank?

Rank #15,348 on seven-day player hours for Shadow_3MK, within the top 69% of all ranked servers.

What population does Shadow_3MK carry?

Shadow_3MK reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players.

About the server

How well does Shadow_3MK perform?

Server fps over the last 48 hours averages 10; the floor is 10. Buildings, deployables and all else in the world took the count as high as 16,284 entities. Memory peaked at 1,447 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on Shadow_3MK?

Rust network protocol 2635 and build 168909 on Windows is what Shadow_3MK runs. Joining needs the same protocol on your game; Steam handles the update.

Is Shadow_3MK up, and what does its uptime show?

The current sample puts Shadow_3MK online. Count back 5 days 21 hours from its reported uptime to get the last restart. 168 of 168 hours up over the last 7 full days, or 100%. The first row Rust Data holds for it is dated 13 September 2026.

Where does Shadow_3MK sit?

No region is published by Shadow_3MK. 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 5.83.170.184:12400.

Rules, settings, map

Which rules apply on Shadow_3MK, and what settings?

No gather rate appears in the name: Shadow_3MK. 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. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has Shadow_3MK selected?

The game generates the map on Shadow_3MK: procedural, size 2,000, seed 56789000. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe schedule

When does Shadow_3MK wipe, and on what schedule?

No next wipe can be predicted for Shadow_3MK, which wipes at irregular times. 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 15 days 5 hours ago.

What is wipe day on Shadow_3MK like?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.

Tags and filters

Which Rust Data filters and lists contain Shadow_3MK?

On Rust Data, Shadow_3MK appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on Shadow_3MK?

The game's server browser reads these tags from Shadow_3MK: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set. 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 Shadow_3MK?

The manual route: launch Rust, F1, then client.connect 5.83.170.184:12400. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players The server lists 50 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

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 75,437 players 11,810 servers online