Station XX-15509 · no signal
[SEA] RustCamp | Vanilla | Biweekly
Offline 103.94.238.201:28015 checked 42d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,509
- no region published
- Last wipe
- 43d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on [SEA] RustCamp | Vanilla | Biweekly?
A procedural map runs on [SEA] RustCamp | Vanilla | Biweekly, generated by the game.
Which settings and rules apply on [SEA] RustCamp | Vanilla | Biweekly?
You will find no gather rate in the name of [SEA] RustCamp | Vanilla | Biweekly. The group limit is 8 players, the game's default. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. It describes itself as vanilla, which means no changed rates, kits or rules: this is the game as Facepunch ships it. The server has VAC on, Valve's anti-cheat.
Live population
What is the current population on [SEA] RustCamp | Vanilla | Biweekly?
[SEA] RustCamp | Vanilla | Biweekly is not responding at this moment and is offline, last seen 42 days 9 hours ago.
How does [SEA] RustCamp | Vanilla | Biweekly rank against other Rust servers?
On player hours for the past week, [SEA] RustCamp | Vanilla | Biweekly sits at #15,509, which puts it inside the top – of every ranked server.
Server details
How reliably does [SEA] RustCamp | Vanilla | Biweekly stay online?
As recorded now, [SEA] RustCamp | Vanilla | Biweekly is not reachable, the last contact having been 42 days 9 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 15 September 2026.
Which region does [SEA] RustCamp | Vanilla | Biweekly run from?
Its name points to Asia, but [SEA] RustCamp | Vanilla | Biweekly publishes no region tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 103.94.238.201:28015.
What build of Rust does [SEA] RustCamp | Vanilla | Biweekly use?
On Linux, [SEA] RustCamp | Vanilla | Biweekly runs Rust network protocol 2633 and build 163794. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
On what timetable does [SEA] RustCamp | Vanilla | Biweekly run its wipes?
The rhythm of [SEA] RustCamp | Vanilla | Biweekly cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 43 days 10 hours.
Server tags
What do the server tags on [SEA] RustCamp | Vanilla | Biweekly mean?
Tags published by [SEA] RustCamp | Vanilla | Biweekly and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs163794 (Build): Game build: 163794; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does [SEA] RustCamp | Vanilla | Biweekly appear?
You will find [SEA] RustCamp | Vanilla | Biweekly on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Asia; Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
How do you connect to [SEA] RustCamp | Vanilla | Biweekly?
To join, enter client.connect 103.94.238.201:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.