Offline 95.105.76.2:28115 checked 23d ago
ANCHOR TEST - local stand
Connect
srv = rust.server("95.105.76.2:28117")
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 71% 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 0, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 12:28 UTC23d ago | 0 | NaN | running | 0 |
| 1 | Thu 24 Sep, 17:31 UTC33d ago | 0 | NaN | 9.8 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 95.105.76.2:28115
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 12:28 UTC
- hostname
- –
- first seen
- 24 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 | 174/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 178/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 139/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 16/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 53/1000 |
Quick answers
From the figures on this page.
Population data
How does ANCHOR TEST - local stand compare in the rankings?
Player hours over seven days put ANCHOR TEST - local stand at #16,009, in the top 71% of the ranked set.
How full does ANCHOR TEST - local stand run?
The current row shows ANCHOR TEST - local stand offline; the last response was 23 days 22 hours ago.
Server data
Which Rust version is ANCHOR TEST - local stand on?
Rust network protocol 2634 and build 166652 on Windows is what ANCHOR TEST - local stand runs. The protocol has to match before you can join, and Steam does the updating.
Is ANCHOR TEST - local stand up, and what does its uptime show?
ANCHOR TEST - local stand is offline at this refresh; the last response came 23 days 22 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 24 September 2026.
Which location does ANCHOR TEST - local stand run from?
There is no region published for ANCHOR TEST - local stand. Rust Data does not look up where the machine stands; it shows where a server says it is. 95.105.76.2:28115 is its address.
Rules, settings, map
Which settings and rules does ANCHOR TEST - local stand run?
No gather rate appears in the name: ANCHOR TEST - local stand. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has ANCHOR TEST - local stand loaded?
A procedural map runs on ANCHOR TEST - local stand, generated by the game.
Wipe data
On what schedule does ANCHOR TEST - local stand wipe?
A rhythm cannot be read from the wipes of ANCHOR TEST - local stand on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 23 days 22 hours ago.
What is wipe day on ANCHOR TEST - local stand like?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 1 hours in.
Tags, lists
Where does ANCHOR TEST - local stand appear among Rust Data lists and filters?
On Rust Data, ANCHOR TEST - local stand appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on ANCHOR TEST - local stand hold?
These tags are published by ANCHOR TEST - local stand and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 ANCHOR TEST - local stand?
Enter client.connect 95.105.76.2:28115 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.