Rust Player Stats
Live UTC 49,583 playing

Online 91.124.63.81:28015 checked 15m ago

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

biweekly wipes oxide
Players now0
Slots100
Full0%
7-day average1peak 11
Rank#3,157top 14%
Last wipe4d agobiweekly schedule
Next wipe8d 9hThu 5 Nov, 19:00 UTC FW
Launch Rust and join Website

By the numbersMatch stats

against its 100 slots
Players now0
0% of the slots taken
7-day average1
players on an average hour this week
7-day peak11
the fullest it got this week
48-hour peak2
the busiest hour of the last two days
On the list46 of 48 hours
hours it answered in the last two days
Server fps29
average over 48 hours; 60 or more is smooth
Standingtop 14%
of all ranked servers, on player hours over seven days
Replay

The story of the match

Players, performance and rank, hour by hour and day by day.

CrowdPlayers

AveragePeak
00.511.5210:0019:0004:0013:0022:0007:00

Hourly average and peak, UTC.

FitnessServer performance

02040608010:0019:0004:0013:0022:0007: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.

FormRank

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.

FixturesWipe schedule

from its schedule tag

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

ResultsWipes

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.

Other matches on now

Similar servers

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

The pundits

Quick answers

From the figures on this page.

Operator and location

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

Right now [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is online. Going by the uptime it reports, the last restart came about 2 hours ago. The last 7 full days put it at 168 of 168 hours up, 100% uptime. Rust Player Stats logged it for the first time on 20 October 2026.

Does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run smoothly?

Averaging 29 server fps across the last 48 hours, it held a floor of 15. Buildings, deployables and everything else in the world pushed the entity count to 97,816. 3,760 MB of memory was the high point. Lag, to a player, is these two together: low fps and a rising entity count.

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

Rust network protocol 2635 and build 168909 on Linux: that is the setup at [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. Same protocol or no entry: your game must match, and Steam keeps it updated for you.

Where is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly located?

Nothing in the tags places [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, but its name points to Europe. Where the machine physically stands is not looked up by Rust Player Stats; it shows only what the server states. You will find it at 91.124.63.81:28015.

Tags

What do the server tags on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly mean?

Tags published by [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly and picked up by the in-game browser: gmrust (Game mode): Survival, standard Rust style; mp100 (Max players): The cap is 100 slots; ts8 (Group limit): Teams cap at 8, the game default; v2635 (Protocol): To join, your game has to run protocol 2635; cs168909 (Build): The game build here is 168909; ptrak (Networking): RakNet handles the network here, the game's standard layer; $r? (Region code): There's no region code on this one; ^b (Biweekly): The cycle is two weeks per wipe; ^o (Oxide): Oxide (uMod) provides the plugin framework here. The tags carry more besides: present players, queue length and when the world was made, all displayed at the top of this page.

Which Rust Player Stats lists and filters include [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

These Rust Player Stats lists take [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: EU Rust servers, live and Community servers, ranked live. These filters on the server list bring it up: 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.

Map and rules

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

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly runs a game-generated procedural map: size 4,000, seed 1. You can look at it on RustMaps from this page, since size and seed give the same map.

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

Nothing in the name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly states a gather rate. Groups top out at 8 players, the default for the game. survival, gather, build, raid: the standard game. PvP is on, and so is raiding. The server browser lists it under Community. Oxide plugins are running. Anti-cheat is on: VAC.

Player counts

How full is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly right now?

Out of 100 slots, 0 are taken on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly at this moment. The seven-day average sits at 1 players; the peak reached 11. It drew its biggest crowd of the last 48 hours at 21:00 UTC: 2 players on average.

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

Ranked #3,157 on seven-day player hours, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is in the top 14% of all ranked servers.

Wipe schedule

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

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. When every Rust server wipes, on Thursday 5 November at 19:00 UTC, its next wipe is the force wipe. 4 days 16 hours ago is when its current world was made. The wipe schedule in its tags is every two weeks.

What does wipe day look like on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

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

Connect

How do I join [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

Console route: F1 in Rust, then client.connect 91.124.63.81:28015. Or use Launch Rust here, which opens Rust through Steam and connects you. You will find the website at https://ekiphost.com.

GlossaryServer tags

what each one means

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

Game

gmrust
Game mode Survival, standard Rust style.
mp100
Max players The cap is 100 slots.
ts8
Group limit Teams cap at 8, the game default.
v2635
Protocol To join, your game has to run protocol 2635.
cs168909
Build The game build here is 168909.
ptrak
Networking RakNet handles the network here, the game's standard layer.
$r?
Region code There's no region code on this one.

Wipe schedule

^b
Biweekly The cycle is two weeks per wipe.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.

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.