On the class lists: B (77), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average1peak 11
Rank#3,137top 14%
Last wipe4d agobiweekly schedule
Next wipe8d 20hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
86/ 100
A−
Holds a respectable place: #3,137 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
49/ 100
D
Needs to work on its frame rate: 29 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
100/ 100
A+
Climbing fast: up 5,057 places this week.
A steady term.
Strongest in wipe hold (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 14% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W··W··
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 8d 20h.
The force wipe · high confidence
usual gap3 daysbetween real wipes
wipe-day peak7players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
8d 20hThu 5 Nov, 19:00 UTCFW
9d 18hFri 6 Nov, 16:36 UTC
23d 18hFri 20 Nov, 16:36 UTC
36d 20hThu 3 Dec, 19:00 UTCFW
37d 18hFri 4 Dec, 16:36 UTC
The first 48 hours of its last wipes
Fri 23 OctTue 20 Oct
Players each hour, from the hour of the wipe. The latest peaked at 11, 3 hours in.
Wipes
newest first
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
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
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
You won't find a region tag on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, but its name indicates Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 91.124.63.81:28015 is the address to use.
How reliable is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly, and is it up?
Right now, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is online. About 40 hours ago, it restarted, based on the uptime it reports. For the last 6 full days, it was up 144 of 144 hours, or 100% of the time. The first sighting by Rust Server Score was on 20 October 2026.
How well does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly run?
It never fell below 15 server fps in the last 48 hours, averaging 29. Up to 98,477 entities were in the world, covering buildings, deployables and the rest. Up to 3,863 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly on?
Rust network protocol 2635 and build 168909 on Linux is what [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly wipe, and how often?
Too few wipes on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly are recorded to confirm the schedule, so its tag guides the prediction. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 4 days 5 hours. A fortnightly wipe schedule appears in its tags.
What should you expect from wipe day on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
The average peak on its recent wipes was 7 players. The crowd on the latest wipe was largest 3 hours after it began. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Player numbers
Where does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly place in the wider field of Rust servers?
Over the last seven days, [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly has #3,137 for player hours, in the top 14% of all ranked servers.
How many players does [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly usually have?
[TR/EU] KOTARI | Solo/Duo/Trio | Biweekly is showing 0 players right now, with 100 slots in total. It peaked at 11 and averaged 1 players over the last seven days. Over the last 48 hours, the peak hour was 21:00 UTC, averaging 2 players.
Lists and filters
What do [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly's tags stand for?
The game's browser takes its cue from the tags [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly has set: gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^o (Oxide): Plugin framework: Oxide (uMod). Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Rust Server Score lists that include [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly: European Rust servers, graded and Best community servers, graded. You can find it under these server-list filters: 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.
Rules and settings
What settings and rules apply on [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
Nothing in the name of [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly uses?
A procedural map of size 4,000 and seed 1, generated by the game, is what [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto [TR/EU] KOTARI | Solo/Duo/Trio | Biweekly?
To connect, start Rust, press F1, and type client.connect 91.124.63.81:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://ekiphost.com.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^b,gmrust,cs168909,ts8,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Mods and access
^o
OxidePlugin framework: 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.
A steady term. Strongest in wipe hold (A+); population is the one to work on (F).