Station EU-1060 · recording
Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly
Online EU 213.239.221.105:28015 checked 11m ago
- Players now
- 6/ 100
- 6% full
- Motion · 24 h
- M0.7▼falling
- −5 players on the day
- 7-day average
- 8
- peak 28
- Rank
- #1,060
- top 5% · #442 in EU
- Last wipe
- 12d ago
- biweekly schedule
- Next wipe
- 7d 21h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 6of 100 slots
- Motion · 24 h
- M0.7▼falling−5 players
- Sharpest hour
- −7into Tue 00:00 UTC
- Peak · 48 h
- 15most players in any hour
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 5% of all ranked servers, top 15% in EU, and #54 of the quad servers (top 7%). Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Thursday 5 November, 19:00 UTC, in 7d 21h. The force wipe · high confidence
- usual gap
- 28 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 45players, last three wipes
- crowd held
- 0%else halves by day 7
Coming wipes
- 7d 21hThu 5 Nov, 19:00 UTCFW
- 15d 19hFri 13 Nov, 17:05 UTC
- 35d 21hThu 3 Dec, 19:00 UTCFW
- 43d 19hFri 11 Dec, 17:05 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 42, 24 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 16 Oct, 17:05 UTC12d ago | M1.6▲rising | 42 | – | running | 6 | |
| Thu 1 Oct, 18:02 UTC FW27d ago | M1.6▲rising | 42 | halved by day 9 | 15 days | 3 | |
| Fri 18 Sep, 17:14 UTC40d ago | M1.7▲rising | 50 | halved by day 5 | 13 days | 5 |
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 Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly?
At size 3,900, the map on Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly is custom and its published file can be downloaded from this page.
Which settings and rules apply on Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly?
No gather rate appears in the name of Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly. The limit for a group is 4 players (quad). survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. Oxide is the plugin framework it runs. By its own description it is vanilla: rates, kits and rules are as Facepunch ships them. The server has VAC on, Valve's anti-cheat.
Live population
What is the current population on Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly?
6 of the 100 slots on Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly are filled right now. Across seven days this server recorded an average of 8 players and a peak of 28. The busiest point in the last 48 hours came at 18:00 UTC, averaging 12 players.
How does Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly rank against other Rust servers?
For player hours across the last seven days, Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly takes #1,060 overall and #442 in Europe, inside the top 5% of all ranked servers. Within quad, it places #54.
Operator and location
How reliably does Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly stay online?
As recorded now, Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly is running. Its reported uptime points to a restart about 12 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
How well does Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly perform under load?
The 48-hour average is 60 server fps; 53 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 104,601. It reached a ceiling of 4,050 MB of memory. Low fps together with a growing entity count is what players experience as lag.
Which region does Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly run from?
The EU tag is how Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly lists itself in Europe. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 213.239.221.105:28015 is the address it uses.
What build of Rust does Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly use?
Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly?
The recent wipes averaged a busiest count of 45 players. The peak on the most recent wipe came 24 hours after the wipe. Half that peak was held until the next wipe in 0% of its recent wipes. It fell under half by day 7 in the wipes where it didn't hold.
On what timetable does Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly run its wipes?
The wipe rhythm at Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly is every 4 weeks on Friday at 17:05 UTC. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 12 days 4 hours. In its tags it sets out a wipe schedule of every two weeks.
Tags
What do the server tags on Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly mean?
These are the tags Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): 100 slots are available; ts4 (Group limit): Teams are capped at 4 players; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): Rates, kits and rules are as Facepunch ships them; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; EU (Europe): Europe is the region it's listed under in the browser; rustmaps (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly appear?
These Rust Server Trends lists include Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly: EU Rust servers, Rust community servers without the side modes and Vanilla Rust servers, recorded live. These filters bring it up on the server list: Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: Quad; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Join the server
How do you connect to Captain's Quarters | Solo/Duo/Trio/Quad | Bi-weekly?
To join, enter client.connect 213.239.221.105: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. https://discord.com/invite/e8XMuWPmKa is where its website lives.
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.