The server's own banner, as it publishes it
Exhibit no. 3,077Acc. 2026.3077
[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
Rust server · in the archive since 20 October 2026
Online 91.124.63.81:28015 checked 12m ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
20 Oct Now 20 Oct17:30 23 Oct16:36 5 Nov19:00 · FW 6 Nov16:36 20 Nov16:36 3 Dec19:00 · FW 4 Dec16:36
a wipe on recordthe monthly force wipeexpectednow, 27 Oct 2026, 18:15 UTCAll times UTC.
The record of each wipe
-
Fri 23 Oct 202616:36 UTC4d ago
- Peak
- 11
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Tue 20 Oct 202617:30 UTC7d ago
- 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.
The rhythm
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 9d 0h. The force wipe · high confidence
Coming wipes
- 9d 0hThu 5 Nov, 19:00 UTCFW
- 9d 22hFri 6 Nov, 16:36 UTC
- 23d 22hFri 20 Nov, 16:36 UTC
- 37d 0hThu 3 Dec, 19:00 UTCFW
- 37d 22hFri 4 Dec, 16:36 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 11, 3 hours in.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 14% of all ranked servers. Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Tags, lists
What do the server tags on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly mean?
These tags from [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, read by the game's server browser, are: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code field is empty; ^b (Biweekly): The server wipes on a two-week cycle; ^o (Oxide): Oxide, also known as uMod, is the plugin framework in use. Shown at the top of this page are the current players, the queue and the world's age, also taken from the tags.
Which Rust Server History lists and filters include [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
These Rust Server History lists include [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: European Rust servers and Rust community servers. 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.
Server entry
Does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run smoothly?
33 server fps on average over the last 48 hours, never below 15. As many as 98,477 entities were in the world: buildings, deployables and the rest. The highest memory use was 3,863 MB. Players feel lag when fps drop and the entity count climbs.
Which version of Rust does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run?
The recorded build for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is Rust network protocol 2635 and build 168909 on Linux. Joining requires your game to be on the same protocol; Steam keeps it updated for you.
Is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly online, and how reliable is it?
At this moment [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is online. Going by its reported uptime, it restarted about 36 hours ago. It was up for 144 of 144 hours in the last 6 full days, 100% of the time. 20 October 2026 is when Rust Server History first saw it.
Where is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly located?
The name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly points to Europe, but no region tag is published. The location on Rust Server History is what a server says, not a lookup of where the machine stands. Its entry gives 91.124.63.81:28015 as the address.
Wipe log
What does wipe day look like on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
At their busiest, its recent wipes drew an average of 7 players. On the latest wipe, 3 hours after the wipe, the crowd peaked. Half that peak was held 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 because the record holds too few of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's wipes to confirm its schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 4 days 1 hours ago its current world was made. Its tags carry a wipe schedule of every two weeks.
Player record
How does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly rank against other Rust servers?
Over seven days of player hours, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly ranks #3,077, inside the top 14% of all ranked servers.
How busy is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
0 players are on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly at present, from 100 slots. A seven-day average of 1 players is recorded, with a peak of 11. An average of 6 players at 19:00 UTC made that the busiest hour of the last 48.
Map and rules
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. The limit of 8 players per group is the game's default. Under game mode, the entry reads survival, gathering, building and raiding: the standard game. Fighting and raiding between players are permitted. The server browser lists it under Community, as a community server. Plugins in use: Oxide. The anti-cheat VAC from Valve is active.
Which map does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run?
Generated by the game at size 4,000 with seed 1, the map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is procedural. From this page you can view the map on RustMaps: the same size and seed give the same map.
Join record
How do I join [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Press F1 in Rust to open the console, then enter client.connect 91.124.63.81:28015 to connect. Launch Rust from this page instead and you join through Steam with the connect already made. You will find its website at https://ekiphost.com.
The label explained
Server tags
What each tag this server publishes means.
Published as mp100,ptrak,$r?,v2635,^b,gmrust,cs168909,ts8,^o
Game
gmrust
mp100
ts8
v2635
cs168909
ptrak
$r?
Wipe schedule
^b
Mods and access
^o
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.