Online 123.192.255.191:28015 checked 12m ago
#2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥
Connect
srv = rust.server("123.192.255.191:28016")
print(srv.connect_command)Right now
srv.summary()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. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Friday 30 October, 09:05 UTC, in 21h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 21h | Fri 30 Oct, 09:05 UTC | wipe |
| 1 | 7d 7h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 14d 21h | Fri 13 Nov, 09:05 UTC | wipe |
| 3 | 28d 21h | Fri 27 Nov, 09:05 UTC | wipe |
| 4 | 35d 7h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 42d 21h | Fri 11 Dec, 09:05 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 09:05 UTC13d ago | 4 | NaN | running | 0 |
| 1 | Fri 2 Oct, 06:52 UTC27d ago | 5 | halved by day 6 | 14.1 days | 0 |
| 2 | Sun 27 Sep, 08:17 UTC32d ago | 3 | held half | 4.9 days | 0 |
| 3 | Fri 18 Sep, 05:51 UTC41d ago | 4 | halved by day 7 | 9.1 days | 1 |
# 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 1673229444![Map of #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥](https://files.facepunch.com/rust/map-images/2b23e634b1df2a68e39760c9f0d55f401f3ff88f670f5e975e411a1b7335ba07/proceduralmap.4500.1792141491269.289_2b23e634b1df2a68e39760c9f0d55f40.jpg)
- map
- Procedural Map
- size
- 4500
- seed
- 1673229444
Server
srv.info()- address
- 123.192.255.191:28015
- region
- –
- max players
- 60
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 16 Oct 2026, 09:05 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 | JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TP | EA · groups of 32+ · 5x · biweekly · 14 on average | 27/120 |
| 1 | [TW-JP-KR-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 | EA · groups of 12+ · 5x · biweekly · 13 on average | 7/200 |
| 2 | Rustmaniac SEA 10X | Loot++ | Kits | TPs | VIP | EA · groups of 10+ · 10x · weekly · 4 on average | 2/150 |
| 3 | [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 | EA · groups of 8+ · 2x · biweekly · 82 on average | 61/115 |
| 4 | [SEA] Rust Manila 2x | Biweekly | EA · groups of 8+ · 2x · biweekly · 24 on average | 62/150 |
| 5 | ［JP］初心者PVPサーバー｜RaidTime・ Events | EA · groups of 10+ · biweekly · 16 on average | 13/100 |
Quick answers
From the figures on this page.
Population data
How does #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 compare in the rankings?
Over the last seven days #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 sits at #3,128 on player hours, in the top 14% of ranked servers.
How full does #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 run?
#2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 reports 0 players at this refresh, with 60 slots configured. Over the last seven days it averaged 1 players and peaked at 9. Averaged by hour over 48 hours, 08:00 UTC is the busiest, at 2 players.
Server facts
What does performance look like on #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥?
Averaged over 48 hours: 193 server fps, never under 38. Entity numbers reached 164,141, and that includes buildings, deployables and the rest. The memory field tops out at 4,588 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥?
The build is Rust network protocol 2635 and build 168909 on Windows, run by #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥. Joining needs the same protocol on your game; Steam handles the update.
Is #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 up, and what does its uptime show?
#2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 reports itself online at the current refresh. The uptime it reports puts the last restart about 3 hours ago. Uptime of 95% across the last 7 full days: 159 hours of 168. Rust Data logged it first on 13 September 2026.
Where does #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 sit?
Its name points to Asia, but #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 publishes no region tag. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 123.192.255.191:28015.
Settings and map
Which rules apply on #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥, and what settings?
The name carries the figure: #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 runs 10x gather. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 selected?
Size 4,500, seed 1673229444: the procedural map on #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥, 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 #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 wipe, and on what schedule?
The prediction follows the tag, because #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥's wipes on record are too few to confirm the schedule. The schedule puts the next wipe on Friday 30 October at 09:05 UTC. A new world was started 13 days 2 hours ago, and that is the one in play. A fortnightly wipe schedule is published in its tags.
On #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥, what happens on wipe day?
Recent wipes averaged 4 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 33% of recent wipes. Otherwise the crowd fell below half by day 6.5.
Tags and filters
Which lists on Rust Data hold #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥, and which filters?
These Rust Data lists include #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥: Modded Rust servers and 10x Rust servers: the live sample. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 10x.
How should you read the server tags on #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥?
These tags are published by #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp60 (Max players): The server lists 60 slots; 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): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to #2[搞就完了]新開｜10X｜秒造快燒｜龍爭虎鬥?
Enter client.connect 123.192.255.191:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.