Rust Data

rustdata.spaceservers50.46.144.90:28016.ipynb

Run all rust-data · live

‹ All servers

Online 50.46.144.90:28015 checked 15m ago

.vAs. Gaming: Rust! - VASGaming.com

Connect

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

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,341 # top 69%
last wipe 7d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123417:0002:0011:0020:0005:0014:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510017:0002:0011:0020:0005:0014:00

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 18 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
15k10k15k20k18 Oct20 Oct22 Oct25 Oct27 Oct29 Oct

Top 69% 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.

usual gap3.7 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 22 OctSun 18 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 22 Oct, 00:01 UTC7d ago 0 NaN running 0
1 Sun 18 Oct, 06:25 UTC11d ago 0 NaN 3.7 days 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

4500 · seed 6738
Map of .vAs. Gaming: Rust! - VASGaming.com
map
Procedural Map
size
4500
seed
6738
Open on RustMaps

Server

srv.info()
address
50.46.144.90:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
22 Oct 2026, 00:01 UTC
hostname
–
first seen
17 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 · 514 on average435/500
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average463/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 281 on average982/1000
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average58/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average982/1000
5Rustoria.co - US MainNA · groups of 16+ · weekly · 236 on average29/250

Quick answers

From the figures on this page.

Population

How does .vAs. Gaming: Rust! - VASGaming.com compare in the rankings?

Player hours over seven days put .vAs. Gaming: Rust! - VASGaming.com at #15,341, in the top 69% of the ranked set.

What population does .vAs. Gaming: Rust! - VASGaming.com carry?

The sample now reads 0 players for .vAs. Gaming: Rust! - VASGaming.com, out of 100 slots. Over the last seven days it averaged 0 players.

About the server

What does performance look like on .vAs. Gaming: Rust! - VASGaming.com?

The 48-hour average is 42 server fps, with a low of 15. Buildings, deployables and all else in the world took the count as high as 112,055 entities. A high of 3,207 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on .vAs. Gaming: Rust! - VASGaming.com?

The build is Rust network protocol 2635 and build 168909 on Linux, run by .vAs. Gaming: Rust! - VASGaming.com. Steam updates your game for you, but the protocol must match to join.

How reliable is .vAs. Gaming: Rust! - VASGaming.com, and is it online now?

Online is the state at the latest refresh for .vAs. Gaming: Rust! - VASGaming.com. A restart about 3 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 17 October 2026.

Which location does .vAs. Gaming: Rust! - VASGaming.com run from?

For .vAs. Gaming: Rust! - VASGaming.com, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 50.46.144.90:28015 is its address.

Rules, settings, map

What rules and settings are recorded for .vAs. Gaming: Rust! - VASGaming.com?

The name .vAs. Gaming: Rust! - VASGaming.com carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

What is the map on .vAs. Gaming: Rust! - VASGaming.com?

.vAs. Gaming: Rust! - VASGaming.com runs a procedural map of size 4,500 with seed 6738, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does .vAs. Gaming: Rust! - VASGaming.com wipe, and how often?

A rhythm cannot be read from the wipes of .vAs. Gaming: Rust! - VASGaming.com on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 7 days 16 hours ago, and that is the one in play.

What is wipe day on .vAs. Gaming: Rust! - VASGaming.com like?

The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.

Tags and filters

Where does .vAs. Gaming: Rust! - VASGaming.com appear among Rust Data lists and filters?

The Rust Data lists that .vAs. Gaming: Rust! - VASGaming.com 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; Last wipe: In the last 2 weeks.

How should you read the server tags on .vAs. Gaming: Rust! - VASGaming.com?

Read by the game's server browser, the tags .vAs. Gaming: Rust! - VASGaming.com publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

How can I connect to .vAs. Gaming: Rust! - VASGaming.com?

Enter client.connect 50.46.144.90:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://www.vasgaming.com/ is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players 100 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
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 96,161 players 11,873 servers online