Offline 85.138.250.124:28015 checked 3h ago
TesteDev
Connect
srv = rust.server("85.138.250.124: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 62% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 22:27 UTC4h ago | NaN | NaN | running | 1 |
| 1 | Tue 29 Sep, 11:46 UTC29d ago | 1 | NaN | 29.4 days | 0 |
| 2 | Fri 25 Sep, 12:31 UTC33d ago | 1 | NaN | 4 days | 1 |
| 3 | Tue 22 Sep, 10:33 UTC36d ago | 1 | NaN | 3.1 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 85.138.250.124:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 28 Oct 2026, 22:27 UTC
- hostname
- –
- first seen
- 21 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 · 155 on average | 27/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 | 28/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 12/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does TesteDev rank?
Over the last seven days TesteDev sits at #13,810 on player hours, in the top 62% of ranked servers.
How many players does TesteDev hold at once?
Offline now for TesteDev, with the last sample 3 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 22:00 UTC, averaging 1 players.
Server facts
What Rust version does TesteDev run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by TesteDev. Steam updates your game for you, but the protocol must match to join.
Is TesteDev up, and what does its uptime show?
The latest sample has TesteDev offline, with a last sighting 3 hours ago. 1 of 168 hours up over the last 7 full days, or 1%. Its earliest recorded date in Rust Data is 21 September 2026.
Where does TesteDev sit?
For TesteDev, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 85.138.250.124:28015.
Map and rules
Which rules apply on TesteDev, and what settings?
You will not find a gather rate in the string TesteDev. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
Which map has TesteDev loaded?
A procedural map runs on TesteDev, generated by the game.
Wipe schedule
When does TesteDev wipe, and how often?
No next wipe can be predicted for TesteDev, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 4 hours ago.
On TesteDev, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in.
Lists and tags
Where does TesteDev appear among Rust Data lists and filters?
The Rust Data lists that TesteDev fits are: 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 24 hours.
Which meanings do the tags on TesteDev hold?
Read by the game's server browser, the tags TesteDev publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is 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.
How to join
What is the way to join TesteDev?
The manual route: launch Rust, F1, then client.connect 85.138.250.124:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.