Online 90.146.82.82:28035 checked 13m ago
Testing
Connect
srv = rust.server("90.146.82.82:28036")
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 68% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 4 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 22:03 UTC4d 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 90.146.82.82:28035
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 22:03 UTC
- hostname
- –
- first seen
- 6 Oct 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 · 161 on average | 29/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 42/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 32/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 9/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 11/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Testing take in the server rankings?
Rank #15,074 on seven-day player hours for Testing, within the top 68% of all ranked servers.
How full does Testing run?
The sample now reads 0 players for Testing, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
What is the Rust version on Testing?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Testing. Steam updates your game for you, but the protocol must match to join.
How reliable is Testing, and is it up?
Online is the state at the latest refresh for Testing. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 6 October 2026.
Where does Testing sit?
No region is published by Testing. Rust Data does not look up where the machine stands; it shows where a server says it is. 90.146.82.82:28035 is its address.
Settings and map
Which rules apply on Testing, and what settings?
The name Testing 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. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
What is the map on Testing?
The game generates its map: procedural, on Testing.
Wipe schedule
On what schedule does Testing wipe?
The record for Testing holds too few wipes to show a 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 4 days 4 hours ago.
On Testing, what happens on wipe day?
The average peak over recent wipes is 1 players. 4 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain Testing?
On Rust Data, Testing appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on Testing?
These tags are published by Testing and read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into Testing?
Enter client.connect 90.146.82.82:28035 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.