Station XX-3061 · recording
[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly
Online 91.124.63.81:28015 checked 7m ago
- Players now
- 1/ 100
- 1% full
- Motion · 24 h
- M0.4▲rising
- +3 players on the day
- 7-day average
- 1
- peak 11
- Rank
- #3,061
- top 14%
- Last wipe
- 5d ago
- biweekly schedule
- Next wipe
- 7d 21h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 100 slots
- Motion · 24 h
- M0.4▲rising+3 players
- Sharpest hour
- +2into Wed 17:00 UTC
- Peak · 48 h
- 3most players in any hour
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
daily · 1 is bestTop 14% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 21h. The force wipe · high confidence
- usual gap
- 3 daysbetween real wipes
- wipe-day peak
- 7players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
Coming wipes
- 7d 21hThu 5 Nov, 19:00 UTCFW
- 8d 19hFri 6 Nov, 16:36 UTC
- 22d 19hFri 20 Nov, 16:36 UTC
- 35d 21hThu 3 Dec, 19:00 UTCFW
- 36d 19hFri 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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 23 Oct, 16:36 UTC5d ago | M1.0▲rising | 11 | – | running | 0 | |
| Tue 20 Oct, 17:30 UTC8d ago | M0.5▲rising | 3 | held half | 3 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Generated by the game, the map on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is procedural, size 4,000 with seed 1. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
You will find no gather rate in the name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly right now?
A reading taken now shows 1 players on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, which has 100 slots. The seven-day average is 1 players, with a peak of 11. Averaged over the last 48 hours, the busiest hour was 17:00 UTC at 3 players.
How does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly rank against other Rust servers?
On player hours for the past week, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly sits at #3,061, which puts it inside the top 14% of every ranked server.
Server facts
How reliably does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly stay online?
[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is up at the moment. The uptime it reports puts its last restart about 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. On 20 October 2026 it was recorded for the first time by Rust Server Trends.
How well does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly perform under load?
The 48-hour average is 24 server fps; 15 is the lowest observed. At its highest, it carried 97,487 entities: buildings, deployables and the world's other contents. Memory use peaked at 3,760 MB. Low fps together with a growing entity count is what players experience as lag.
Where in the world is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly hosted?
Its name points to Europe, but [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly publishes no region tag. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 91.124.63.81:28015.
Which Rust version is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly running?
Rust network protocol 2635 and build 168909 on Linux is what [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
On average, the busiest point of its recent wipes drew 7 players. 3 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
On what timetable does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run its wipes?
The prediction is taken from its tag, since [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly has too few wipes on record to confirm the schedule. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 5 days 4 hours is how long the current world has been running. Its tags state that it wipes every two weeks.
Tags
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): Survival in standard Rust; mp100 (Max players): 100 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): Oxide (uMod) is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly appear?
You will find [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly on the following Rust Server Trends lists: EU Rust servers and Rust community servers without the side modes. On the server list, the filters it matches are: 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.
Connecting
What steps get you onto [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
To join, enter client.connect 91.124.63.81:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. https://ekiphost.com is where its website lives.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.