RUST METRICSFlight deck · live data
Data live Servers11,721 Players56,361 Populated3,397 Fresh wipes 3 h136 Scan5 min
‹ All servers91.124.63.81:28015
Online Full Queue Fresh wipe Wipe due No query

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

Online 91.124.63.81:28015 checked 5m ago

biweekly wipes oxide
COM 1 · connect

Server instruments

last reading Tue 22:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 15 SERVER FPS

Server fps

48 h low 15 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 94,658 ×1000

Entities

48 h range 93,937–98,477 · memory 2,948 MB
1239 ET SINCE RESTART 1D 17H

Uptime

1 days 17 hours since its last restart, at the last reading
7-day average1peak 11
Rank#3,172top 14%
Last wipe4d agobiweekly schedule
Next wipe8d 19hThu 5 Nov, 19:00 UTC FW
Memory2,948MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5200:0009:0018:0004:0013:0022:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608000:0009:0018:0004:0013:0022: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.

REC 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 8d 19h. 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. WPT 1Thu 5 Nov, 19:00 UTC8d 19hFW
  2. WPT 2Fri 6 Nov, 16:36 UTC9d 16h
  3. WPT 3Fri 20 Nov, 16:36 UTC23d 16h
  4. WPT 4Thu 3 Dec, 19:00 UTC36d 19hFW
  5. WPT 5Fri 4 Dec, 16:36 UTC37d 16h

The first 48 hours of its last wipes

Fri 23 OctTue 20 Oct
02.557.510+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 16:36 UTC4d ago 11 – running 0
Tue 20 Oct, 17:30 UTC7d 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.

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 [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly when wipe day comes?

The busiest point of its recent wipes drew 7 players on average. 3 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

How often does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly wipe, and when?

The prediction follows its tag, because too few of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's wipes are on record to confirm its schedule. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 4 days 7 hours ago the current world was made. The tags carry an every-two-weeks wipe schedule.

Tag meanings

Which tags does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Two-week wipe schedule; ^o (Oxide): Plugin framework in use: Oxide (uMod) from [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

These Rust Metrics lists carry [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: EU Rust servers, checked and Rust community servers: live readings. Check: filters. On the server list it appears under these: 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.

Population

What position does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly hold among Rust servers?

Player hours over seven days put [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly at #3,172, in the top 14% of all ranked servers.

How full does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly get?

Current headcount on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: 0 players, 100 slots available. Seven-day check: 1 players on average. Peak reading: 11. Average at the busiest hour was 2 players, at 21:00 UTC over the last 48 hours.

Server details

Where does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly sit?

Reading: location. Nothing in the tags, but the name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly points to Europe. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 91.124.63.81:28015.

What Rust version is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly on?

Reading: [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

Is performance on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly within range?

Reading: 28 server fps on average across the last 48 hours. It never dropped below 15. Peak entity count: 98,477. Buildings, deployables and all else included. Reading: 3,863 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

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

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly reports online. Status: normal. Reading: uptime. About 41 hours ago it restarted, on its own count. Uptime for the last 6 full days: 144 of 144 hours, or 100%. Reading: first seen 20 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

Reading the name gives no gather rate for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

Size 4,000 and seed 1: the game generates the procedural map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

What do you do to join [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

Check: join. Open Rust, press F1, then enter client.connect 91.124.63.81:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://ekiphost.com is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Mods and access

^o
Oxide Plugin framework in use: 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.