Offline 195.138.91.141:28015 checked 25d ago
TEST
Connect
srv = rust.server("195.138.91.141: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, measured since 26 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 · 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 07:49 UTC27d ago | 1 | NaN | running | 0 |
| 1 | Thu 1 Oct, 18:20 UTC FW27d ago | 1 | NaN | 0.6 days | 1 |
| 2 | Mon 28 Sep, 23:59 UTC30d ago | 2 | held half | 2.8 days | 0 |
| 3 | Sat 26 Sep, 21:05 UTC32d ago | 2 | NaN | 2.1 days | 2 |
# 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
3250 · seed 387396033
- map
- Procedural Map
- size
- 3250
- seed
- 387396033
Server
srv.info()- address
- 195.138.91.141:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 07:49 UTC
- hostname
- –
- first seen
- 26 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 · 149 on average | 157/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 · 118 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 66/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 11/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 21/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does TEST rank?
Rank #15,998 on seven-day player hours for TEST, within the top 70% of all ranked servers.
How many players does TEST hold at once?
TEST returns no live count at this refresh, having last been seen 25 days 23 hours ago.
About the server
What is the Rust version on TEST?
Version Rust network protocol 2634 and build 166586 on Windows is reported by TEST. The protocol has to match before you can join, and Steam does the updating.
How reliable is TEST, and is it up?
The latest sample has TEST offline, with a last sighting 25 days 23 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 26 September 2026.
Where does TEST sit?
For TEST, no region is published. 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 195.138.91.141:28015.
Settings and map
Which settings and rules does TEST run?
You will not find a gather rate in the string TEST. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has TEST selected?
The game generates the map on TEST: procedural, size 3,250, seed 387396033. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does TEST wipe, and how often?
No next wipe can be predicted for TEST, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 27 days 3 hours ago.
What is wipe day on TEST like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Lists and tags
Which Rust Data filters and lists contain TEST?
These Rust Data lists include TEST: 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.
How should you read the server tags on TEST?
These tags are published by TEST and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166586 (Build): The server runs build 166586; 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): 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
What is the way into TEST?
Enter client.connect 195.138.91.141:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.