Rust Data

rustdata.spaceservers178.45.32.248:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 178.45.32.248:28015 checked 24d ago

gitler

Connect

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

Right now

srv.summary()
players now 1/5 # 20% full
7-day average 0 # peak –
rank #13,911 # top 61%
last wipe 24d ago # no schedule published
next wipe – # no wipe seen yet

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
15k10k15k20k3 Oct4 Oct6 Oct7 Oct9 Oct10 Oct

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

Wipe schedule

srv.wipe_schedule()

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · no wipe seen yet.

# 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
178.45.32.248:28015
region
–
max players
5
group limit
8, the default
wipe schedule
–
last wipe
3 Oct 2026, 17:53 UTC
hostname
–
first seen
3 Oct 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 · 520 on average389/425
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 336 on average22/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 333 on average45/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average180/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 279 on average69/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 263 on average77/100

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does gitler rank?

Rank #13,911 on seven-day player hours for gitler, within the top 61% of all ranked servers.

How many players does gitler hold at once?

The current row shows gitler offline; the last response was 24 days 2 hours ago.

Server data

What Rust version does gitler run?

The build is Rust network protocol 2634 and build 166652 on Windows, run by gitler. The protocol has to match before you can join, and Steam does the updating.

How reliable is gitler, and is it up?

gitler is offline at this refresh; the last response came 24 days 2 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 3 October 2026.

Which location does gitler run from?

No region is published by gitler. 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 178.45.32.248:28015.

Rules, settings, map

What rules and settings are recorded for gitler?

The name gitler carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

What is the map on gitler?

A procedural map runs on gitler, generated by the game.

Wipe data

When does gitler wipe, and on what schedule?

Too few wipes are on record for gitler to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 24 days 6 hours ago.

Tags and filters

Which lists on Rust Data hold gitler, and which filters?

On Rust Data, gitler appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on gitler?

Read by the game's server browser, the tags gitler publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): The server runs build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is 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 gitler?

The manual route: launch Rust, F1, then client.connect 178.45.32.248: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 mp5,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp5
Max players The server lists 5 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166652
Build The server runs build 166652.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is 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 51,358 players 11,704 servers online