[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
91.124.63.81:28015 checked 11m ago
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 17% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 11d 14h. The force wipe · high confidence
- usual gap
- 3 days between real wipes
- wipe-day peak
- 3 players, last three wipes
- crowd held
- 100% of its cycles kept half the crowd
Coming wipes
- 11d 14hThu 5 Nov, 19:00 UTCFW
- 12d 12hFri 6 Nov, 16:36 UTC
- 26d 12hFri 20 Nov, 16:36 UTC
- 39d 14hThu 3 Dec, 19:00 UTCFW
- 40d 12hFri 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 3, 4 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 16:36 UTC 1d ago | – | – | running | 0 |
| Tue 20 Oct, 17:30 UTC 4d 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.
Similar servers
Quick answers
Population
How busy is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is holding 0 of its 100 slots at the moment. For the last seven days the mean was 1 players; the highest count was 11. Over the past 48 hours, the peak period was 20:00 UTC with an average of 10 players.
How does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly rank against other Rust servers?
For player hours in the last seven days, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly holds rank #3,782 and is in the top 17% of all ranked servers.
Wipe schedule
What does wipe day look like on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
The busiest points of its recent wipes drew 3 players on average. 4 hours after the latest wipe, the crowd peaks. Half that peak or more 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 schedule of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly cannot be confirmed from the wipes on record, which are too few, so the prediction follows its tag. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe that clears every Rust server. 35 hours ago the current world was made. The tags carry an every-two-weeks wipe schedule.
Server details
Is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly online, and how reliable is it?
Right now [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is up and online. It reports an uptime that puts the last restart at about 34 hours ago. In the last 4 full days, it was up for 96 of 96 hours, or 100% of the time. The earliest record When Is Wipe has is 20 October 2026.
Performance of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: does it run smoothly?
Over the past 48 hours, it averaged 44 server fps, with a minimum of 15. Buildings, deployables and other world objects pushed the entity count as high as 96,942. The peak memory usage was 3,349 MB. What players experience as lag comes from low fps and a rising entity count.
Which version of Rust does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run?
On [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, the Rust version is network protocol 2635 and build 168909 and the OS is Linux. Your game must match the protocol to connect, and Steam keeps it updated.
Where is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly located?
No region tag is published by [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, but its name points to Europe. When Is Wipe shows the location a server claims; it does not look up the machine's actual location. 91.124.63.81:28015 is its address.
Lists and tags
Which When Is Wipe lists include [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly? And filters?
These When Is Wipe lists include [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: EU Rust servers and Community Rust servers. It appears 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 3 days.
What do the server tags on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly mean?
The game's server browser reads the tags [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly publishes: gmrust (Game mode): This server runs standard Rust survival; mp100 (Max players): The server holds 100 players; ts8 (Group limit): Teams are capped at 8, as shipped by default; v2635 (Protocol): The server runs game protocol 2635; a version mismatch blocks joining; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The server has no region code; ^b (Biweekly): The schedule is a wipe each fortnight; ^o (Oxide): The plugin framework here is Oxide (uMod). The tags also hold its population now, its queue and when its world was made, all shown at the top of this page.
Map and rules
What rules does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly enforce? And settings?
No gather rate appears in [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's name. Under the default setting, groups are limited to 8 players. The game mode for this server is survival, standard survival: gathering, building, raiding. PvP and raiding are enabled. Listed under Community, it is a community server. Plugins: Oxide. The server has VAC, Valve's anti-cheat, on.
Which map does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run?
A procedural map, size 4,000 with seed 1, is used by [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly; the game generates it. With the same size and seed, the map is identical and can be seen on RustMaps from here.
Join
How do I join [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Press F1 in Rust and enter client.connect 91.124.63.81:28015 in the console. You can also use Launch Rust here, which opens Rust through Steam and connects you. You can find its website at https://ekiphost.com.
Server tags
Published as mp100,ptrak,$r?,v2635,^b,gmrust,cs168909,ts8,^o
Game
gmrust- Game mode This server runs standard Rust survival.
mp100- Max players The server holds 100 players.
ts8- Group limit Teams are capped at 8, as shipped by default.
v2635- Protocol The server runs game protocol 2635; a version mismatch blocks joining.
cs168909- Build Build 168909.
ptrak- Networking The network layer is RakNet, Rust's default.
$r?- Region code The server has no region code.
Wipe schedule
^b- Biweekly The schedule is a wipe each fortnight.
Mods and access
^o- Oxide The plugin framework here 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.