[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 13m ago · 91.124.63.81:28015
Abstract
We describe the public Rust server [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, reached at 91.124.63.81:28015. At the last check it held 0 of 100 places, against a seven-day mean of 1 and a peak of 111. It ranks #3,158 of all servers, the top 14%. It last wiped 4d ago on a published biweekly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
Keywordsbiweekly wipes oxide
1Summary statistics

2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 14% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: from its schedule tag
The next wipe is expected Thursday 5 November, 19:00 UTC, in 8d 14h. The force wipe (high confidence).
| Measure | Value | Note |
|---|---|---|
| Usual gap | 3 days | between real wipes |
| Wipe-day peak | 7 | players, last three wipes |
| Crowd held | 100% | of its cycles kept half the crowd |
| When (UTC) | In | Kind |
|---|---|---|
| Thu 5 Nov, 19:00 | 8d 14h | force wipefw |
| Fri 6 Nov, 16:36 | 9d 11h | its own schedule |
| Fri 20 Nov, 16:36 | 23d 11h | its own schedule |
| Thu 3 Dec, 19:00 | 36d 14h | force wipefw |
| Fri 4 Dec, 16:36 | 37d 11h | its own schedule |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Fri 23 Oct, 16:364d ago | 11 | – | running | 0 |
| Tue 20 Oct, 17:307d ago | 3 | held half | 3 d | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 91.124.63.81:28015 |
|---|---|
| Region | – |
| Max players | 100 |
| Group limit | 8, the default |
| Wipe schedule | biweekly |
| Last wipe | 23 Oct 2026, 16:36 UTC |
| Hostname | – |
| First seen | 20 Oct 2026 |
| Map | Procedural Map |
| Size | 4000 |
| Seed | 1 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are rust servers in europe [2], community tab servers measured [3] and next Rust wipe times [4].
| Server | Players |
|---|---|
| Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 278 on average | 41/200 |
| Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 152 on average | 14/100 |
| Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 37 on average | 7/200 |
| Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 26 on average | 7/200 |
| РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10EU · groups of 8+ · biweekly · 21 on average | 3/200 |
| Rustopia.gg - EU MediumEU · groups of 12+ · biweekly · 20 on average | 2/200 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1Is the performance of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly smooth?
Its average server fps over the last 48 hours was 29, with a minimum of 15. The highest number of entities it carried was 98,333, comprising buildings, deployables and all other objects. Its highest memory usage was 3,488 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.
A.2What location does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly have?
No region tag is published by [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, but its name points to Europe. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 91.124.63.81:28015 is its address.
A.3What is the online status and reliability of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is currently online. It last restarted around 46 hours ago, according to its reported uptime. Of the 168 hours in the last 7 full days, 168 were served, an availability of 100%. The first record of it by Rust Statistics dates to 20 October 2026.
A.4What version of Rust is run on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Rust network protocol 2635 and build 168909 is the version that [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly runs, on Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe schedule
A.5When are wipes carried out on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
The record of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's wipes is too sparse to confirm the schedule, so the prediction is based on its tag. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC; this server's next wipe is then. The world currently in use was created 4 days 12 hours ago. The server's tags give a wipe schedule of every two weeks.
A.6What happens on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly when wipe day arrives?
Recent wipes saw an average peak of 7 players. The peak on the latest wipe came 3 hours after it began. Half the peak was sustained until the next wipe in 100% of recent wipes.
Player count
A.7What is the rank of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly among Rust servers?
Ranked by player hours across seven days, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly holds #3,158, in the top 14% of all ranked servers.
A.8What is the population level of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
At this moment 0 players are on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, which has 100 slots in total. Averaged over the last seven days: 1 players; the same period peaks at 11. Averaging 2 players, 21:00 UTC was the busiest hour of the past 48.
Tags and filters
A.9What is the meaning of the tags on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Tags from [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): It offers 100 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^b (Biweekly): Every two weeks the server wipes; ^o (Oxide): The plugin framework in use is Oxide (uMod). The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.10Where can [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly be found among the Rust Statistics lists and filters?
The Rust Statistics lists that [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly fits are: European Rust servers and Rust community servers, measured. These filters on the server list return it: 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.
Settings and map
A.11Under what rules and settings does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly operate?
The name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly states no gather rate. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gather, build and raid: the standard game. Combat and raiding against other players are allowed. It is a community server, as the browser's Community listing shows. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
A.12On which map does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly take place?
The game generates [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's procedural map at size 4,000, from seed 1. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.
Connection
A.13What is the process for joining [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Press F1 inside Rust to open the console and enter client.connect 91.124.63.81:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection. Its website can be found at https://ekiphost.com.
Appendix BServer tags
What each of the server's tags means. Published as mp100,ptrak,$r?,v2635,^b,gmrust,cs168909,ts8,^o.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp100 | Max players. It offers 100 slots. |
ts8 | Group limit. Teams are limited to 8, as the game defaults. |
v2635 | Protocol. Joining requires the same game version: protocol 2635. |
cs168909 | Build. The game build is 168909. |
ptrak | Networking. Networking runs on RakNet, the game's standard layer. |
$r? | Region code. The region code is unset. |
| Wipe schedule | |
^b | Biweekly. Every two weeks the server wipes. |
| Mods and access | |
^o | Oxide. The plugin framework in use is 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.
Appendix CAbout this server, in its own words
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Rust servers in europe. ruststatistics.org/top-eu-rust-servers.
- [3]Rust Statistics. Community tab servers measured. ruststatistics.org/top-rust-community-servers.
- [4]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.