Rust Server TrendsSeismic network · station log
Recording Stations11,597 Players34,396 Active2,832 Wipes · 3 h63 48 h

Station XX-15423 · recording

[SEA] RustCamp | 3x | Biweekly

Online 108.136.160.56:28015 checked 14m ago

3x biweekly wipes moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak –
Rank
#15,423
top 69%
Last wipe
23d ago
biweekly schedule
Next wipe
4d 17h
Sun 1 Nov, 22:13 UTC
Seismic record · station XX-15423 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123416:0023:0006:0013:0020:0003:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040016:0023:0006:0013:0020:0003:00

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 29 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k29 Sep5 Oct11 Oct16 Oct22 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

from its schedule tag

Next wipe Sunday 1 November, 22:13 UTC, in 4d 17h. Its biweekly schedule tag · low confidence

wipe-day peak
0players, last three wipes

Coming wipes

  1. 4d 17hSun 1 Nov, 22:13 UTC
  2. 8d 13hThu 5 Nov, 19:00 UTCFW
  3. 18d 17hSun 15 Nov, 22:13 UTC
  4. 32d 17hSun 29 Nov, 22:13 UTC
  5. 36d 13hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sun 4 Oct, 22:13 UTC23d ago M0.0steady 0 – running 0

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 EA · groups of 8+ · 2x · biweekly · 78 on average
65/ 115
Japan Tokyo - Limited Raid Hours |3x|PvP|JP EA · groups of 8+ · 3x · weekly · 38 on average
16/ 300
[SEA] Rust Manila 2x | Biweekly EA · groups of 8+ · 2x · biweekly · 29 on average
7/ 150
[TW-JP-KR-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 EA · groups of 12+ · 5x · biweekly · 14 on average
4/ 200
JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TP EA · groups of 32+ · 5x · biweekly · 13 on average
13/ 120
Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long EA · groups of 100+ · 3x · monthly · 6 on average
7/ 120
Readings, in words

Quick answers

from the figures on this page

Map and rules

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. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on [SEA] RustCamp | 3x | Biweekly?

Going by its name, [SEA] RustCamp | 3x | Biweekly runs 3x gather. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on [SEA] RustCamp | 3x | Biweekly right now?

A reading taken now shows 0 players on [SEA] RustCamp | 3x | Biweekly, which has 50 slots. Averaged across the last seven days, the population was 0 players.

How does [SEA] RustCamp | 3x | Biweekly rank against other Rust servers?

The last seven days of player hours place [SEA] RustCamp | 3x | Biweekly at #15,423, in the top 69% of all ranked servers.

Operator and location

How reliably does [SEA] RustCamp | 3x | Biweekly stay online?

[SEA] RustCamp | 3x | Biweekly is up at the moment. Its reported uptime points to a restart about 33 hours ago. Of the 168 hours in the last 7 full days, it was up for 111, or 66% of the time. Its earliest appearance in the records of Rust Server Trends dates to 29 September 2026.

Does [SEA] RustCamp | 3x | Biweekly hold a steady tick rate?

The 48-hour average is 222 server fps; 183 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 69,800. Memory use peaked at 2,233 MB. What you feel as lag is the combination of low fps and a rising entity count.

Where in the world is [SEA] RustCamp | 3x | Biweekly hosted?

The name of [SEA] RustCamp | 3x | Biweekly points to Asia, even though it publishes no region tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 108.136.160.56:28015 is the address it uses.

Which Rust version is [SEA] RustCamp | 3x | Biweekly running?

On Linux, [SEA] RustCamp | 3x | Biweekly runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on [SEA] RustCamp | 3x | Biweekly?

On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.

How often does [SEA] RustCamp | 3x | Biweekly wipe, and on which days?

The prediction is taken from its tag, since [SEA] RustCamp | 3x | Biweekly has too few wipes on record to confirm the schedule. Sunday 1 November at 22:13 UTC is when its next wipe is due. 23 days 6 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.

Server tags

What do the server tags on [SEA] RustCamp | 3x | Biweekly mean?

These are the tags [SEA] RustCamp | 3x | Biweekly publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; 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. 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 | 3x | Biweekly appear?

These Rust Server Trends lists include [SEA] RustCamp | 3x | Biweekly: 3x Rust servers, by live population and Modded Rust servers, tracked live. On the server list, the filters it matches are: 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.

How to join

What steps get you onto [SEA] RustCamp | 3x | Biweekly?

Enter client.connect 108.136.160.56:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^b,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players Slots: 50.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Wipe schedule

^b
Biweekly A wipe comes every second week.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

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.