Station XX-16875 · no signal
[SEA] RustCamp | 3x | Biweekly
Offline 103.94.238.201:28015 checked 29d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,875
- top 71%
- Last wipe
- 43d ago
- biweekly schedule
- Next wipe
- 7d 8h
- Thu 5 Nov, 19:00 UTC FW
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. The 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 pageRules and settings
Which map is running on [SEA] RustCamp | 3x | Biweekly?
[SEA] RustCamp | 3x | Biweekly runs a procedural map of size 3,500 with seed 12345, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on [SEA] RustCamp | 3x | Biweekly?
Going by its name, [SEA] RustCamp | 3x | Biweekly runs 3x gather. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on [SEA] RustCamp | 3x | Biweekly right now?
[SEA] RustCamp | 3x | Biweekly is not responding at this moment and is offline, last seen 29 days 20 hours ago.
How does [SEA] RustCamp | 3x | Biweekly rank against other Rust servers?
Over the last seven days, [SEA] RustCamp | 3x | Biweekly recorded enough player hours to reach #16,875 worldwide, placing it in the top 71% of all ranked servers.
Operator and location
How reliably does [SEA] RustCamp | 3x | Biweekly stay online?
No contact with [SEA] RustCamp | 3x | Biweekly right now, and the last recorded contact was 29 days 20 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 16 September 2026 is when Rust Server Trends first recorded it.
Which region does [SEA] RustCamp | 3x | Biweekly run from?
Its name points to Asia, but [SEA] RustCamp | 3x | 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. 103.94.238.201:28015 is the address it uses.
Which Rust version is [SEA] RustCamp | 3x | Biweekly running?
[SEA] RustCamp | 3x | Biweekly is running Rust network protocol 2633 and build 164530 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
On what timetable does [SEA] RustCamp | 3x | Biweekly run its wipes?
From the force wipe the next wipe of [SEA] RustCamp | 3x | Biweekly is estimated. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. 43 days 23 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.
Tags
What do the server tags on [SEA] RustCamp | 3x | Biweekly mean?
The game's server browser reads the tags [SEA] RustCamp | 3x | Biweekly publishes: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs164530 (Build): Game build: 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): A wipe comes every second week; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does [SEA] RustCamp | 3x | Biweekly appear?
You will find [SEA] RustCamp | 3x | Biweekly on the following Rust Server Trends lists: 3x Rust servers, by live population and Modded Rust servers, tracked live. You will find it under these filters 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; Gather rate: 3x.
Join the server
How do you connect to [SEA] RustCamp | 3x | 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.