Rust Data

rustdata.spaceservers91.196.55.117:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 91.196.55.117:28015 checked 26d ago

MaxTime

Connect

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

Right now

srv.summary()
players now 0/500 # 0% full
7-day average 0 # peak –
rank #15,905 # top 70%
last wipe 26d 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 70% 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
91.196.55.117:28015
region
–
max players
500
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 11:04 UTC
hostname
–
first seen
2 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 · 565 on average196/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average119/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average23/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 289 on average11/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average23/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average28/225

Quick answers

From the figures on this page.

Population

How does MaxTime compare in the rankings?

Over the last seven days MaxTime sits at #15,905 on player hours, in the top 70% of ranked servers.

What population does MaxTime carry?

The current row shows MaxTime offline; the last response was 26 days 14 hours ago.

About the server

Which Rust version is MaxTime on?

Rust network protocol 2634 and build 166586 on Windows is what MaxTime runs. Steam updates your game for you, but the protocol must match to join.

Is MaxTime up, and what does its uptime show?

Offline now for MaxTime, last seen 26 days 14 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 2 October 2026.

Which location does MaxTime run from?

For MaxTime, no region is published. 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 91.196.55.117:28015.

Rules, settings, map

Which settings and rules does MaxTime run?

The name MaxTime carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has MaxTime loaded?

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

Wipes and dates

When does MaxTime wipe, and on what schedule?

The record for MaxTime holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 26 days 14 hours ago.

Lists and tags

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

These Rust Data lists include MaxTime: 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.

How should you read the server tags on MaxTime?

Read by the game's server browser, the tags MaxTime publishes are: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): 500 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $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.

Connecting

What is the way into MaxTime?

Enter client.connect 91.196.55.117:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp500
Max players 500 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166586
Build Recorded game build: 166586.
ptrak
Networking The network layer is RakNet, standard for the game.
$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 41,069 players 11,703 servers online