Rust Data LabData lab · live
Live readings Servers11,682 Players55,436 Populated3,376 Fresh wipes · 3h102 Sampled every 5 min

Element card · group Community · atomic number 3,159, its rank

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

Online 91.124.63.81:28015 checked 10m ago

biweekly wipes oxide
Join the experiment
Atomic mass · players now 0/ 100 0% full Room to join
7-day average1peak 11
Rank · atomic number#3,159top 14%
Last wipe4d agobiweekly schedule
Next wipe8d 8hThu 5 Nov, 19:00 UTC FW
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
00.511.5211:0020:0005:0014:0023:0008:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
02040608011:0020:0005:0014:0023:0008: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.

Result 03

Rank

Result

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.

Reaction kinetics

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 8d 8h. 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. 8d 8hThu 5 Nov, 19:00 UTCFW
  2. 9d 6hFri 6 Nov, 16:36 UTC
  3. 23d 6hFri 20 Nov, 16:36 UTC
  4. 36d 8hThu 3 Dec, 19:00 UTCFW
  5. 37d 6hFri 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

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

Reaction 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rustoria.co - … 152
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 273 on average 152/ 200
  2. 2 Ru Rustafied.com … 44
    Rustafied.com - EU Medium - Large EU · groups of 16+ · biweekly · 150 on average 44/ 100
  3. 3 Ru Rusty Moose |E… 22
    Rusty Moose |EU Biweekly| EU · groups of 12+ · biweekly · 36 on average 22/ 200
  4. 4 Ru Rustoria.co - … 4
    Rustoria.co - EU Medium EU · groups of 12+ · biweekly · 26 on average 4/ 200
  5. 5 Ро РОССИЯ#2|КЛАСС… 7
    РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10 EU · groups of 8+ · biweekly · 21 on average 7/ 200
  6. 6 Ru Rustopia.gg - … 10
    Rustopia.gg - EU Medium EU · groups of 12+ · biweekly · 20 on average 10/ 200

Quick answers

from the figures on this page

Server setup

What map is in play on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

The map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is procedural at size 4,000 with seed 1, made by the game. The map repeats when size and seed match, and you can view it on RustMaps from this page.

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

No gather rate appears in the name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. Groups top out at 8 players, the default for the game. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. It appears under Community in the server browser. The plugin count is Oxide. Anti-cheat is on: Valve's VAC.

Server facts

In what location does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly sit?

The name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly points to Europe, even without a region tag. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 91.124.63.81:28015 is the address it uses.

On what Rust version does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly operate?

On Linux, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is running Rust network protocol 2635 and build 168909. Your game needs to match the protocol to join, and Steam updates it automatically.

How reliably does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly stay online?

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is live as of now. The uptime it reports suggests it restarted roughly 3 hours ago. It was online for 168 of 168 hours in the last 7 full days, which is 100% uptime. The first sighting by Rust Data Lab was on 20 October 2026.

Is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly known for smooth running?

In the last 48 hours, it averaged 28 server fps, with a low of 15. The entity count reached 97,816, including buildings, deployables and all other world items. Memory use peaked at 3,760 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipes and resets

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

The prediction for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly follows its tag, as too few wipes are on record to confirm the schedule. The next time this server wipes will be the force wipe on Thursday 5 November at 19:00 UTC, which wipes every Rust server. Counting back, the current world began 4 days 17 hours ago. Wipes every two weeks are what its tags set out.

What does a typical wipe day on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly involve?

At their busiest, recent wipes averaged 7 players. The latest wipe's peak fell 3 hours after it began. Above half the peak until the next wipe: that held in 100% of its recent wipes.

Tags, lists

How should you read the tags on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

These are the tags [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly makes public for the server browser to read: gmrust (Game mode): Standard Rust survival is the game here; mp100 (Max players): 100 is the slot count; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): The region field is left blank; ^b (Biweekly): Every two weeks, the server wipes; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Where among the Rust Data Lab lists and filters does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly come up?

You will find [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly on the following Rust Data Lab lists: EU Rust servers, measured and Rust community servers, measured. These filters bring it up 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.

Population

How does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly compare with other servers in the rankings?

The seven-day player-hours table has [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly at #3,159, in the top 14% of ranked servers.

How many players does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly have at the moment?

At the moment [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly has 0 of its 100 slots filled. Averaged over the past week: 1 players, peaking at 11. Peak time in the past 48 hours: 21:00 UTC, when the average was 2 players.

Getting on

What is the way to join [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

In Rust, press F1 and enter client.connect 91.124.63.81:28015. Or click Launch Rust here to open Rust via Steam and connect automatically. You can find its website at https://ekiphost.com.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game here.
mp100
Max players 100 is the slot count.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code The region field is left blank.

Wipe schedule

^b
Biweekly Every two weeks, the server wipes.

Mods and access

^o
Oxide A plugin framework called Oxide (uMod) powers the plugins.

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.