Rust Server IndexCard catalogue of Rust servers

Holdings11,782 servers82,108 players158 fresh wipes

Call no.3138 On the shelf · online

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

Online 91.124.63.81:28015 checked 12m ago

Subjects 1. biweekly wipes 2. oxide
Players now
0/ 100
0% full
7-day average
1
peak 11
Rank
#3,138
top 14%
Last wipeWiped23 OCT2026 · 4d 22h ago
4d ago · biweekly schedule
Next wipe
8d 4h
Thu 5 Nov, 19:00 UTC FW
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
00.511.5215:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

02040608015:0000:0009:0019:0004:0013: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.

Record sheet C · appended

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.

Record sheet D · loan terms

Wipe schedule

from its schedule tag

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

usual gap
3 daysbetween real wipes
wipe-day peak
7players, last three wipes
crowd held
100%of its cycles kept half the crowd

Coming wipes

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

Record sheet E · date due

Wipes

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

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

EU
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 265 on average
215/ 250
EU
Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 147 on average
57/ 100
EU
Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 34 on average
43/ 200
EU
Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 25 on average
16/ 200
EU
РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10EU · groups of 8+ · biweekly · 20 on average
3/ 200
EU
Rustopia.gg - EU MediumEU · groups of 12+ · biweekly · 19 on average
16/ 200
Reference desk

Quick answers

From the figures on this page.

Settings and map

Where can you read the rules and settings that apply on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

No gather rate appears in the name [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. 8 players per group is the default limit. Filed under survival, building, gathering and raiding in the standard game. Fighting and raiding other players is permitted. The server browser lists it under Community; it is a community server. Oxide plugins are run on it. The server has VAC, Valve's anti-cheat, turned on.

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

Generated by the game, the procedural map of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly has size 4,000 and seed 1. From this page you can view the map on RustMaps; the same size and seed give the same map.

Tags

Where does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly appear among the Rust Server Index lists and filters?

The Rust Server Index lists that include [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly are Rust servers filed under Europe and Community Rust servers, indexed. It appears under the following 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.

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

The server's own tags are listed here, and the game's server browser reads them: [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly gives gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): The queue ceiling sits at 100; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): It runs build 168909; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): No region code has been set; ^b (Biweekly): The cycle runs to a wipe every fortnight; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework. The top of this page shows three items from the tags: players at present, queue and world creation time.

Wipe dates

How does a wipe day run on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

At their busiest, its recent wipes drew 7 players on average. 3 hours into the latest wipe, the crowd reached its peak. Its recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

How often is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly wiped, and on what schedule?

Its schedule is unconfirmed: too few of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's wipes are on record, and the prediction follows the tag. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. 4 days 22 hours is when its current world was made. Filed in its tags: a wipe schedule of every two weeks.

Population

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

On player hours over seven days, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly takes #3,138, within the top 14% of ranked servers.

Is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly quiet or crowded?

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is currently showing 0 players on 100 slots. Averaged across seven days: 1 players, peaking at 11. The busiest point in the last 48 hours was 21:00 UTC, averaging 2 players.

Operator and status

What version does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly use?

Rust network protocol 2635 and build 168909 on Linux is what you will find on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. The protocol must match before you can join, and Steam takes care of updating it.

Is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly reachable, and does it stay up?

Right now [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is up and running. Its reported uptime gives the last restart as roughly 8 hours ago. Of the last 7 full days, 168 of 168 hours were up, 100% of the time. It was first recorded by Rust Server Index on 20 October 2026.

Is the performance on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly good?

The last 48 hours give an average of 25 server fps and a floor of 15. The entity count reached 97,816, covering buildings, deployables and all else in the world. The peak memory figure stood at 3,760 MB. What players feel as lag is low fps together with a rising entity count.

Where in the world is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly hosted?

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly gives no region tag, so the name is the only pointer, and it points to Europe. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 91.124.63.81:28015.

Joining the server

How can you connect to [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

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

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Survival on standard Rust rules.
mp100
Max players The queue ceiling sits at 100.
ts8
Group limit Teams cap at 8, the default setting.
v2635
Protocol The protocol is 2635; older or newer clients cannot join.
cs168909
Build It runs build 168909.
ptrak
Networking Networking runs on RakNet, the game's default layer.
$r?
Region code No region code has been set.

Wipe schedule

^b
Biweekly The cycle runs to a wipe every fortnight.

Mods and access

^o
Oxide Oxide, also known as uMod, provides the plugin framework.

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.