Rust Server TrendsSeismic network · station log
Recording Stations11,735 Players53,534 Active3,365 Wipes · 3 h127 48 h

Station XX-15418 · no signal

kogita

Offline 178.206.189.183:28015 checked 27d ago

Connect
Players now
1/ 5
20% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,418
top 65%
Last wipe
27d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15418 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 5 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

Top 65% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 10:28 UTC27d ago M0.0rising 1 – – running 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 553 on average
324/ 375
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
217/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 294 on average
35/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 293 on average
31/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 273 on average
57/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 252 on average
73/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on kogita?

kogita uses a procedural map, which the game generates.

Which settings and rules apply on kogita?

The name of kogita gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. It is a community server, and the browser lists it under Community. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on kogita right now?

kogita is not responding at this moment and is offline, last seen 27 days 12 hours ago.

How does kogita rank against other Rust servers?

On player hours for the past week, kogita sits at #15,418, which puts it inside the top 65% of every ranked server.

Operator and location

How reliably does kogita stay online?

As recorded now, kogita is not reachable, the last contact having been 27 days 12 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 1 October 2026 is when Rust Server Trends first recorded it.

Where in the world is kogita hosted?

Nothing about a region comes from kogita. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 178.206.189.183:28015.

What build of Rust does kogita use?

Rust network protocol 2633 and build 165217 on Windows is what kogita runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on kogita?

1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.

How often does kogita wipe, and on which days?

On record so far are too few of kogita's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 27 days 13 hours.

Lists and tags

What do the server tags on kogita mean?

These are the tags kogita publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp5 (Max players): The server has 5 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does kogita appear?

You will find kogita on the following Rust Server Trends lists: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

What steps get you onto kogita?

To join, enter client.connect 178.206.189.183: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.

Instrument codes

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp5
Max players The server has 5 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build The game build is 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

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.

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.