Rust Data

rustdata.spaceservers185.158.112.236:10001.ipynb

Run all rust-data · live

‹ All servers

Online 185.158.112.236:10000 checked 11m ago

RolePlayRust #1

moddedoxide

Connect

srv = rust.server("185.158.112.236:10001")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
02.557.51012:0021:0006:0016:0001:0010:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020012:0021:0006:0016:0001:0010: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
11k2k3k4k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 7% 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.4 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak20players, last three wipes
crowd held0%else halves by day 9

The first 48 hours of its last wipes

Fri 16 OctThu 1 OctThu 17 Sep
010203040+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 14:26 UTC11d ago 18 NaN running 3
1 Thu 1 Oct, 19:31 UTC FW26d ago 24+1 queue halved by day 6 14.8 days 1
2 Thu 17 Sep, 19:05 UTC40d ago 17+1 queue halved by day 12 14 days 7

# 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

4500 · seed 2147483647
Map of RolePlayRust #1
map
Procedural Map
size
4500
seed
2147483647
Open on RustMaps

Server

srv.info()
address
185.158.112.236:10000
region
–
max players
10
group limit
20 max
wipe schedule
–
last wipe
16 Oct 2026, 14:26 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 · 155 on average172/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average133/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average179/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average126/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average15/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average54/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does RolePlayRust #1 rank?

Rank #1,642 on seven-day player hours for RolePlayRust #1, within the top 7% of all ranked servers.

What population does RolePlayRust #1 carry?

RolePlayRust #1 reports 2 players at this refresh, with 10 slots configured. Over the last seven days it averaged 4 players and peaked at 11. Averaged by hour over 48 hours, 16:00 UTC is the busiest, at 7 players.

Server facts

How well does RolePlayRust #1 perform?

The 48-hour average is 79 server fps, with a low of 3. The entity count peaked at 147,060, covering buildings, deployables and the rest of the world. The memory field tops out at 4,203 MB. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on RolePlayRust #1?

Rust network protocol 2635 and build 168909 on Windows is what RolePlayRust #1 runs. The protocol has to match before you can join, and Steam does the updating.

Is RolePlayRust #1 up, and what does its uptime show?

The current sample puts RolePlayRust #1 online. Count back 11 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 168 of 168, 100%. The first row Rust Data holds for it is dated 13 September 2026.

Which location does RolePlayRust #1 run from?

There is no region published for RolePlayRust #1. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 185.158.112.236:10000.

Map and rules

Which rules apply on RolePlayRust #1, and what settings?

No gather rate appears in the name: RolePlayRust #1. 20 players is the maximum per group. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has RolePlayRust #1 selected?

RolePlayRust #1 runs a procedural map of size 4,500 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 RolePlayRust #1 wipe, and on what schedule?

RolePlayRust #1 wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 11 days 21 hours ago, and that is the one in play.

On RolePlayRust #1, what happens on wipe day?

Recent wipes averaged 20 players at their peak. 3 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 9 in the other cases.

Lists and tags

Which lists on Rust Data hold RolePlayRust #1, and which filters?

These Rust Data lists include RolePlayRust #1: Modded Rust servers and Rust roleplay 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 2 weeks.

How should you read the server tags on RolePlayRust #1?

The game's server browser reads these tags from RolePlayRust #1: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts20 (Group limit): No team may exceed 20; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; 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): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

How can I connect to RolePlayRust #1?

The manual route: launch Rust, F1, then client.connect 185.158.112.236:10000. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://rprust.gamestores.app/ is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts20,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players 10 slots in total.
ts20
Group limit No team may exceed 20.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 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 Plugin framework: 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 64,778 players 11,681 servers online