Online 136.46.129.110:28015 checked 11m ago
DevRustQA
Connect
srv = rust.server("136.46.129.110:28017")
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. 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 bestTop 20% of all ranked servers. 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 22:35 UTC40m ago | NaN | NaN | running | 0 |
| 1 | Wed 21 Oct, 20:42 UTC7d ago | 1 | NaN | NaN | 1 |
| 2 | Thu 1 Oct, 19:10 UTC FW27d ago | 1 | held half | 20.1 days | 1 |
| 3 | Fri 25 Sep, 06:56 UTC33d ago | 1 | held half | 6.5 days | 0 |
| 4 | Thu 24 Sep, 17:56 UTC34d ago | 1 | NaN | 0.5 days | 1 |
| 5 | Sun 20 Sep, 17:46 UTC38d ago | 1 | held half | 4 days | 1 |
# 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
- map
- QAIsland
- size
- –
- seed
- –
Server
srv.info()- address
- 136.46.129.110:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 28 Oct 2026, 22:35 UTC
- hostname
- –
- first seen
- 18 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 56/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 54/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 53/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 16/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Player counts
How does DevRustQA compare in the rankings?
Over the last seven days DevRustQA sits at #4,491 on player hours, in the top 20% of ranked servers.
What population does DevRustQA carry?
The sample now reads 1 players for DevRustQA, out of 2 slots. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 00:00 UTC is the busiest, at 1 players.
Server facts
Which Rust version is DevRustQA on?
The build is Rust network protocol 2635 and build 169587 on Windows, run by DevRustQA. Joining needs the same protocol on your game; Steam handles the update.
Is DevRustQA up, and what does its uptime show?
DevRustQA reports itself online at the current refresh. Uptime of 42% across the last 7 full days: 71 hours of 168. Rust Data logged it first on 18 September 2026.
Where does DevRustQA sit?
There is no region published for DevRustQA. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 136.46.129.110:28015.
Rules, settings, map
Which rules apply on DevRustQA, and what settings?
No gather rate appears in the name: DevRustQA. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Wipe data
On what schedule does DevRustQA wipe?
Irregular wipe times on DevRustQA leave no next wipe to forecast. 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 40 minutes ago, and that is the one in play.
On DevRustQA, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags and filters
Where does DevRustQA appear among Rust Data lists and filters?
The Rust Data lists that DevRustQA fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.
How should you read the server tags on DevRustQA?
These tags are published by DevRustQA and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs169587 (Build): Build number: 169587; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. 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
What is the way into DevRustQA?
Enter client.connect 136.46.129.110:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.