Online 79.160.193.176:28015 checked 7m ago
RustTool Test
Connect
srv = rust.server("79.160.193.176: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 best
Top 51% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 19:22 UTC3d ago | 1 | NaN | running | 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
- 79.160.193.176:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 19:22 UTC
- hostname
- –
- first seen
- 25 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 · 151 on average | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 93/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 31/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 | 9/1000 |
Quick answers
From the figures on this page.
Player counts
What position does RustTool Test take in the server rankings?
Player hours over seven days put RustTool Test at #11,399, in the top 51% of the ranked set.
How many players does RustTool Test hold at once?
The sample now reads 0 players for RustTool Test, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 1.
About the server
What is the Rust version on RustTool Test?
The build is Rust network protocol 2635 and build 168909 on Linux, run by RustTool Test. Steam updates your game for you, but the protocol must match to join.
How reliable is RustTool Test, and is it up?
RustTool Test reports itself online at the current refresh. Over the last 3 full days the hours up number 71 of 72, 99%. Rust Data logged it first on 25 October 2026.
Which location does RustTool Test run from?
There is no region published for RustTool Test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 79.160.193.176:28015.
Map and rules
Which settings and rules does RustTool Test run?
You will not find a gather rate in the string RustTool Test. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. The VAC field reads off.
Which map has RustTool Test loaded?
The game generates its map: procedural, on RustTool Test.
Wipe schedule
On what schedule does RustTool Test wipe?
The record for RustTool Test holds too few wipes to show a rhythm. 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 3 days 11 hours ago.
What is wipe day on RustTool Test like?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold RustTool Test, and which filters?
On Rust Data, RustTool Test appears in these lists: 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 week.
How should you read the server tags on RustTool Test?
Read by the game's server browser, the tags RustTool Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; 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): The plugin framework in use is 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.
Connecting
What is the way to join RustTool Test?
In Rust, F1 opens the console: type client.connect 79.160.193.176:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.