Rust Data

rustdata.spaceservers54.39.102.131:21020.ipynb

Run all rust-data · live

‹ All servers

Online NA 54.39.102.131:21015 checked 23m ago

US Testing Server

moddedoxide

Connect

srv = rust.server("54.39.102.131:21020")
print(srv.connect_command)

Right now

srv.summary()
players now 0/?
7-day average 0 # peak –
rank #15,262 # top 69% · #1495 in NA
last wipe 14d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123401:0010:0020:0005:0014:0023:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
0510152001:0010:0020:0005:0014:0023: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 25 Sep. 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
15k10k15k20k26 Sep3 Oct9 Oct16 Oct22 Oct29 Oct

Top 69% of all ranked servers, top 80% in NA. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.9 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 15 OctWed 14 OctWed 14 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 15 Oct, 21:30 UTC14d ago 0 NaN running 0
1 Wed 14 Oct, 21:21 UTC15d ago 0 NaN 1 days 0
2 Wed 14 Oct, 13:30 UTC15d ago 0 NaN 0.3 days 0
3 Tue 13 Oct, 13:21 UTC16d ago 0 NaN 1 days 0
4 Tue 13 Oct, 01:44 UTC16d ago 0 NaN 0.5 days 0
5 Sat 26 Sep, 20:50 UTC33d ago 0 NaN 16.2 days 0
6 Fri 25 Sep, 23:26 UTC34d ago 0 NaN 0.9 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

1024 · seed 1337
Map of US Testing Server
map
CraggyIsland
size
1024
seed
1337

Server

srv.info()
address
54.39.102.131:21015
region
NA
max players
–
group limit
8, the default
wipe schedule
–
last wipe
15 Oct 2026, 21:30 UTC
hostname
–
first seen
25 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Friendly Seattle: No KOS | Chill | Noob FriendlyNA · groups of 8+ · biweekly · 41 on average54/100
1[US] Enardo - Random Farming - Small One Grid | OneGridNA · groups of 8+ · 30 on average37/50
2[NA] Willjum's Solo Only | Thursday WipesNA · groups of 8+ · weekly · 26 on average93/100
3Rust Degens - US Vanilla | FridaysNA · groups of 8+ · weekly · 15 on average6/150
4[NA] Willjum's Casual Solo/Duo MonthlyNA · groups of 8+ · monthly · 14 on average18/175
5Hempville 420 No Kos Low Decay / Limited PvPNA · groups of 8+ · monthly · 7 on average9/90

Quick answers

From the figures on this page.

Population data

How does US Testing Server compare in the rankings?

Ranked #15,262 on seven-day player hours, US Testing Server is #1,495 in North America and in the top 69% of all ranked servers.

What population does US Testing Server carry?

Point query at this second: US Testing Server returns 0 players. Over the last seven days it averaged 0 players.

Server facts

How well does US Testing Server perform?

The 48-hour average is 20 server fps, with a low of 18. The entity count peaked at 2,909, covering buildings, deployables and the rest of the world. The memory field tops out at 632 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does US Testing Server run?

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

How reliable is US Testing Server, and is it online now?

Online is the state at the latest refresh for US Testing Server. Count back 13 hours from its reported uptime to get the last restart. 143 of 168 hours up over the last 7 full days, or 85%. Its earliest recorded date in Rust Data is 25 September 2026.

In which location is US Testing Server hosted?

The NA tag is what US Testing Server uses to list itself in North America. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 54.39.102.131:21015 is its address.

Map and rules

What rules and settings are recorded for US Testing Server?

No gather rate appears in the name: US Testing Server. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has US Testing Server selected?

The game generates the map on US Testing Server: procedural, size 1,024, seed 1337. Size and seed fix the map, so RustMaps can show it, linked from this page. CraggyIsland is what the map name field says.

Wipe data

On what schedule does US Testing Server wipe?

Irregular wipe times on US Testing Server leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 14 days 3 hours ago, and that is the one in play.

What is wipe day on US Testing Server like?

Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.

Lists and tags

Which Rust Data filters and lists contain US Testing Server?

The Rust Data lists that US Testing Server fits are: Modded Rust servers and North America Rust servers. Under these filters on the server list, it is listed: Region: North America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on US Testing Server?

Read by the game's server browser, the tags US Testing Server publishes are: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): Slot count: 0; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167584 (Build): The server runs build 167584; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; NA (North America): The server browser files it under North America. 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 US Testing Server?

Enter client.connect 54.39.102.131:21015 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 mp0,ptrak,$r?,v2634,NA,gmrust,cs167584,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp0
Max players Slot count: 0.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs167584
Build The server runs build 167584.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

Region

NA
North America The server browser files it under North America.

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