Offline 185.189.255.249:35400 checked 29d ago
testing
Connect
srv = rust.server("185.189.255.249:35410")
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 20 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 bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Tuesday 3 November, 11:31 UTC, in 4d 16h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 4d 16h | Tue 3 Nov, 11:31 UTC | wipe |
| 1 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 11d 16h | Tue 10 Nov, 11:31 UTC | wipe |
| 3 | 18d 16h | Tue 17 Nov, 11:31 UTC | wipe |
| 4 | 25d 16h | Tue 24 Nov, 11:31 UTC | wipe |
| 5 | 32d 16h | Tue 1 Dec, 11:31 UTC | wipe |
| 6 | 34d 23h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 39d 16h | Tue 8 Dec, 11:31 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 29 Sep, 11:31 UTC30d ago | 1 | NaN | running | 1 |
| 1 | Sun 27 Sep, 07:47 UTC32d ago | 2 | held half | 2.2 days | 2 |
| 2 | Sat 26 Sep, 09:48 UTC33d ago | 2 | NaN | 0.9 days | 0 |
| 3 | Fri 25 Sep, 14:19 UTC34d ago | 2 | NaN | 0.8 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
2500 · seed 53296983
- map
- Procedural Map
- size
- 2500
- seed
- 53296983
Server
srv.info()- address
- 185.189.255.249:35400
- region
- –
- max players
- 50
- group limit
- 5 max
- wipe schedule
- weekly
- last wipe
- 29 Sep 2026, 11:31 UTC
- hostname
- –
- first seen
- 20 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 | RETRO RUST #3 Х5|MAX 5|LOOT+|CRAFT GLOBAL 29.10 | EU · groups of 5 · weekly · 75 on average | 208/250 |
| 1 | 红果十倍/10.26号新开/爆枪/新人入门 | EA · groups of 6 · weekly · 9 on average | 1/200 |
| 2 | РУССКИЙ ДЛЯ НОВИЧКОВ | MAX5 | 50%Upkeep 23.10 | EU · groups of 5 · weekly · 1 on average | 0/200 |
| 3 | Rusty Moose |EU Mini| | EU · groups of 5 · weekly · 74 on average | 273/300 |
| 4 | Rusty Moose |US Mini| | NA · groups of 5 · weekly · 56 on average | 29/150 |
| 5 | [LATAM] LUNARUST Vanilla | 27/10 Wipe | SA · groups of 5 · weekly · 17 on average | 12/200 |
Quick answers
From the figures on this page.
Population data
What position does testing take in the server rankings?
Rank #16,773 on seven-day player hours for testing, within the top 70% of all ranked servers.
What population does testing carry?
testing returns no live count at this refresh, having last been seen 29 days 2 hours ago.
Server data
Which Rust version is testing on?
Version Rust network protocol 2633 and build 165217 on Windows is reported by testing. Joining needs the same protocol on your game; Steam handles the update.
Is testing up, and what does its uptime show?
The latest sample has testing offline, with a last sighting 29 days 2 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 20 September 2026.
Which location does testing run from?
No region is published by testing. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 185.189.255.249:35400.
Settings and map
What rules and settings are recorded for testing?
No gather rate appears in the name: testing. 5 players is the maximum per group. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has testing selected?
The game generates the map on testing: procedural, size 2,500, seed 53296983. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
On what schedule does testing wipe?
Too few wipes are on record for testing to confirm its schedule, so the tag drives the prediction. The schedule puts the next wipe on Tuesday 3 November at 11:31 UTC. The world it runs now was generated 30 days 7 hours ago. A weekly wipe schedule is published in its tags.
What is wipe day on testing like?
Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 1 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags and filters
Where does testing appear among Rust Data lists and filters?
These Rust Data lists include testing: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
Which meanings do the tags on testing hold?
Read by the game's server browser, the tags testing publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): The server lists 50 slots; ts5 (Group limit): The team cap is 5; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^w (Weekly): A wipe every week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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 testing?
In Rust, F1 opens the console: type client.connect 185.189.255.249:35400. Launch Rust on this page does the same by opening the game through Steam and connecting.