Skip to the page
Network live 11,721 servers online 48,587 players aboard 110 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

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

Online 91.124.63.81:28015 checked 8m ago

biweekly wipes oxide
Tracking number · connect
Launch Rust and join Website
Wipe progress · wiped 5d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Thu 5 Nov, 19:00 UK Thu 5 Nov, 19:00 UTC FW in 7d 18h · high confidence
1/ 100 players now 1% full
17-day averagepeak 11
#3,050ranktop 14%
5d agolast wipebiweekly schedule
7d 18hnext wipeThu 5 Nov, 19:00 UTC FW
Delivery history

Players, performance and rank

Players

AveragePeak
0123401:0010:0019:0003:0012:0022:00

Hourly average and peak, UTC.

Server performance

02040608001:0010:0019:0003:0012:0022: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 delivery expected

Next wipe Thursday 5 November, 19:00 UTC · 19:00 UK, in 7d 18h.

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

  1. 7d 18hThu 5 Nov, 19:00 UTC19:00 UKFW
  2. 8d 16hFri 6 Nov, 16:36 UTC16:36 UK
  3. 22d 16hFri 20 Nov, 16:36 UTC16:36 UK
  4. 35d 18hThu 3 Dec, 19:00 UTC19:00 UKFW
  5. 36d 16hFri 4 Dec, 16:36 UTC16:36 UK

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

every wipe as a delivery, newest first
  1. Thu 5 Nov, 19:00 UTC FW19:00 UK · in 7d 18h
    Next wipe expected · the force wipe
  2. Fri 23 Oct, 16:36 UTC 17:36 UK · 5d ago
    Wipe delivered
    Peak
    11
    Crowd
    –
    Lasted
    running
    Players before
    0
  3. Tue 20 Oct, 17:30 UTC 18:30 UK · 8d ago
    Wipe delivered
    Peak
    3
    Crowd
    held half
    Lasted
    3 days
    Players before
    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 parcels

Similar servers

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

  1. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average 53 / 200
  2. Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 131 on average 24 / 100
  3. Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 30 on average 16 / 200
  4. Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 25 on average 20 / 200
  5. Владивосток | ДЛЯ НОВИЧКОВ | INSOMNISEU · groups of 30+ · biweekly · 17 on average 4 / 150
  6. РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10EU · groups of 8+ · biweekly · 17 on average 5 / 200
Help desk

Quick answers

From the figures on this page.

Player count

What is the ranking of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly against other Rust servers?

In the top 14% of all ranked servers sits [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, at #3,050 on hours played over seven days.

Is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly busy at the moment?

Checking now: 1 players on 100 slots at [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. The seven-day figures show an average of 1 players and a peak of 11. The busiest hour over the last 48 hours was 17:00 UTC, averaging 3 players.

Server rules

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

Size 4,000 and seed 1 define the procedural map [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly runs, generated by the game. Size and seed match means the map matches, so you can view it on RustMaps from this page.

Which 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. The game's default applies: 8 players to a group at most. You get survival here, gather, build and raid, as the standard game goes. Fighting and raiding between players is allowed. The server browser files it under Community, as a community server. Plugins come from Oxide. VAC, Valve's anti-cheat, is switched on.

About the server

In which region is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly based?

No region tag comes from [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, but the name points to Europe. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. The address to connect to is 91.124.63.81:28015.

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

The 48-hour average for server fps stands at 24, never dipping below 15. The world held as many as 97,487 entities: buildings, deployables and the rest. 3,760 MB of memory was its top figure. What players call lag is the mix of low fps and an entity count that keeps climbing.

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

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is up and online at the moment. Its reported uptime suggests a restart roughly 17 hours ago. It was up 144 of 168 hours over the last 7 full days, 86% of the time. 20 October 2026 is when Rust Wipe Tracker first recorded it.

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

The version on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is Rust network protocol 2635 and build 168909, running on Linux. To join, your game must be on the same protocol; Steam handles that update for you.

Wipe times

What happens on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly when wipe day arrives?

At their busiest, its recent wipes drew an average of 7 players. 3 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

How often does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly wipe, and at what times?

The prediction is taken from its tag, as [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly has too few wipes on record to confirm the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next one. 5 days 7 hours have passed since this world was made. In its tags it posts a wipe every two weeks.

Tags and listings

Where does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly appear in Rust Wipe Tracker lists and filters?

You will find [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly on the following Rust Wipe Tracker lists: Rust servers in Europe and Rust community servers, unmodded. These are the filters that 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.

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

The game's server browser picks up these [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly tags: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): The server has 100 slots; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): It wipes on a two-week cycle; ^o (Oxide): It uses Oxide (uMod) for plugins. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

How to join

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

Enter client.connect 91.124.63.81:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you. You will 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 Survival in standard Rust.
mp100
Max players The server has 100 slots.
ts8
Group limit 8 per team, which is the default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet handles networking, as standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly It wipes on a two-week cycle.

Mods and access

^o
Oxide It uses 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.