Statistical profileOnline
[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
91.124.63.81:28015 checked 11m ago
Connect to this server
1. Main points
Players now
0/ 100
0% full
7-day average
1
peak 11
Rank
#3,158
top 14%
Last wipe
4d ago
biweekly schedule
Next wipe
8d 19h
Thu 5 Nov, 19:00 UTC FW
Main points
- There were 0 players on it, 0% of its 100 slots.
- Over the last seven days it averaged 1 players, with a peak of 11.
- It ranks #3,158 of all ranked servers, the top 14%, on player hours over the last seven days.
- Its current map went up 4d ago; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
2. Players
Figure 1: Players on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 14% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternfrom its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 8d 19h. The force wipe · high confidence
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
Table 1: Coming wipes
Expected from its own rhythm and the force wipe
| In | Date and time | Kind |
|---|---|---|
| 8d 19h | Thu 5 Nov, 19:00 UTC | Force wipe FW |
| 9d 17h | Fri 6 Nov, 16:36 UTC | Own schedule |
| 23d 17h | Fri 20 Nov, 16:36 UTC | Own schedule |
| 36d 19h | Thu 3 Dec, 19:00 UTC | Force wipe FW |
| 37d 17h | Fri 4 Dec, 16:36 UTC | Own schedule |
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 11, 3 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 2: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 16:36 UTC4d ago | 11 | – | running | 0 |
| Tue 20 Oct, 17:30 UTC7d ago | 3 | held half | 3 days | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
4000 · seed 1
![Map of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly](https://files.facepunch.com/rust/map-images/bf46b286171c7d6b55b1c6c157d6f1b85e7d4f113dafe1b158976f6103755992/proceduralmap.4000.1792773330652.289_bf46b286171c7d6b55b1c6c157d6f1b8.jpg)
8. Server characteristics
Table 4: Characteristics of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
What the server publishes and what was recorded
| 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 |
9. About this server
In its own words: the description the server publishes, unedited.
⚔️ KOTARI RUST | TR/EU ⚔️ ━━━━━━━━━━━━━━━━━━ �� SOLO / DUO / TRIO �� �� Turkish & European Community �� MAX TEAM: 3 PLAYERS �� BIWEEKLY WIPE ⚔️ COMPETITIVE PvP �� BUILD • RAID • SURVIVE ━━━━━━━━━━━━━━━━━━ �� KOTARI RUST �� �� TRUST NO ONE. SURVIVE EVERYTHING. ━━━━━━━━━━━━━━━━━━ �� JOIN OUR DISCORD �� https://discord.gg/7pmxNRm4JV
10. Similar servers
Table 5: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 279 on average | 92 / 200 |
| Rustafied.com - EU Medium - Large | EU · groups of 16+ · biweekly · 154 on average | 56 / 100 |
| Rusty Moose |EU Biweekly| | EU · groups of 12+ · biweekly · 38 on average | 21 / 200 |
| Rustoria.co - EU Medium | EU · groups of 12+ · biweekly · 27 on average | 8 / 200 |
| РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10 | EU · groups of 8+ · biweekly · 22 on average | 6 / 200 |
| Rustopia.gg - EU Medium | EU · groups of 12+ · biweekly · 22 on average | 7 / 200 |
11. Quick answers
From the figures on this page.
Wipe schedule
On what schedule are wipes carried out on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Too few wipes of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly are recorded to confirm its schedule, so its tag is followed by the prediction. On Thursday 5 November at 19:00 UTC the next wipe falls, as a force wipe takes every Rust server. This world was generated 4 days 6 hours ago. The tags list a fortnightly wipe schedule.
What should you expect on wipe day at [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
The average busiest point of its recent wipes drew 7 players. On the latest wipe, 3 hours passed before the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe in 100% of cases.
About the server
What does the record show for the uptime and current status of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
This release records [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly as online. About 41 hours ago is when it last restarted, according to the uptime it reports. A total of 144 of 144 hours were up over 6 full days, which is 100% of the time. The first sighting of it by Rust Census was on 20 October 2026.
What does the performance record of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly show?
Over the last 48 hours, server fps averaged 28; the lowest reading was 15. Buildings, deployables and everything else in the world took the entity count to 98,477. Memory use reached 3,863 MB at its peak. Players feel low fps and a rising entity count as lag.
Which location does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run from?
Pointing to Europe is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's name, though no region tag is published. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. At 91.124.63.81:28015 it is addressed.
On which Rust version does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly operate?
Rust network protocol 2635 and build 168909 on Linux is the version [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly runs. Steam updates your game for you, but it has to be on the same protocol to join.
Player figures
What population has been recorded on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
At counting time [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly recorded 0 players across 100 slots. Averaged over seven days: 1 players, with a peak of 11. The busiest hour in the last 48 hours was 21:00 UTC, with an average of 2 players.
In the rankings of Rust servers, where is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly placed?
For seven-day player hours, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is ranked #3,158, placing it in the top 14% of all ranked servers.
Tag details
Where does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly appear among the Rust Census lists and filters?
Included in these Rust Census lists is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: EU Rust servers: the regional count and Community servers. These filters 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.
What is meant by each tag shown on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
These are the tags [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly publishes for the game's server browser to read: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): Build 168909 is installed; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): This server carries no region code; ^b (Biweekly): The wipe interval is two weeks; ^o (Oxide): The plugin framework in use is Oxide (uMod). Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Map and rules
What map is listed for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Size 4,000 and seed 1: that is the procedural map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, generated by the game. The same size and seed produce the same map; RustMaps shows it from this page.
How is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly configured, and what rules does it keep?
No gather rate is recorded for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly in its name. The group cap stands at 8 players, the default for the game. survival is the game mode recorded, the standard game: gather, build, raid. Combat between players and raiding are both permitted. The server browser lists it under Community. Plugins on it number Oxide. Anti-cheat is active: VAC, Valve's system, is on.
How to join
What steps are needed to join [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
You can open the console in Rust with F1 and enter client.connect 91.124.63.81:28015; or press Launch Rust and join on this page, and you are connected through Steam. The website recorded for it is https://ekiphost.com.
12. Server tags
What each tag this server publishes means: a glossary.
Published asmp100,ptrak,$r?,v2635,^b,gmrust,cs168909,ts8,^o
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp100 | Max players The server holds 100 slots. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs168909 | Build Build 168909 is installed. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code This server carries no region code. |
Wipe schedule
^b | Biweekly The wipe interval is two weeks. |
|---|
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.