Rust Data

rustdata.spaceservers194.93.2.154:35102.ipynb

Run all rust-data · live

‹ All servers

Online 194.93.2.154:35100 checked 10m ago

ShockRust | Blue | NoLimit

moddedoxide

Connect

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

Right now

srv.summary()
players now 100/500 # 20% full
7-day average 164 # peak 352
rank #129 # top 0.6%
last wipe 4d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
010020030040023:0008:0017:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040023:0008:0017: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 23 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
15k10k15k20k22 Oct23 Oct24 Oct25 Oct26 Oct27 Oct

Top 0.6% 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 peak352players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 12:55 UTC4d ago 352 NaN running 96

# 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 1636364137
No map picture published
map
Procedural Map
size
4250
seed
1636364137
Open on RustMaps

Server

srv.info()
address
194.93.2.154:35100
region
–
max players
500
group limit
not published
wipe schedule
–
last wipe
23 Oct 2026, 12:55 UTC
hostname
–
first seen
22 Oct 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
0МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average131/100
1RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average110/225
2RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average29/200
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average96/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average34/1000
5[Whitelist]KagiRust8groups of 20+ · 81 on average18/300

Quick answers

From the figures on this page.

Player counts

How does ShockRust | Blue | NoLimit compare in the rankings?

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

How full does ShockRust | Blue | NoLimit run?

ShockRust | Blue | NoLimit reports 100 players at this refresh, with 500 slots configured. Over the last seven days it averaged 164 players and peaked at 352. Averaged by hour over 48 hours, 13:00 UTC is the busiest, at 265 players.

Server facts

How well does ShockRust | Blue | NoLimit perform?

Averaged over 48 hours: 189 server fps, never under 110. Entity numbers reached 310,729, and that includes buildings, deployables and the rest. A high of 7,265 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is ShockRust | Blue | NoLimit on?

The build is Rust network protocol 2556 and build 104046 on Linux, run by ShockRust | Blue | NoLimit. Joining needs the same protocol on your game; Steam handles the update.

How reliable is ShockRust | Blue | NoLimit, and is it up?

ShockRust | Blue | NoLimit reports itself online at the current refresh. The uptime it reports puts the last restart about 19 hours ago. 96 of 96 hours up over the last 4 full days, or 100%. Its earliest recorded date in Rust Data is 22 October 2026.

In which location is ShockRust | Blue | NoLimit hosted?

For ShockRust | Blue | NoLimit, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 194.93.2.154:35100 is its address.

Map and rules

Which rules apply on ShockRust | Blue | NoLimit, and what settings?

The name ShockRust | Blue | NoLimit carries no gather rate. Group limits do not appear in its data. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC on.

Which map has ShockRust | Blue | NoLimit selected?

Size 4,250, seed 1636364137: the procedural map on ShockRust | Blue | NoLimit, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

When does ShockRust | Blue | NoLimit wipe, and on what schedule?

A rhythm cannot be read from the wipes of ShockRust | Blue | NoLimit on record, which are too few. 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 4 days 9 hours ago.

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

The average peak over recent wipes is 352 players. The crowd on the latest wipe topped out 3 hours after it began.

Tags, lists

Which Rust Data filters and lists contain ShockRust | Blue | NoLimit?

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

How should you read the server tags on ShockRust | Blue | NoLimit?

Read by the game's server browser, the tags ShockRust | Blue | NoLimit publishes are: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): Slot count: 500; v2556 (Protocol): To join, your game must run protocol 2556; 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): 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.

Join steps

What is the way to join ShockRust | Blue | NoLimit?

In Rust, F1 opens the console: type client.connect 194.93.2.154:35100. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp500,ptrak,$r?,v2556,gmrust,cs104046,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp500
Max players Slot count: 500.
v2556
Protocol To join, your game must run protocol 2556.
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 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 69,659 players 11,803 servers online