Rust Data

rustdata.spaceservers131.153.205.250:7049.ipynb

Run all rust-data · live

‹ All servers

Online 131.153.205.250:7048 checked 9m ago

[SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(

moddedoxide

Connect

srv = rust.server("131.153.205.250:7049")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123401:0010:0019:0004:0013:0023:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020001:0010:0019:0004:0013:0023: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
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 42% 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.5 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 3

The first 48 hours of its last wipes

Wed 21 OctThu 8 OctThu 1 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, 13 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 21 Oct, 23:54 UTC7d ago 1 NaN running 0
1 Thu 8 Oct, 12:50 UTC20d ago 1 halved by day 1 13.5 days 0
2 Thu 1 Oct, 23:52 UTC FW27d ago 1 halved by day 3 6.5 days 0
3 Mon 14 Sep, 13:04 UTC44d ago 2 halved by day 3 17.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

3650 · seed 7
Map of [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(
map
Procedural Map
size
3650
seed
7
Open on RustMaps

Server

srv.info()
address
131.153.205.250:7048
region
–
max players
69
group limit
8, the default
wipe schedule
–
last wipe
21 Oct 2026, 23:54 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
0QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 24 on average29/100
1【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐EA · groups of 8+ · weekly · 19 on average23/200
2[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 17 on average4/100
3#10-[搞就完了]10倍/10.29新档/无权/萌新首选EA · no group limit · 11 on average18/100
4[JP] DON-tacos PvEEA · groups of 8+ · monthly · 11 on average5/100
5[守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新EA · no group limit · 11 on average19/100

Quick answers

From the figures on this page.

Player counts

What position does [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( take in the server rankings?

Over the last seven days [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( sits at #9,308 on player hours, in the top 42% of ranked servers.

How many players does [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( hold at once?

Current row: 0 players on [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(, against 69 slots. Over the last seven days it averaged 0 players and peaked at 1.

About the server

How smoothly does [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( run?

Averaged over 48 hours: 111 server fps, never under 71. The entity count peaked at 79,819, covering buildings, deployables and the rest of the world. A high of 3,002 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(?

Version Rust network protocol 2635 and build 168909 on Linux is reported by [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(. Joining needs the same protocol on your game; Steam handles the update.

How reliable is [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(, and is it up?

Online is the state at the latest refresh for [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(. Count back 47 hours from its reported uptime to get the last restart. Uptime of 86% across the last 7 full days: 144 hours of 168. Rust Data logged it first on 13 September 2026.

Where does [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( sit?

No region tag is published by [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(, though its name points to Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 131.153.205.250:7048.

Settings and map

What rules and settings are recorded for [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(?

You will not find a gather rate in the string [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( loaded?

[SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( runs a procedural map of size 3,650 with seed 7, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe schedule

On what schedule does [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( wipe?

[SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( wipes on no fixed rhythm, so there is nothing to predict. 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 7 days ago.

On [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 13 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 3.

Tags, lists

Where does [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( appear among Rust Data lists and filters?

These Rust Data lists include [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(: Modded Rust servers. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( hold?

These tags are published by [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :( and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp69 (Max players): 69 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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

What is the way into [SEA] DO NOT JOIN IF UNINVITED - Admin abuse admin rights :(?

In Rust, F1 opens the console: type client.connect 131.153.205.250:7048. 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 mp69,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp69
Max players 69 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not 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 47,275 players 11,713 servers online