Rust Data

rustdata.spaceservers136.158.40.123:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 136.158.40.123:28015 checked 9h ago

Rust Solo (Local)

moddedoxide

Connect

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

Right now

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

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75112:0015:0019:0022:0014:0017:00Wiped Mon 26 Oct, 22:12 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
15k10k15k20k28 Sep3 Oct14 Oct18 Oct23 Oct28 Oct

Top 24% 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 rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 13 OctTue 13 OctMon 12 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 Mon 26 Oct, 22:12 UTC1d ago NaN NaN running 1
1 Tue 13 Oct, 12:45 UTC14d ago 1 held half 13.4 days 1
2 Tue 13 Oct, 04:57 UTC14d ago 1 NaN 0.3 days 0
3 Mon 12 Oct, 17:40 UTC15d ago 1 NaN 0.5 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
136.158.40.123:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
26 Oct 2026, 22:12 UTC
hostname
–
first seen
28 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 · 160 on average39/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average124/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average48/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average19/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average7/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average5/1000

Quick answers

From the figures on this page.

Population

What position does Rust Solo (Local) take in the server rankings?

Rank #5,233 on seven-day player hours for Rust Solo (Local), within the top 24% of all ranked servers.

What population does Rust Solo (Local) carry?

Rust Solo (Local) returns no live count at this refresh, having last been seen 9 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 13:00 UTC, averaging 1 players.

Server data

Which Rust version is Rust Solo (Local) on?

Version Rust network protocol 2635 and build 168909 on Windows is reported by Rust Solo (Local). The protocol has to match before you can join, and Steam does the updating.

How reliable is Rust Solo (Local), and is it up?

Rust Solo (Local) is offline at this refresh; the last response came 9 hours ago. Uptime of 26% across the last 7 full days: 43 hours of 168. The first row Rust Data holds for it is dated 28 September 2026.

Which location does Rust Solo (Local) run from?

No region is published by Rust Solo (Local). Rust Data does not look up where the machine stands; it shows where a server says it is. 136.158.40.123:28015 is its address.

Rules, settings, map

Which rules apply on Rust Solo (Local), and what settings?

You will not find a gather rate in the string Rust Solo (Local). No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. The VAC field reads off.

What is the map on Rust Solo (Local)?

Rust Solo (Local) runs a procedural map, which the game generates.

Wipes and dates

On what schedule does Rust Solo (Local) wipe?

No next wipe can be predicted for Rust Solo (Local), which wipes at irregular times. 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 28 hours ago, and that is the one in play.

On Rust Solo (Local), what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

Lists and tags

Which lists on Rust Data hold Rust Solo (Local), and which filters?

On Rust Data, Rust Solo (Local) appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

How should you read the server tags on Rust Solo (Local)?

Read by the game's server browser, the tags Rust Solo (Local) publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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 Rust Solo (Local)?

Enter client.connect 136.158.40.123: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 Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is 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 39,332 players 11,647 servers online