Rust Data

rustdata.spaceservers46.61.245.181:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 46.61.245.181:28015 checked 11d ago

Koti 2

Connect

srv = rust.server("46.61.245.181:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 1/2 # 50% full
7-day average 0 # peak –
rank #12,922 # top 60%
last wipe 11d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k21 Sep27 Sep4 Oct10 Oct17 Oct23 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.8 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 16 OctThu 15 OctWed 14 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 10:00 UTC11d ago 1 NaN running 1
1 Thu 15 Oct, 15:26 UTC12d ago 1 NaN 0.8 days 1
2 Wed 14 Oct, 18:37 UTC13d ago 1 NaN 0.9 days 0
3 Fri 2 Oct, 14:48 UTC25d ago 2 held half 12.2 days 1
4 Thu 1 Oct, 19:32 UTC FW26d ago 2 NaN 0.8 days 2

# 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
46.61.245.181:28015
region
–
max players
2
group limit
8, the default
wipe schedule
–
last wipe
16 Oct 2026, 10:00 UTC
hostname
–
first seen
21 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 536 on average454/475
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average259/225
2Rustoria.co - EU MainEU · groups of 16+ · weekly · 318 on average27/250
3Rusty Moose |EU Main|EU · groups of 12+ · weekly · 317 on average33/250
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 276 on average140/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average53/100

Quick answers

From the figures on this page.

Player counts

What position does Koti 2 take in the server rankings?

Player hours over seven days put Koti 2 at #12,922, in the top 60% of the ranked set.

How full does Koti 2 run?

Koti 2 returns no live count at this refresh, having last been seen 11 days 13 hours ago.

About the server

Which Rust version is Koti 2 on?

The build is Rust network protocol 2634 and build 166586 on Windows, run by Koti 2. Joining needs the same protocol on your game; Steam handles the update.

Is Koti 2 up, and what does its uptime show?

Offline now for Koti 2, last seen 11 days 13 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 21 September 2026.

Where does Koti 2 sit?

No region is published by Koti 2. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 46.61.245.181:28015.

Settings and map

Which settings and rules does Koti 2 run?

You will not find a gather rate in the string Koti 2. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has Koti 2 loaded?

The game generates its map: procedural, on Koti 2.

Wipes and dates

When does Koti 2 wipe, and on what schedule?

No next wipe can be predicted for Koti 2, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 11 days 22 hours ago.

What is wipe day on Koti 2 like?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 2 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Lists and tags

Where does Koti 2 appear among Rust Data lists and filters?

These Rust Data lists include Koti 2: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on Koti 2 hold?

The game's server browser reads these tags from Koti 2: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): Build number: 166586; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way to join Koti 2?

The manual route: launch Rust, F1, then client.connect 46.61.245.181:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp2,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp2
Max players The server lists 2 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs166586
Build Build number: 166586.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

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.

Rust Data 46,883 players 11,635 servers online