RUST METRICSFlight deck · live data
Data live Servers11,790 Players78,914 Populated3,567 Fresh wipes 3 h245 Scan5 min
‹ All servers108.136.160.56:28015
Online Full Queue Fresh wipe Wipe due No query

[SEA] RustCamp | 3x | Biweekly

Online 108.136.160.56:28015 checked 13m ago

3x biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 21:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 193 SERVER FPS

Server fps

48 h low 183 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 69,527 ×1000

Entities

48 h range 67,190–69,679 · memory 2,470 MB
1239 ET SINCE RESTART 3D 03H

Uptime

3 days 3 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,276top 69%
Last wipe25d agobiweekly schedule
Next wipe2d 23hSun 1 Nov, 22:13 UTC
Memory2,470MBat the last reading
REC 1

Players

AveragePeak
0123423:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040023:0008:0017:0003:0012:0021: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k29 Sep5 Oct11 Oct17 Oct23 Oct29 Oct

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

PLAN

Wipe schedule

from its schedule tag

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

wipe-day peak0players, last three wipes

Coming wipes

  1. WPT 1Sun 1 Nov, 22:13 UTC2d 23h
  2. WPT 2Thu 5 Nov, 19:00 UTC6d 20hFW
  3. WPT 3Sun 15 Nov, 22:13 UTC16d 23h
  4. WPT 4Sun 29 Nov, 22:13 UTC30d 23h
  5. WPT 5Thu 3 Dec, 19:00 UTC34d 20hFW

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 22:13 UTC25d ago 0 – running 0

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on [SEA] RustCamp | 3x | Biweekly when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does [SEA] RustCamp | 3x | Biweekly wipe?

Its tag guides the prediction: too few of [SEA] RustCamp | 3x | Biweekly's wipes are on record to confirm its schedule. On Sunday 1 November at 22:13 UTC its next wipe is due. The world it runs now was made 25 days ago. The tags carry an every-two-weeks wipe schedule.

Tags

Which tags does [SEA] RustCamp | 3x | Biweekly carry, and what do they mean?

These are the tags [SEA] RustCamp | 3x | Biweekly publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): It wipes once a fortnight; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does [SEA] RustCamp | 3x | Biweekly appear in Rust Metrics lists and filters?

On Rust Metrics, [SEA] RustCamp | 3x | Biweekly sits in these lists: 3x Rust servers, checked live and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: 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.

Population

What position does [SEA] RustCamp | 3x | Biweekly hold among Rust servers?

Player hours over seven days put [SEA] RustCamp | 3x | Biweekly at #15,276, in the top 69% of all ranked servers.

What player count does [SEA] RustCamp | 3x | Biweekly carry?

0 of 50 slots are filled on [SEA] RustCamp | 3x | Biweekly right now. A seven-day average of 0 players is the reading.

Server

What location is [SEA] RustCamp | 3x | Biweekly hosted in?

Reading: location. Nothing in the tags, but the name of [SEA] RustCamp | 3x | Biweekly points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 108.136.160.56:28015.

What Rust version is [SEA] RustCamp | 3x | Biweekly on?

Rust network protocol 2635 and build 168909 on Linux is the build [SEA] RustCamp | 3x | Biweekly runs. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for [SEA] RustCamp | 3x | Biweekly?

Over the last 48 hours the average was 212 server fps; the floor was 183. Peak entity count: 69,679. Buildings, deployables and all else included. Memory peak: 2,708 MB. Expect lag when fps falls and entities climb.

Is [SEA] RustCamp | 3x | Biweekly up, and how often does it stay up?

[SEA] RustCamp | 3x | Biweekly reports online. Status: normal. Reading: uptime. About 3 days 3 hours ago it restarted, on its own count. Reading: 65% uptime over the last 7 full days. It was up 110 of 168 hours. The first sighting on Rust Metrics was 29 September 2026.

Settings and map

How is [SEA] RustCamp | 3x | Biweekly configured, and what rules are in force?

The name carries the rate: 3x gather on [SEA] RustCamp | 3x | Biweekly. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on [SEA] RustCamp | 3x | Biweekly?

Size 3,500 and seed 12345: the game generates the procedural map on [SEA] RustCamp | 3x | Biweekly from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How do you connect to [SEA] RustCamp | 3x | Biweekly?

Press F1 in Rust and enter client.connect 108.136.160.56:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

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.