Live coverage · Rust server
Offline [SEA] RustCamp | 3x | Biweekly is not on the server list right now. The figures below are from when it was last seen, 2d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Next wipe Sunday 1 November, 22:13 UTC, in 3d 7h. Biweekly: 14 days after its last wipe
This server has not put up a new map since the desk started watching it.
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.
Estimating [SEA] RustCamp | 3x | Biweekly's next wipe relies on biweekly: 14 days after its last wipe. Sunday 1 November at 22:13 UTC is the date of its next wipe. 24 days 16 hours have passed since this world was generated. Wipes every two weeks: that is the schedule its tags publish.
These are the Rust Live Stats lists [SEA] RustCamp | 3x | Biweekly fits: 3x Rust servers live now and Modded Rust servers live now. You will find it on the server list under 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.
These are the tags [SEA] RustCamp | 3x | Biweekly makes public: gmrust (Game mode): Survival here follows standard Rust; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code; ^b (Biweekly): The cycle is two weeks per wipe; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): The game changes here through plugins or settings, so it is Modded. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
[SEA] RustCamp | 3x | Biweekly is not online at the moment, having last been seen 2 days 22 hours ago. The seven-day average for this server is 0 players.
On player hours for the past seven days, [SEA] RustCamp | 3x | Biweekly sits at #15,335, inside the top 69% of ranked servers.
The name says it: gathering runs at 3x on [SEA] RustCamp | 3x | Biweekly. No custom limit is set, so groups hold the default 8 players. survival applies here, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. The plugin load is Oxide. VAC is enabled: Valve's anti-cheat.
A procedural map, generated by the game, runs on [SEA] RustCamp | 3x | Biweekly.
There is no region tag on [SEA] RustCamp | 3x | Biweekly; its name still points to Asia. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. 114.12.19.184:28015 is its address.
Rust network protocol 2635 and build 168909 on Linux is what [SEA] RustCamp | 3x | Biweekly runs. To join, your game must use the same protocol; Steam handles the update for you.
At the time of this update, [SEA] RustCamp | 3x | Biweekly is down, last seen 2 days 22 hours ago. It was online for 40 of 96 hours in the last 4 full days, or 42% of the time. On 24 October 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 114.12.19.184:28015.