Online EA 203.135.196.151:21000 checked 12m ago
[JP][PvE]Babury Server Ver7.0
Connect
srv = rust.server("203.135.196.151:21003")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 bestTop 14% of all ranked servers, top 52% in EA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 6h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 6h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 12, 19 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 10:41 UTC27d ago | 12 | NaN | running | 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
4000 · seed 1372262969![Map of [JP][PvE]Babury Server Ver7.0](https://files.facepunch.com/rust/map-images/05dc667dde01bc63f8d0eed97a161335aa94611dd818f7efcf792d765d67b48a/proceduralmap.4000.1790940920740.289_05dc667dde01bc63f8d0eed97a161335.jpg)
- map
- Procedural Map
- size
- 4000
- seed
- 1372262969
Server
srv.info()- address
- 203.135.196.151:21000
- region
- EA
- max players
- 30
- group limit
- 12 max
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 11:35 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖 | EA · groups of 8+ · monthly · 35 on average | 37/100 |
| 1 | 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 21/88 |
| 2 | [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 | EA · groups of 8+ · monthly · 12 on average | 15/100 |
| 3 | [JP]ちょっぴりHard-PvE RiSu Server | EA · groups of 8+ · monthly · 11 on average | 21/100 |
| 4 | 【青岩-PVE服】原倍/萌新/突袭据点 | EA · groups of 8+ · monthly · 11 on average | 17/200 |
| 5 | 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 | EA · groups of 16+ · monthly · 10 on average | 14/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does [JP][PvE]Babury Server Ver7.0 rank?
On seven-day player hours [JP][PvE]Babury Server Ver7.0 is #3,133 overall and #283 in Asia, inside the top 14% of all ranked servers.
What population does [JP][PvE]Babury Server Ver7.0 carry?
[JP][PvE]Babury Server Ver7.0 reports 3 players at this refresh, with 30 slots configured. Over the last seven days it averaged 1 players and peaked at 5. The 48-hour sample puts the busiest hour at 11:00 UTC, averaging 4 players.
Server facts
How smoothly does [JP][PvE]Babury Server Ver7.0 run?
Averaged over 48 hours: 194 server fps, never under 86. The entity count peaked at 154,703, covering buildings, deployables and the rest of the world. The memory field tops out at 4,251 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on [JP][PvE]Babury Server Ver7.0?
The build is Rust network protocol 2635 and build 168909 on Linux, run by [JP][PvE]Babury Server Ver7.0. Joining needs the same protocol on your game; Steam handles the update.
How reliable is [JP][PvE]Babury Server Ver7.0, and is it online now?
[JP][PvE]Babury Server Ver7.0 reports itself online at the current refresh. A restart about 16 hours ago is what its reported uptime implies. Uptime of 93% across the last 7 full days: 157 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Where does [JP][PvE]Babury Server Ver7.0 sit?
With its EA tag, [JP][PvE]Babury Server Ver7.0 lists itself in Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. 203.135.196.151:21000 is its address.
Map and rules
Which settings and rules does [JP][PvE]Babury Server Ver7.0 run?
You will not find a gather rate in the string [JP][PvE]Babury Server Ver7.0. 12 players is the maximum per group. Recorded as pve, player combat is not allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. Its own label is vanilla: facepunch's stock game, with rates, kits and rules untouched. VAC, Valve's anti-cheat, is enabled.
Which map has [JP][PvE]Babury Server Ver7.0 selected?
The game generates the map on [JP][PvE]Babury Server Ver7.0: procedural, size 4,000, seed 1372262969. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does [JP][PvE]Babury Server Ver7.0 wipe, and on what schedule?
Once a month [JP][PvE]Babury Server Ver7.0 wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 27 days 1 hours ago. The tags list wipes as monthly.
What is wipe day on [JP][PvE]Babury Server Ver7.0 like?
Recent wipes averaged 12 players at their peak. 19 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain [JP][PvE]Babury Server Ver7.0?
These Rust Data lists include [JP][PvE]Babury Server Ver7.0: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Region: Asia; Type: Vanilla and Modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on [JP][PvE]Babury Server Ver7.0?
The game's server browser reads these tags from [JP][PvE]Babury Server Ver7.0: gmvanilla (Game mode): The mode is vanilla survival; mp30 (Max players): The server lists 30 slots; ts12 (Group limit): The team cap is 12; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon; EA (East Asia): In the server browser it sits under East Asia. 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 [JP][PvE]Babury Server Ver7.0?
In Rust, F1 opens the console: type client.connect 203.135.196.151:21000. Launch Rust on this page does the same by opening the game through Steam and connecting. https://rust.babury.net is the website recorded for it.