Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO F SRV11,615online PAX40,773playing OCC3,012with players WIPED 3H86
COMCommunity traffic
Callsign

KTR3162=

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

Online 91.124.63.81:28015 checked 13m ago

biweekly wipes oxide
Clearance · join
Players now 0/ 100 0% full
7-day average1peak 11
Rank#3,162top 14%
Last wipe4d agobiweekly schedule
Next wipe8d 11hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeak
00.511.5208:0017:0002:0012:0021:0006:00

Hourly average and peak, UTC.

Server performance

02040608008:0017:0002:0012:0021:0006: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.

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 8d 11h.

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

Nearby traffic

Similar servers

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

  1. 01COM
    Callsign RST015EU · groups of 12+ · biweekly · 277 on average Rustoria.co - EU East Medium
    Players 92/225
  2. 02COM
    Callsign RST018EU · groups of 16+ · biweekly · 152 on average Rustafied.com - EU Medium - Large
    Players 20/100
  3. 03COM
    Callsign RST015EU · groups of 12+ · biweekly · 37 on average Rusty Moose |EU Biweekly|
    Players 12/200
  4. 04COM
    Callsign RST015EU · groups of 12+ · biweekly · 26 on average Rustoria.co - EU Medium
    Players 5/200
  5. 05COM
    Callsign SRV210EU · groups of 8+ · biweekly · 21 on average РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10
    Players 7/200
  6. 06COM
    Callsign RST010EU · groups of 12+ · biweekly · 20 on average Rustopia.gg - EU Medium
    Players 3/200
ATIS · this server

Quick answers

From the figures on this page.

Tags

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

On Rust Tracker, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly sits in these lists: EU Rust servers, tracked live and Community servers, no tags. On the server list, these filters 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.

What do the tags mean that [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is listed under?

These tags are published by [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly for the game's server browser to read: gmrust (Game mode): Standard survival mode for Rust; mp100 (Max players): Capacity: 100 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): The region code is unset; ^b (Biweekly): Two-week wipe cycle; ^o (Oxide): A plugin framework runs here: Oxide (uMod). Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

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

At their busiest, recent wipes averaged 7 players. The peak on the latest wipe came 3 hours after it. The crowd stayed above half the peak until the next wipe in 100% of recent wipes.

Which wipe times are confirmed for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

The prediction for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly follows its tag, as too few wipes are on record to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. This world has been running 4 days 14 hours. A two-weekly wipe schedule is published in its tags.

Location and Status

What is the uptime on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, and is it online?

Right now [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is online. The uptime it reports puts the last restart about 1 hours ago. Uptime stood at 100% for the last 7 full days, 168 of 168 hours online. First contact for Rust Tracker: 20 October 2026.

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

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

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

For the last 48 hours it averaged 29 server fps; the floor was 15. Buildings, deployables and the rest of the world took it to a maximum of 98,333 entities. Memory peaked at 3,760 MB. Lag, as players experience it, comes from low fps and a rising entity count.

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

No region tag from [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, but the name points to Europe. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 91.124.63.81:28015.

Player Count

How many players are on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly right now?

Tracking [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: 0 of 100 slots filled. Peak of 11 in the last seven days, average 1 players. Busiest window in 48 hours: 21:00 UTC, 2 players on average.

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

Seven-day player hours put [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly at #3,162, within the top 14% of all ranked servers.

Settings

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

Nothing in [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's name states a gather rate. Up to 8 players per group, the game's default. It runs survival, gather, build and raid: the standard game. Raiding and PvP are permitted between players. The server browser lists it under Community, as a community server. Oxide plugins run on it. VAC is on, Valve's anti-cheat.

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

The map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is procedural, size 4,000, seed 1, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map.

How to Join

What is the way to join [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?

To connect: start Rust, press F1, enter client.connect 91.124.63.81:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://ekiphost.com.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp100
Max players Capacity: 100 slots.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code The region code is unset.

Wipe schedule

^b
Biweekly Two-week wipe cycle.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).

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.