Rust Data

rustdata.spaceservers98.97.33.196:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 98.97.33.196:28015 checked 8d ago

THOR

Connect

srv = rust.server("98.97.33.196:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/15 # 0% full
7-day average 0 # peak –
rank #15,351 # top 70%
last wipe 9d 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
15k10k15k20k20 Oct21 Oct23 Oct24 Oct26 Oct27 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
98.97.33.196:28015
region
–
max players
15
group limit
8, the default
wipe schedule
–
last wipe
19 Oct 2026, 01:19 UTC
hostname
–
first seen
19 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 · 560 on average237/275
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average157/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 292 on average27/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 291 on average14/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average31/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average43/200

Quick answers

From the figures on this page.

Population data

What position does THOR take in the server rankings?

Player hours over seven days put THOR at #15,351, in the top 70% of the ranked set.

How many players does THOR hold at once?

THOR returns no live count at this refresh, having last been seen 8 days 13 hours ago.

Server data

Which Rust version is THOR on?

Version Rust network protocol 2634 and build 167781 on Linux is reported by THOR. The protocol has to match before you can join, and Steam does the updating.

Is THOR up, and what does its uptime show?

The latest sample has THOR offline, with a last sighting 8 days 13 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 19 October 2026.

Which location does THOR run from?

No region is published by THOR. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 98.97.33.196:28015.

Settings and map

Which settings and rules does THOR run?

The name THOR carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat status: VAC on.

Which map has THOR loaded?

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

Wipe schedule

On what schedule does THOR wipe?

A rhythm cannot be read from the wipes of THOR on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 9 days 23 hours ago, and that is the one in play.

Tags and filters

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

On Rust Data, THOR appears in these lists: Rust community servers, unfiltered. It appears under these filters 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.

How should you read the server tags on THOR?

These tags are published by THOR and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp15 (Max players): Slot count: 15; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join THOR?

In Rust, F1 opens the console: type client.connect 98.97.33.196:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp15,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp15
Max players Slot count: 15.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167781
Build Build number: 167781.
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 45,884 players 11,696 servers online