Rust Data

rustdata.spaceservers1.161.216.47:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 1.161.216.47:28015 checked 13d ago

LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP

Connect

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

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,119 # top 70%
last wipe 13d ago # no schedule published
next wipe – # too few wipes 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, measured since 16 Oct. 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
15k10k15k20k16 Oct17 Oct19 Oct20 Oct22 Oct23 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 04:56 UTC13d ago 1 NaN running 0

# 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

3500 · seed 123456
Map of LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP
map
Procedural Map
size
3500
seed
123456
Open on RustMaps

Server

srv.info()
address
1.161.216.47:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
16 Oct 2026, 04:29 UTC
hostname
–
first seen
16 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rustoria.co - SEA MainEA · groups of 16+ · weekly · 181 on average436/450
1Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.comEA · groups of 16+ · weekly · 119 on average19/550
2Rustoria.co - SEA LongEA · groups of 12+ · monthly · 105 on average81/200
3Rustafied.com - SEA MainEA · groups of 16+ · weekly · 85 on average227/450
4Rustoria.co - SEA Medium | JUST WIPED 29.10EA · no group limit · 65 on average57/100
5Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]EA · groups of 8+ · weekly · 53 on average17/200

Quick answers

From the figures on this page.

Player counts

What position does LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP take in the server rankings?

Over the last seven days LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP sits at #15,119 on player hours, in the top 70% of ranked servers.

What population does LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP carry?

Offline now for LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP, with the last sample 13 days 1 hours ago.

About the server

What Rust version does LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP run?

Version Rust network protocol 2634 and build 167781 on Windows is reported by LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP. Steam updates your game for you, but the protocol must match to join.

How reliable is LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP, and is it up?

The latest sample has LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP offline, with a last sighting 13 days 1 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 16 October 2026.

Which location does LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP run from?

No region tag is published by LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP, though its name points to Asia. 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 1.161.216.47:28015.

Map and rules

Which rules apply on LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP, and what settings?

The name LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

Which map has LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP selected?

Size 3,500, seed 123456: the procedural map on LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

On what schedule does LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP wipe?

Too few wipes are on record for LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP to reveal its 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 13 days 5 hours ago.

What is wipe day on LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP like?

Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Where does LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP appear among Rust Data lists and filters?

These Rust Data lists include LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP: Rust community servers, unfiltered. It appears under these filters on the server list: Region: Asia; 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 LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP?

These tags are published by LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

How can I connect to LAST STAND | TW | Vanilla | No Limit Teams | Hardcore PvP?

Enter client.connect 1.161.216.47: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 mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players 50 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167781
Build Build number: 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

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 55,754 players 11,716 servers online