Online NA 54.39.102.131:28015 checked 11m ago
US Testing Server
Connect
srv = rust.server("54.39.102.131:28020")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
Top 68% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 01:31 UTC13d ago | 0 | NaN | running | 0 |
| 1 | Thu 15 Oct, 09:31 UTC14d ago | 0 | NaN | 0.7 days | 0 |
| 2 | Wed 14 Oct, 17:31 UTC15d ago | 0 | NaN | 0.7 days | 0 |
| 3 | Wed 14 Oct, 01:31 UTC15d ago | 0 | NaN | 0.7 days | 0 |
| 4 | Tue 13 Oct, 01:45 UTC16d ago | 0 | NaN | 1 days | 0 |
| 5 | Sun 27 Sep, 05:22 UTC32d ago | 0 | NaN | 15.8 days | 0 |
| 6 | Sat 26 Sep, 20:53 UTC32d ago | 0 | NaN | 0.4 days | 0 |
| 7 | Sat 26 Sep, 02:25 UTC33d ago | 0 | NaN | 0.8 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())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Friendly Seattle: No KOS | Chill | Noob Friendly | NA · groups of 8+ · biweekly · 42 on average | 32/100 |
| 1 | [US] Enardo - Random Farming - Small One Grid | OneGrid | NA · groups of 8+ · 29 on average | 33/50 |
| 2 | [NA] Willjum's Solo Only | Thursday Wipes | NA · groups of 8+ · weekly · 27 on average | 16/100 |
| 3 | Rust Degens - US Vanilla | Fridays | NA · groups of 8+ · weekly · 15 on average | 6/150 |
| 4 | [NA] Willjum's Casual Solo/Duo Monthly | NA · groups of 8+ · monthly · 14 on average | 8/175 |
| 5 | Hempville 420 No Kos Low Decay / Limited PvP | NA · groups of 8+ · monthly · 7 on average | 7/90 |
Quick answers
From the figures on this page.
Population data
How does US Testing Server compare in the rankings?
Player hours over the last seven days: #15,269 for US Testing Server, #1,495 in North America, within the top 68% of the ranked set.
How full does US Testing Server run?
0 is the count in the players field for US Testing Server at this refresh. Over the last seven days it averaged 0 players.
Server data
How well does US Testing Server perform?
Server fps over the last 48 hours averages 20; the floor is 20. Entity numbers reached 69,605, and that includes buildings, deployables and the rest. A high of 2,225 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on US Testing Server?
Rust network protocol 2634 and build 167584 on Windows is what US Testing Server runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is US Testing Server, and is it up?
US Testing Server reports itself online at the current refresh. A restart about 8 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 25 September 2026.
In which location is US Testing Server hosted?
With its NA tag, US Testing Server lists itself in North America. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 54.39.102.131:28015.
Map and rules
What rules and settings are recorded for US Testing Server?
You will not find a gather rate in the string US Testing Server. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has US Testing Server loaded?
The game generates the map on US Testing Server: procedural, size 3,700, seed 1337. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.
Wipe schedule
When does US Testing Server wipe, and on what schedule?
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 13 days 19 hours ago, and that is the one in play.
On US Testing Server, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain US Testing Server?
These Rust Data lists include US Testing Server: 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; Last wipe: In the last 2 weeks.
How should you read the server tags on US Testing Server?
These tags are published by US Testing Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): The server lists 0 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167584 (Build): The server runs build 167584; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^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.
Join steps
How can I connect to US Testing Server?
In Rust, F1 opens the console: type client.connect 54.39.102.131:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.