Rust Data

rustdata.spaceservers133.206.80.160:28016.ipynb

Run all rust-data · live

‹ All servers

Online 133.206.80.160:30000 checked 10m ago

風紀委員 堤防部

moddedoxide

Connect

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

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123417:0002:0011:0020:0005:0014:00

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
12k4k6k8k26 Sep3 Oct9 Oct16 Oct22 Oct29 Oct

Top 12% 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 rhythm50%of its recent wipes
wipe-day peak6players, last three wipes
crowd held0%else halves by day 10

The first 48 hours of its last wipes

Tue 20 OctTue 20 OctSat 3 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 15 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 20 Oct, 21:45 UTC8d ago 6 NaN running 1
1 Tue 20 Oct, 10:26 UTC9d ago 6 NaN 0.5 days 0
2 Sat 3 Oct, 08:48 UTC26d ago 7 halved by day 10 17.1 days 0
3 Sat 3 Oct, 01:08 UTC26d ago 7 NaN 0.3 days 0
4 Fri 2 Oct, 12:28 UTC27d ago 7 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
133.206.80.160:30000
region
–
max players
30
group limit
8, the default
wipe schedule
–
last wipe
20 Oct 2026, 21:45 UTC
hostname
–
first seen
26 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Intoxicated SEA Sandbox - Creative | Build | NoclipEA · groups of 8+ · 10 on average19/100
1桃乐丝 UKN - 起床 | 死斗 | 训练 | 建筑 | 竞技场EA · groups of 10+ · 9 on average16/50
2『夜猫子』PVE1000倍/快乐建家/NPC建筑/F1刷物品EA · groups of 100+ · 2 on average2/188
3【南瓜】Build-TestEA · groups of 8+ · 10 on average11/101
4【开心萌橙PVE-kxmc】休闲娱乐/5倍/防抄家/任务EA · groups of 20+ · monthly · 2 on average2/150
5可爱-1000倍PVE-不掉-突袭-养殖-僵尸-无限耐久EA · groups of 8+ · biweekly · 1 on average1/100

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does 風紀委員 堤防部 rank?

Over the last seven days 風紀委員 堤防部 sits at #2,789 on player hours, in the top 12% of ranked servers.

How full does 風紀委員 堤防部 run?

The sample now reads 0 players for 風紀委員 堤防部, out of 30 slots. Over the last seven days it averaged 1 players and peaked at 5. Averaged by hour over 48 hours, 13:00 UTC is the busiest, at 2 players.

Server data

What Rust version does 風紀委員 堤防部 run?

The build is Rust network protocol 2635 and build 168909 on Windows, run by 風紀委員 堤防部. The protocol has to match before you can join, and Steam does the updating.

How reliable is 風紀委員 堤防部, and is it up?

Online is the state at the latest refresh for 風紀委員 堤防部. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 26 September 2026.

Where does 風紀委員 堤防部 sit?

The name of 風紀委員 堤防部 points to Asia, even though no region tag is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 133.206.80.160:30000 is its address.

Map and rules

Which rules apply on 風紀委員 堤防部, and what settings?

You will not find a gather rate in the string 風紀委員 堤防部. The group limit sits at the default of 8 players. Game mode build & creative, with this note: no gathering, just sandbox building. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has 風紀委員 堤防部 selected?

A procedural map runs on 風紀委員 堤防部, generated by the game.

Wipe data

When does 風紀委員 堤防部 wipe, and how often?

No next wipe can be predicted for 風紀委員 堤防部, 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. The world it runs now was generated 8 days 18 hours ago.

What is wipe day on 風紀委員 堤防部 like?

The average peak over recent wipes is 6 players. 15 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 10.

Tags and filters

Which Rust Data filters and lists contain 風紀委員 堤防部?

These Rust Data lists include 風紀委員 堤防部: Modded Rust servers, Servers with build or creative tags and Rust creative servers, listed. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Server tag: Creative ^c, 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 風紀委員 堤防部?

The game's server browser reads these tags from 風紀委員 堤防部: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): Slot count: 30; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^c (Creative): Build freely, with no gathering: sandbox mode; ^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

How can I connect to 風紀委員 堤防部?

The manual route: launch Rust, F1, then client.connect 133.206.80.160:30000. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp30,ptrak,$r?,v2635,^c,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp30
Max players Slot count: 30.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Gameplay

^c
Creative Build freely, with no gathering: sandbox mode.

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 95,389 players 11,875 servers online