StatusLive Servers online11,808 Players76,491 Populated3,745 Wiped · 3 h114 Interval5 min Date28 OCT 2026

DWG RG-S3061Server sheetchecked 7m ago

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly

Online 91.124.63.81:28015 checked 7m ago

biweekly wipes oxide
Connect
Players now 1/ 100 1% full
7-day average1peak 11
Rank#3,061top 14%
Last wipe5d agobiweekly schedule
Next wipe7d 22hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
0123421:0006:0015:0000:0009:0019:00

Hourly average and peak, UTC.

Fig. 1Players on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
Fig. 2

Server performance

02040608021:0006:0015:0000:0009:0019: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 20 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Oct22 Oct23 Oct25 Oct26 Oct28 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 22h. The force wipe · high confidence

usual gap3 daysbetween real wipes
wipe-day peak7players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

  1. 7d 22hThu 5 Nov, 19:00 UTCFW
  2. 8d 19hFri 6 Nov, 16:36 UTC
  3. 22d 19hFri 20 Nov, 16:36 UTC
  4. 35d 22hThu 3 Dec, 19:00 UTCFW
  5. 36d 19hFri 4 Dec, 16:36 UTC

The first 48 hours of its last wipes

Fri 23 OctTue 20 Oct
02.557.510+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 16:36 UTC5d ago 11 – running 0
Tue 20 Oct, 17:30 UTC8d ago 3 held half 3 days 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average
140 / 300
02
Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 135 on average
41 / 100
03
Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 31 on average
30 / 200
04
Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 25 on average
21 / 200
05
РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10EU · groups of 8+ · biweekly · 17 on average
7 / 200
06
Владивосток | ДЛЯ НОВИЧКОВ | INSOMNISEU · groups of 30+ · biweekly · 17 on average
7 / 150
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

How reliable is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, and is it online now?

At this moment [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is online. Counted from its reported uptime, the last restart was about 11 hours ago. 168 of 168 hours up over the last 7 full days, which is 100% of the time. First seen by Rust Graphs on 20 October 2026.

How does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly perform, as measured?

Average server fps over the last 48 hours is 25; the lowest was 15. Counted at its highest: 97,487 entities, buildings, deployables and the rest of the world included. 3,760 MB is the memory peak. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

Its name points to Europe, though [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly publishes no region tag. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 91.124.63.81:28015.

On which Rust version is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly running?

On Linux, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly runs Rust network protocol 2635 and build 168909. The same protocol is required for joining, and Steam updates your game to it.

Population

What player count is recorded on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

At the last refresh, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly recorded 1 players across 100 slots. The seven-day mean is 1 players; the peak over the same period is 11. Averaged over the last 48 hours, the player count is highest at 17:00 UTC: 3 players.

Against other Rust servers, where is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly placed?

Over the last seven days, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly records #3,061 for player hours: the top 14% of all ranked servers.

Wipe times

On [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, what does the data show for wipe day?

An average of 7 players was recorded at the busiest point of its recent wipes. 3 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 100% of its recent wipes stayed above half that peak.

On [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, when do wipes occur?

Too few of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 5 days 4 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.

Rules and settings

Which rules and settings are recorded for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

The name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly records no gather rate. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. The server browser lists it under Community. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.

Which map has [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly loaded?

Seed 1 and size 4,000 define the procedural map [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

On Rust Graphs, which lists and filters contain [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

These Rust Graphs lists include [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: Europe servers, plotted and Rust community servers, plotted. It is returned by these filters on the server list: Region: Europe; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week.

Which meaning is attached to each tag on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

gmrust (Game mode): Standard survival, as Rust plays; mp100 (Max players): 100 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Plugin framework: Oxide (uMod) are the tags [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

How to join

How is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly joined?

Enter client.connect 91.124.63.81:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://ekiphost.com is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp100
Max players 100 player slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code field is empty.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

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.

KeyTag string decoded