Rust Data

rustdata.spaceservers23.127.52.120:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 23.127.52.120:28015 checked 1d ago

s3s Plugin Server

moddedoxide

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak 1
rank #11,379 # top 51%
last wipe 27d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75122:0002:0003:00Wiped Tue 27 Oct, 22:05 UTCWIPE

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. 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 Sep6 Oct13 Oct21 Oct29 Oct

Top 51% 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 gap0.5 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 1 OctMon 28 SepMon 28 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 22:05 UTC1d ago NaN NaN running 0
1 Thu 1 Oct, 22:59 UTC FW27d ago 0 NaN 26 days 1
2 Mon 28 Sep, 12:27 UTC31d ago 1 NaN 3.4 days 0
3 Mon 28 Sep, 00:38 UTC31d ago 1 NaN 0.5 days 1
4 Sun 27 Sep, 15:24 UTC31d ago 1 NaN 0.4 days 0
5 Sun 27 Sep, 06:02 UTC32d ago 1 NaN 0.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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
23.127.52.120:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 22:59 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 · 149 on average168/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average122/100
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average80/700
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average17/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average22/1000
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 83 on average259/700

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does s3s Plugin Server rank?

Rank #11,379 on seven-day player hours for s3s Plugin Server, within the top 51% of all ranked servers.

What population does s3s Plugin Server carry?

Offline now for s3s Plugin Server, with the last sample 33 hours ago. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 03:00 UTC, averaging 1 players.

Server data

Which Rust version is s3s Plugin Server on?

The build is Rust network protocol 2635 and build 168909 on Windows, run by s3s Plugin Server. Joining needs the same protocol on your game; Steam handles the update.

How reliable is s3s Plugin Server, and is it up?

s3s Plugin Server is offline at this refresh; the last response came 33 hours ago. 5 of 168 hours up over the last 7 full days, or 3%. Rust Data logged it first on 13 September 2026.

In which location is s3s Plugin Server hosted?

No region is published by s3s Plugin Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 23.127.52.120:28015 is its address.

Rules, settings, map

What rules and settings are recorded for s3s Plugin Server?

No gather rate appears in the name: s3s Plugin Server. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has s3s Plugin Server loaded?

s3s Plugin Server runs a procedural map, which the game generates.

Wipe data

On what schedule does s3s Plugin Server wipe?

s3s Plugin Server wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 27 days 13 hours ago.

On s3s Plugin Server, what happens on wipe day?

The average peak over recent wipes is 1 players. 1 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Which Rust Data filters and lists contain s3s Plugin Server?

The Rust Data lists that s3s Plugin Server fits are: 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.

How should you read the server tags on s3s Plugin Server?

Read by the game's server browser, the tags s3s Plugin Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; 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): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way to join s3s Plugin Server?

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

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players 10 slots in total.
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 Runs on Oxide (uMod) for plugins.
^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 67,749 players 11,777 servers online