Offline 42.114.93.106:28025 checked 5d ago
TEST COPY (update check)
Connect
srv = rust.server("42.114.93.106: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 40% 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
- 42.114.93.106:28025
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 16:38 UTC
- hostname
- –
- first seen
- 23 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 | 20/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 · 122 on average | 39/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 5/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 23/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 96/200 |
Quick answers
From the figures on this page.
Population data
How does TEST COPY (update check) compare in the rankings?
Over the last seven days TEST COPY (update check) sits at #8,976 on player hours, in the top 40% of ranked servers.
What population does TEST COPY (update check) carry?
The current row shows TEST COPY (update check) offline; the last response was 5 days 21 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
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). Joining needs the same protocol on your game; Steam handles the update.
How reliable is TEST COPY (update check), and is it online now?
Offline now for TEST COPY (update check), last seen 5 days 21 hours ago. Over the last 6 full days the hours up number 6 of 144, 4%. Rust Data logged it first on 23 October 2026.
In which location is TEST COPY (update check) hosted?
For TEST COPY (update check), no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 42.114.93.106:28025.
Settings and map
Which rules apply on TEST COPY (update check), and what settings?
You will not find a gather rate in the string TEST COPY (update check). 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. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
What is the map on TEST COPY (update check)?
A procedural map runs on TEST COPY (update check), generated by the game.
Wipe data
On what schedule does TEST COPY (update check) wipe?
The record for TEST COPY (update check) holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 10 days 11 hours ago.
Tags, lists
Which lists on Rust Data hold TEST COPY (update check), and which filters?
These Rust Data lists include TEST COPY (update check): 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; Last wipe: In the last 2 weeks.
Which meanings do the tags on TEST COPY (update check) hold?
The game's server browser reads these tags from TEST COPY (update check): gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; 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): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed 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 42.114.93.106:28025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.