Rust PopulationField survey · Rust servers
Observing 67,584 players 11,791 servers 3,634 with someone on 129 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 3,053habitat unknownfirst seen 20 Oct 2026

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

Online 91.124.63.81:28015 checked 8m ago

biweekly wipes oxide

Measurements

Players now
0/ 100
0% full
7-day average
1
peak 11
Rank
#3,053
top 14%
Last wipe
5d ago
biweekly schedule
Next wipe
7d 21h
Thu 5 Nov, 19:00 UTC FW
Obs. 1 · sightings

Players

AveragePeak
0123422:0007:0016:0001:0010:0020:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

02040608022:0007:0016:0001:0010: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.

Obs. 3 · standing

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.

Obs. 4 · the wipe cycle

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h. The force wipe · high confidence

3 days
usual gap
between real wipes
7
wipe-day peak
players, last three wipes
100%
crowd held
of its cycles kept half the crowd

Coming wipes

7d 21h
Thu 5 Nov, 19:00 UTC
FW
8d 18h
Fri 6 Nov, 16:36 UTC
22d 18h
Fri 20 Nov, 16:36 UTC
35d 21h
Thu 3 Dec, 19:00 UTC
FW
36d 18h
Fri 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.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 16:36 UTC5d ago 11 – running 0
Tue 20 Oct, 17:30 UTC8d 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.

Field questions

Quick answers

from the figures on this page

Player counts

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

By player hours over the last seven days, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly places at #3,053, within the top 14% of ranked servers.

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

Of its 100 slots, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is using 0 right now. We counted an average of 1 players in the past week, with 11 at the busiest. In the last 48 hours the peak hour came at 17:00 UTC, averaging 3 players.

Tags

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, as read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): You can join up to 100 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): Your game needs the same version, protocol 2635, to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): The server wipes on a two-week cycle; ^o (Oxide): A plugin framework, Oxide (uMod), is in use. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

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

These Rust Population lists include [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: Rust servers in Europe and Community servers, field-listed. Look for it under these filters 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.

Wipe notes

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

Across its recent wipes the busiest crowds averaged 7 players. Peak came 3 hours into the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

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

The prediction follows its tag, since too few of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's wipes are on record to confirm the schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Counted from 5 days 5 hours ago, that is how long the current world has stood. A wipe every two weeks is what the tags publish.

Map and rules

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

The map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is procedural, made by the game at size 4,000 from seed 1. You can look at it on RustMaps from this page: size and seed determine the map.

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

No gather rate appears in the name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. No limit is set beyond the standard 8 players per group. survival is what it runs, gather, build and raid, as in the standard game. You can raid and fight other players here. You will find it under Community: it is a community server. Oxide plugins are in use here. You play with Valve's anti-cheat on: VAC.

About the server

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. The protocol must match for you to join, and Steam updates it for you.

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

It ran at 25 server fps on average over the last 48 hours, and never went below 15. The entity count reached 97,487: buildings, deployables and all other objects. The highest memory usage was 3,760 MB. What players experience as lag comes from low fps and a rising entity count.

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

[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is up and running at the moment. The uptime it reports suggests a restart roughly 15 hours ago. Over the last 7 full days, 168 of 168 hours were online, or 100%. The first sighting by Rust Population was on 20 October 2026.

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

Nothing in the tags says where [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is, but its name points to Europe. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. You will find it at 91.124.63.81:28015.

Getting in

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

To connect directly, open Rust's console with F1 and type client.connect 91.124.63.81:28015; or press Launch Rust on this page and Steam opens Rust and joins for you. You can find its website at https://ekiphost.com.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players You can join up to 100 slots.
ts8
Group limit This is the game default: at most 8 per team.
v2635
Protocol Your game needs the same version, protocol 2635, to join.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer here, as standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly The server wipes on a two-week cycle.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), is in use.

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.