Offline 114.12.19.184:28015 checked 3d ago
[SEA] RustCamp | 3x | Biweekly
Connect
srv = rust.server("114.12.19.184:28017")
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. 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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Next wipe Sunday 1 November, 22:13 UTC, in 2d 22h. # Biweekly: 14 days after its last wipe
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 114.12.19.184:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 4 Oct 2026, 22:13 UTC
- hostname
- –
- first seen
- 24 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 | EA · groups of 8+ · 2x · biweekly · 84 on average | 9/115 |
| 1 | Japan Tokyo - Limited Raid Hours |3x|PvP|JP | EA · groups of 8+ · 3x · weekly · 40 on average | 4/300 |
| 2 | [SEA] Rust Manila 2x | Biweekly | EA · groups of 8+ · 2x · biweekly · 26 on average | 30/150 |
| 3 | JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TP | EA · groups of 32+ · 5x · biweekly · 15 on average | 6/120 |
| 4 | [TW-JP-KR-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 | EA · groups of 12+ · 5x · biweekly · 13 on average | 3/200 |
| 5 | Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long | EA · groups of 100+ · 3x · monthly · 7 on average | 5/120 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does [SEA] RustCamp | 3x | Biweekly rank?
Rank #15,290 on seven-day player hours for [SEA] RustCamp | 3x | Biweekly, within the top 69% of all ranked servers.
What population does [SEA] RustCamp | 3x | Biweekly carry?
Offline now for [SEA] RustCamp | 3x | Biweekly, with the last sample 3 days 7 hours ago. Over the last seven days it averaged 0 players.
Server data
What Rust version does [SEA] RustCamp | 3x | Biweekly run?
Rust network protocol 2635 and build 168909 on Linux is what [SEA] RustCamp | 3x | Biweekly runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is [SEA] RustCamp | 3x | Biweekly, and is it online now?
Offline now for [SEA] RustCamp | 3x | Biweekly, last seen 3 days 7 hours ago. Uptime of 42% across the last 4 full days: 40 hours of 96. Rust Data logged it first on 24 October 2026.
Where does [SEA] RustCamp | 3x | Biweekly sit?
No region tag is published by [SEA] RustCamp | 3x | Biweekly, though its name points to Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 114.12.19.184:28015.
Map and rules
Which rules apply on [SEA] RustCamp | 3x | Biweekly, and what settings?
Gather sits at 3x, read from the server's own name: [SEA] RustCamp | 3x | Biweekly. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on [SEA] RustCamp | 3x | Biweekly?
The game generates its map: procedural, on [SEA] RustCamp | 3x | Biweekly.
Wipes and dates
When does [SEA] RustCamp | 3x | Biweekly wipe, and how often?
An estimate from biweekly: 14 days after its last wipe gives [SEA] RustCamp | 3x | Biweekly's next wipe. Sunday 1 November at 22:13 UTC is when the next wipe is due. The world it runs now was generated 25 days 1 hours ago. A fortnightly wipe schedule is published in its tags.
Tags and filters
Which lists on Rust Data hold [SEA] RustCamp | 3x | Biweekly, and which filters?
The Rust Data lists that [SEA] RustCamp | 3x | Biweekly fits are: Modded Rust servers and 3x Rust servers, filtered live. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Gather rate: 3x.
Which meanings do the tags on [SEA] RustCamp | 3x | Biweekly hold?
Read by the game's server browser, the tags [SEA] RustCamp | 3x | Biweekly publishes are: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^b (Biweekly): Wipes run on a two-week cycle; ^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.
Connecting
How can I connect to [SEA] RustCamp | 3x | Biweekly?
The manual route: launch Rust, F1, then client.connect 114.12.19.184:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.