Rust Data

rustdata.spaceservers180.144.66.116:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 180.144.66.116:28015 checked 39d ago

TestServer

Connect

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

Right now

srv.summary()
players now 1/1 # 100% full
7-day average 0 # peak –
rank #13,272 # no region published
last wipe 56d 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 Sep21 Sep23 Sep24 Sep26 Sep27 Sep

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
180.144.66.116:28015
region
–
max players
1
group limit
8, the default
wipe schedule
–
last wipe
3 Sep 2026, 23:04 UTC
hostname
–
first seen
20 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 · 491 on average84/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average115/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 284 on average397/450
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average21/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average476/525
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average362/425

Quick answers

From the figures on this page.

Population data

How does TestServer compare in the rankings?

Rank #13,272 on seven-day player hours for TestServer, within the top – of all ranked servers.

How full does TestServer run?

TestServer returns no live count at this refresh, having last been seen 39 days 12 hours ago.

Server data

Which Rust version is TestServer on?

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

How reliable is TestServer, and is it up?

Offline now for TestServer, last seen 39 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 20 September 2026.

Where does TestServer sit?

There is no region published for TestServer. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 180.144.66.116:28015 is its address.

Rules, settings, map

What rules and settings are recorded for TestServer?

No gather rate appears in the name: TestServer. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

What is the map on TestServer?

TestServer runs a procedural map, which the game generates.

Wipe schedule

On what schedule does TestServer wipe?

The record for TestServer holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 56 days 2 hours ago.

Tags and filters

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

The Rust Data lists that TestServer fits are: 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.

Which meanings do the tags on TestServer hold?

These tags are published by TestServer and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs162929 (Build): Build number: 162929; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way into TestServer?

The manual route: launch Rust, F1, then client.connect 180.144.66.116: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 mp1,ptrak,$r?,v2633,gmrust,cs162929,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp1
Max players Slot count: 1.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol The server speaks protocol 2633, so match your game version.
cs162929
Build Build number: 162929.
ptrak
Networking Standard network layer for Rust: RakNet.
$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 60,014 players 11,706 servers online