Rust Data

rustdata.spaceservers185.207.214.212:35102.ipynb

Run all rust-data · live

‹ All servers

Offline 185.207.214.212:35100 checked 6d ago

ShockRust | Blue | NoLimit

moddedoxide

Connect

srv = rust.server("185.207.214.212:35102")
print(srv.connect_command)

Right now

srv.summary()
players now 12/400 # 3% full
7-day average 30 # peak 90
rank #3,239 # top 15%
last wipe 13d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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
12505007501k20 Sep28 Sep6 Oct13 Oct21 Oct29 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 gap13.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak375players, last three wipes
crowd held0%else halves by day 9

The first 48 hours of its last wipes

Fri 16 OctFri 9 OctFri 18 Sep
0100200300400+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 377, 2 hours in, with 23 in the queue.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 12:54 UTC13d ago 377+23 queue NaN running 97
1 Fri 9 Oct, 12:51 UTC20d ago 376+29 queue halved by day 6 7 days 91
2 Fri 18 Sep, 15:52 UTC41d ago 373+29 queue halved by day 12 20.9 days 102

# 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

4250 · seed 2147483647
No map picture published
map
Procedural Map
size
4250
seed
2147483647
Open on RustMaps

Server

srv.info()
address
185.207.214.212:35100
region
–
max players
400
group limit
not published
wipe schedule
–
last wipe
16 Oct 2026, 12:54 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
Уникальный модифицированный сервер Rust с расширенными возможностями, эксклюзивными событиями и дружелюбным комьюнити.

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 average106/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average135/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average163/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 95 on average67/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 90 on average206/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average345/350

Quick answers

From the figures on this page.

Population data

What position does ShockRust | Blue | NoLimit take in the server rankings?

Rank #3,239 on seven-day player hours for ShockRust | Blue | NoLimit, within the top 15% of all ranked servers.

How full does ShockRust | Blue | NoLimit run?

ShockRust | Blue | NoLimit returns no live count at this refresh, having last been seen 6 days 19 hours ago. Over the last seven days it averaged 30 players and peaked at 90.

Server facts

Which Rust version is ShockRust | Blue | NoLimit on?

Rust network protocol 2556 and build 104046 on Linux is what ShockRust | Blue | NoLimit runs. The protocol has to match before you can join, and Steam does the updating.

Is ShockRust | Blue | NoLimit up, and what does its uptime show?

Offline now for ShockRust | Blue | NoLimit, last seen 6 days 19 hours ago. Uptime of 14% across the last 7 full days: 24 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

In which location is ShockRust | Blue | NoLimit hosted?

No region is published by ShockRust | Blue | NoLimit. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 185.207.214.212:35100 is its address.

Rules, settings, map

Which settings and rules does ShockRust | Blue | NoLimit run?

No gather rate appears in the name: ShockRust | Blue | NoLimit. The field for group size is empty. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has ShockRust | Blue | NoLimit selected?

ShockRust | Blue | NoLimit runs a procedural map of size 4,250 with seed 2147483647, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does ShockRust | Blue | NoLimit wipe, and how often?

Irregular wipe times on ShockRust | Blue | NoLimit leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 13 days 6 hours ago.

What is wipe day on ShockRust | Blue | NoLimit like?

Recent wipes averaged 375 players at their peak. On the latest wipe the peak came 2 hours after the wipe, with a queue of 23. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 9.

Tags, lists

Where does ShockRust | Blue | NoLimit appear among Rust Data lists and filters?

On Rust Data, ShockRust | Blue | NoLimit 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; Last wipe: In the last 2 weeks; Players now: At least 10; Average players: 25+ on average.

Which meanings do the tags on ShockRust | Blue | NoLimit hold?

These tags are published by ShockRust | Blue | NoLimit and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp400 (Max players): 400 slots in total; v2556 (Protocol): Protocol 2556 is required; a different game version cannot connect; cs104046 (Build): The server runs build 104046; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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 ShockRust | Blue | NoLimit?

Enter client.connect 185.207.214.212:35100 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 mp400,ptrak,$r?,v2556,gmrust,cs104046,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp400
Max players 400 slots in total.
v2556
Protocol Protocol 2556 is required; a different game version cannot connect.
cs104046
Build The server runs build 104046.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is 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 104,335 players 11,883 servers online