Offline 114.12.17.185:28015 checked 24d ago
[SEA] RustCamp | 3x | Biweekly
Connect
srv = rust.server("114.12.17.185: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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 10h. # The force 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.17.185:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 15 Sep 2026, 10:24 UTC
- hostname
- –
- first seen
- 1 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 · 82 on average | 60/115 |
| 1 | Japan Tokyo - Limited Raid Hours |3x|PvP|JP | EA · groups of 8+ · 3x · weekly · 40 on average | 11/300 |
| 2 | [SEA] Rust Manila 2x | Biweekly | EA · groups of 8+ · 2x · biweekly · 24 on average | 47/150 |
| 3 | JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TP | EA · groups of 32+ · 5x · biweekly · 14 on average | 16/120 |
| 4 | [TW-JP-KR-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 | EA · groups of 12+ · 5x · biweekly · 14 on average | 4/200 |
| 5 | Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long | EA · groups of 100+ · 3x · monthly · 7 on average | 9/120 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does [SEA] RustCamp | 3x | Biweekly rank?
Rank #15,961 on seven-day player hours for [SEA] RustCamp | 3x | Biweekly, within the top 71% of all ranked servers.
How many players does [SEA] RustCamp | 3x | Biweekly hold at once?
The current row shows [SEA] RustCamp | 3x | Biweekly offline; the last response was 24 days 10 hours ago.
Server facts
Which Rust version is [SEA] RustCamp | 3x | Biweekly on?
The build is Rust network protocol 2633 and build 164530 on Linux, run by [SEA] RustCamp | 3x | Biweekly. Joining needs the same protocol on your game; Steam handles the update.
How reliable is [SEA] RustCamp | 3x | Biweekly, and is it up?
Offline now for [SEA] RustCamp | 3x | Biweekly, last seen 24 days 10 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 1 October 2026.
Where does [SEA] RustCamp | 3x | Biweekly sit?
The name of [SEA] RustCamp | 3x | Biweekly points to Asia, even though no region tag is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 114.12.17.185:28015.
Rules, settings, map
Which settings and rules does [SEA] RustCamp | 3x | Biweekly run?
The name carries the figure: [SEA] RustCamp | 3x | Biweekly runs 3x gather. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
What is the map on [SEA] RustCamp | 3x | Biweekly?
The game generates its map: procedural, on [SEA] RustCamp | 3x | Biweekly.
Wipe schedule
On what schedule does [SEA] RustCamp | 3x | Biweekly wipe?
An estimate from the force wipe gives [SEA] RustCamp | 3x | Biweekly's next wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 43 days 22 hours ago, and that is the one in play. The tags list a two-weekly wipe cycle.
Tags, lists
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): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): Build number: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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
How can I connect to [SEA] RustCamp | 3x | Biweekly?
Enter client.connect 114.12.17.185:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.