Rust Dashboard73,779 playing

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

Online 91.124.63.81:28015 checked 11m ago

biweekly wipes oxide

Players now

Live
0of 100
Full
0%
In queue
0
Peak, 48 hours
3
Peak, 7 days
11

0% full

Sun 22:00Tue 20:00players each hour · 48 hours · UTC

Rank

#3,116

top 14%

7-day average

1

peak 11

Last wipe

4d ago

biweekly schedule

Next wipe

8d 21h

Thu 5 Nov, 19:00 UTC FW

Players

AveragePeak
0123422:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

02040608022:0007:0016:0002:0011:0020: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 Oct21 Oct23 Oct24 Oct26 Oct27 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 21h. The force wipe · high confidence

3 daysusual gapbetween real wipes
7wipe-day peakplayers, last three wipes
100%crowd heldof its cycles kept half the crowd

Coming wipes

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

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
    Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average
    165/ 200
  2. 2
    Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 156 on average
    80/ 100
  3. 3
    Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 39 on average
    28/ 200
  4. 4
    Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 27 on average
    14/ 200
  5. 5
    Rustopia.gg - EU MediumEU · groups of 12+ · biweekly · 23 on average
    7/ 200
  6. 6
    РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10EU · groups of 8+ · biweekly · 22 on average
    11/ 200

Quick answers

from the figures on this page

Server details

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

Players can join [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: it is online. The uptime it reports puts its last restart about 39 hours ago. It was online 100% of the last 6 full days, which is 144 of 144 hours. Rust Dashboard logged it for the first time on 20 October 2026.

Which version of Rust 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 needs the same protocol on your side, and Steam handles that update.

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

No region tag comes from [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, though the name points to Europe. Rust Dashboard takes the location a server gives; the machine's real position is not checked. You'll connect at 91.124.63.81:28015.

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

Server fps averaged 30 over the last 48 hours and never dropped below 15. The world held as many as 98,477 entities, counting buildings, deployables and all the rest. Memory use peaked at 3,863 MB. A low fps figure and an entity count that keeps rising are what lag feels like to players.

Tags

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

The Rust Dashboard lists that carry [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly are: Best Rust community servers and Europe's Rust servers, live. It appears under these filters when you browse 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.

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

These are the tags [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly publishes, read by the game's server browser: gmrust (Game mode): The game runs on standard Rust survival settings; mp100 (Max players): The server has 100 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): This one runs game build 168909; ptrak (Networking): The game's standard network layer, RakNet, carries this server; $r? (Region code): This server sets no region code; ^b (Biweekly): Every two weeks brings a wipe; ^o (Oxide): This server runs Oxide (uMod) for plugins. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

Player counts

How busy is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

As things stand, 0 players are on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, which holds 100 slots. Its seven-day average is 1 players, and it reached 11 at the highest. Across the last 48 hours, the peak came at 22:00 UTC with an average of 2 players.

How does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly rank against other Rust servers?

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

Wipe days

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. Peak crowd on the latest wipe came 3 hours after it began. The crowd held above half that peak until the next wipe in 100% of recent wipes.

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 the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world now in play was generated 4 days 5 hours ago. The tags carry a wipe schedule of once every two weeks.

Settings

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

You will not find a gather rate in the name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. 8 players per group is the game's default, and that is the cap here. survival is the mode here, gather, build and raid: the standard game. You can fight other players and raid their bases. The server browser lists it under Community. The plugin count is Oxide. VAC is on: that is Valve's anti-cheat.

Which map does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run?

The game generates the procedural map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, size 4,000 with seed 1. This page links to RustMaps, where the map looks the same for its size and seed.

Connect

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

Type client.connect 91.124.63.81:28015 in the Rust console, which F1 opens. Launch Rust on this page also works: Steam opens Rust and connects you. You can 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 The game runs on standard Rust survival settings.
mp100
Max players The server has 100 slots.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build This one runs game build 168909.
ptrak
Networking The game's standard network layer, RakNet, carries this server.
$r?
Region code This server sets no region code.

Wipe schedule

^b
Biweekly Every two weeks brings a wipe.

Mods and access

^o
Oxide This server 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.