Offline 171.254.141.176:28025 checked 5d ago
TEST COPY (update check)
Connect
srv = rust.server("171.254.141.176:28027")
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 171.254.141.176:28025
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 16:38 UTC
- hostname
- –
- first seen
- 24 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 · 149 on average | 188/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 84/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 27/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 29/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 273/700 |
Quick answers
From the figures on this page.
Player counts
How does TEST COPY (update check) compare in the rankings?
Rank #15,326 on seven-day player hours for TEST COPY (update check), within the top 69% of all ranked servers.
How many players does TEST COPY (update check) hold at once?
TEST COPY (update check) returns no live count at this refresh, having last been seen 5 days 1 hours ago. Over the last seven days it averaged 0 players.
About the server
What Rust version does TEST COPY (update check) run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by TEST COPY (update check). The protocol has to match before you can join, and Steam does the updating.
How reliable is TEST COPY (update check), and is it up?
TEST COPY (update check) is offline at this refresh; the last response came 5 days 1 hours ago. 0 of 96 hours up over the last 4 full days, or 0%. Its earliest recorded date in Rust Data is 24 October 2026.
Where does TEST COPY (update check) sit?
There is no region published for TEST COPY (update check). The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 171.254.141.176:28025 is its address.
Rules, settings, map
Which rules apply on TEST COPY (update check), and what settings?
The name TEST COPY (update check) carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has TEST COPY (update check) loaded?
A procedural map runs on TEST COPY (update check), generated by the game.
Wipe data
When does TEST COPY (update check) wipe, and how often?
A rhythm cannot be read from the wipes of TEST COPY (update check) on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 9 days 21 hours ago, and that is the one in play.
Tags and filters
Which lists on Rust Data hold TEST COPY (update check), and which filters?
On Rust Data, TEST COPY (update check) 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 2 weeks.
How should you read the server tags on TEST COPY (update check)?
The game's server browser reads these tags from TEST COPY (update check): gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^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 COPY (update check)?
The manual route: launch Rust, F1, then client.connect 171.254.141.176:28025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.