Rust Server Analytics 63,224 players11,690 servers
All servers
Drill-through Server detail

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

Online 91.124.63.81:28015 checked 12m ago

Drill-through
FilterServeris [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
Attributes
biweekly wipes oxide
Last refreshed
Players now 0/ 100
7-day average 1 peak 11
Rank #3,151 top 14%
Last wipe 4d ago biweekly schedule
Next wipe 8d 7h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
00.511.5212:0021:0006:0015:0000:0009:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
02040608012:0021:0006:0015:0000:0009: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.

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.

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 8d 7h. 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

InWhen, UTCKind
8d 7hThu 5 Nov, 19:00 UTCFW force wipe
9d 5hFri 6 Nov, 16:36 UTCits own
23d 5hFri 20 Nov, 16:36 UTCits own
36d 7hThu 3 Dec, 19:00 UTCFW force wipe
37d 5hFri 4 Dec, 16:36 UTCits own

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.

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
ServerProfilePlayers now
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 272 on average 153 / 200
Rustafied.com - EU Medium - Large EU · groups of 16+ · biweekly · 150 on average 58 / 100
Rusty Moose |EU Biweekly| EU · groups of 12+ · biweekly · 36 on average 29 / 200
Rustoria.co - EU Medium EU · groups of 12+ · biweekly · 26 on average 8 / 200
РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10 EU · groups of 8+ · biweekly · 21 on average 9 / 200
Rustopia.gg - EU Medium EU · groups of 12+ · biweekly · 19 on average 11 / 200

Quick answers

from the figures on this page

Wipe cycle

On what cycle does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly wipe?

The prediction follows its tag, because too few of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's wipes are on record to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe that reaches every Rust server. 4 days 18 hours ago the current world was made. A wipe every two weeks is stated in its tags.

On [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, what happens on wipe day?

Recent wipes averaged a busiest count of 7 players. The highest player count on the latest wipe arrived 3 hours in. Recent wipes held the crowd above half that peak until the next wipe in 100% of cases.

Server details

Which location hosts [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

No region tag is published by [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, but the name points to Europe. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. 91.124.63.81:28015 is its address.

What Rust build does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run?

On Linux, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly runs Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam handles the update.

Is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly up, and how steady is its uptime?

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly reports online at the current check. Its reported uptime indicates a restart roughly 4 hours ago. 100% uptime over the last 7 full days, equal to 168 of 168 hours. 20 October 2026 is when Rust Server Analytics first recorded it.

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

Over 48 hours the average held at 28 server fps, and the minimum was 15. At its highest the entity count was 97,816, including buildings, deployables and all else. Memory use reached 3,760 MB at peak. Players experience lag as low fps combined with a rising entity count.

Tags

What do [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's tags stand for?

Tags from [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, as read by the game's server browser, are: gmrust (Game mode): Rust survival, standard ruleset; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default team size of 8; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank; ^b (Biweekly): Every two weeks the server wipes; ^o (Oxide): It runs Oxide (uMod) for plugins. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Where does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly appear across Rust Server Analytics's lists and filters?

Among the Rust Server Analytics lists [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly fits are: EU Rust servers: live population data and Community Rust servers, live. It appears on the server list under the following filters: 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

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

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

What is the population of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly holds 0 players of its 100 slots as of the latest update. Averaging 1 players across seven days, the server reached a peak of 11. Across the last 48 hours, 21:00 UTC shows the highest average: 2 players.

Settings

What are the settings on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, and its rules?

No gather rate is given in the name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. No custom group limit: 8 players is the standard. survival is the game mode, the standard game: gather, build, raid. Raiding and PvP combat are available. Community is its listing; it is a community server. Plugins from Oxide are in use. VAC, Valve's anti-cheat, is enabled.

The map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: which one is it?

The game generates a procedural map of size 4,000 with seed 1 for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. Size and seed fix the map, so a RustMaps view is available from this page.

Connection

How can a player join [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 91.124.63.81:28015. Find it online 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 Rust survival, standard ruleset.
mp100
Max players 100 slots in total.
ts8
Group limit Default team size of 8.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build The game build is 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code The region code is blank.

Wipe schedule

^b
Biweekly Every two weeks the server wipes.

Mods and access

^o
Oxide It runs Oxide (uMod) for 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.