Working its way up from the back of the class: #16,875 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 1,403 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 22h.
The force wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does [SEA] RustCamp | 3x | Biweekly sit?
You won't find a region tag on [SEA] RustCamp | 3x | Biweekly, but its name indicates Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 103.94.238.201:28015.
Is [SEA] RustCamp | 3x | Biweekly up, and how steady is its uptime?
The server is down: [SEA] RustCamp | 3x | Biweekly is offline now, with the last sighting 29 days 6 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 16 September 2026.
What Rust version is [SEA] RustCamp | 3x | Biweekly on?
The server [SEA] RustCamp | 3x | Biweekly is on Rust network protocol 2633 and build 164530 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does [SEA] RustCamp | 3x | Biweekly reset?
the force wipe gives the basis for estimating [SEA] RustCamp | 3x | Biweekly's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 43 days 10 hours have passed since this world was made. Its tags say it wipes every two weeks.
Population
Where does [SEA] RustCamp | 3x | Biweekly sit among Rust servers?
Over the last seven days, [SEA] RustCamp | 3x | Biweekly has #16,875 for player hours, in the top 71% of all ranked servers.
How many players does [SEA] RustCamp | 3x | Biweekly usually have?
The last sighting of [SEA] RustCamp | 3x | Biweekly was 29 days 6 hours ago, and it is offline right now.
Tags
How should you read the tags on [SEA] RustCamp | 3x | Biweekly?
You'll see [SEA] RustCamp | 3x | Biweekly tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): The game build is 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show [SEA] RustCamp | 3x | Biweekly?
Rust Server Score lists that include [SEA] RustCamp | 3x | Biweekly: 3x Rust servers, graded and Modded Rust servers, graded. It shows under the following 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.
Server rules
What settings and rules apply on [SEA] RustCamp | 3x | Biweekly?
[SEA] RustCamp | 3x | Biweekly sets gather at 3x, as its name suggests. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on [SEA] RustCamp | 3x | Biweekly?
A procedural map of size 3,500 and seed 12345, generated by the game, is what [SEA] RustCamp | 3x | Biweekly runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto [SEA] RustCamp | 3x | Biweekly?
Enter client.connect 103.94.238.201:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,^b,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find 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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).