Online 91.124.63.81:28015 checked 7m ago
[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
Connect
srv = rust.server("91.124.63.81:28016")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 14% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 20h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 9d 18h | Fri 6 Nov, 16:36 UTC | wipe |
| 2 | 23d 18h | Fri 20 Nov, 16:36 UTC | wipe |
| 3 | 36d 20h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 37d 18h | Fri 4 Dec, 16:36 UTC | wipe |
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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 16:36 UTC4d ago | 11 | NaN | running | 0 |
| 1 | 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.
display(srv.map, srv.info())Map
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)
- map
- Procedural Map
- size
- 4000
- seed
- 1
Server
srv.info()- 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
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 280 on average | 125/200 |
| 1 | Rustafied.com - EU Medium - Large | EU · groups of 16+ · biweekly · 155 on average | 70/100 |
| 2 | Rusty Moose |EU Biweekly| | EU · groups of 12+ · biweekly · 39 on average | 24/200 |
| 3 | Rustoria.co - EU Medium | EU · groups of 12+ · biweekly · 27 on average | 12/200 |
| 4 | Rustopia.gg - EU Medium | EU · groups of 12+ · biweekly · 22 on average | 7/200 |
| 5 | РОССИЯ#2|КЛАССИКА|ДЛЯ НОВИЧКОВ16.10 | EU · groups of 8+ · biweekly · 22 on average | 9/200 |
Quick answers
From the figures on this page.
Player counts
How does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly compare in the rankings?
Rank #3,137 on seven-day player hours for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, within the top 14% of all ranked servers.
How many players does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly hold at once?
The sample now reads 0 players for [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, out of 100 slots. Over the last seven days it averaged 1 players and peaked at 11. Averaged by hour over 48 hours, 21:00 UTC is the busiest, at 2 players.
Server data
How well does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly perform?
Averaged over 48 hours: 29 server fps, never under 15. Entity numbers reached 98,477, and that includes buildings, deployables and the rest. Memory peaked at 3,863 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. The protocol has to match before you can join, and Steam does the updating.
How reliable is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, and is it up?
The current sample puts [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly online. Count back 40 hours from its reported uptime to get the last restart. 144 of 144 hours up over the last 6 full days, or 100%. Rust Data logged it first on 20 October 2026.
Which location does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run from?
No region tag is published by [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, though its name points to Europe. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 91.124.63.81:28015 is its address.
Rules, settings, map
Which rules apply on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, and what settings?
You will not find a gather rate in the string [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly selected?
Size 4,000, seed 1: the procedural map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly wipe, and how often?
The tag sets the prediction: [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly has too few wipes on record 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. A new world was started 4 days 5 hours ago, and that is the one in play. The tags list a two-weekly wipe cycle.
On [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, what happens on wipe day?
Recent wipes averaged 7 players at their peak. The crowd on the latest wipe topped out 3 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Lists and tags
Which lists on Rust Data hold [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, and which filters?
On Rust Data, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly appears in these lists: EU Rust servers and Rust community servers, unfiltered. 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.
How should you read the server tags on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
These tags are published by [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): The plugin framework in use is Oxide (uMod). Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
In Rust, F1 opens the console: type client.connect 91.124.63.81:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://ekiphost.com.