Offline 93.175.40.170:28047 checked 2h ago
test server
Connect
srv = rust.server("93.175.40.170:28048")
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 best
Top 29% 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, 18:54 UTC9h ago | NaN | NaN | running | 0 |
| 1 | Mon 26 Oct, 18:54 UTC2d ago | 1 | held half | 2 days | 0 |
| 2 | Sat 10 Oct, 08:39 UTC18d ago | 0 | NaN | 16.4 days | 1 |
| 3 | Fri 18 Sep, 17:02 UTC40d ago | 1 | NaN | 21.7 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())
Map
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 93.175.40.170:28047
- region
- –
- max players
- 547
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Oct 2026, 00:29 UTC
- hostname
- –
- first seen
- 15 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 · 153 on average | 35/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 59/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Player counts
How does test server compare in the rankings?
Over the last seven days test server sits at #6,439 on player hours, in the top 29% of ranked servers.
What population does test server carry?
Offline now for test server, with the last sample 2 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 19:00 UTC, averaging 1 players.
Server facts
Which Rust version is test server on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by test server. The protocol has to match before you can join, and Steam does the updating.
How reliable is test server, and is it online now?
The latest sample has test server offline, with a last sighting 2 hours ago. Over the last 7 full days the hours up number 23 of 168, 14%. Its earliest recorded date in Rust Data is 15 September 2026.
Where does test server sit?
No region is published by test server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 93.175.40.170:28047.
Map and rules
What rules and settings are recorded for test server?
The name test server carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. Anti-cheat status: VAC on.
Wipes and dates
When does test server wipe, and on what schedule?
Irregular wipe times on test server leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 4 hours ago, and that is the one in play.
What is wipe day on test server like?
Recent wipes averaged 1 players at their peak. 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
Which lists on Rust Data hold test server, and which filters?
On Rust Data, test server appears in these lists: Modded Rust servers. It appears under these filters 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.
Which meanings do the tags on test server hold?
These tags are published by test server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp547 (Max players): The server lists 547 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to test server?
The manual route: launch Rust, F1, then client.connect 93.175.40.170:28047. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.