Offline 62.129.150.101:28022 checked 20d ago
TEST SERVER NAME
Connect
srv = rust.server("62.129.150.101:28022")
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 8 Oct. 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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 11:30 UTC25d ago | NaN | NaN | running | 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
3000 · seed 1234567- map
- Procedural Map
- size
- 3000
- seed
- 1234567
Server
srv.info()- address
- 62.129.150.101:28022
- region
- –
- max players
- 10
- group limit
- not published
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 11:30 UTC
- hostname
- –
- first seen
- 2 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 | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 96/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 | 10/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TEST SERVER NAME rank?
Rank #15,662 on seven-day player hours for TEST SERVER NAME, within the top 71% of all ranked servers.
How full does TEST SERVER NAME run?
The current row shows TEST SERVER NAME offline; the last response was 20 days 16 hours ago.
Server facts
Which Rust version is TEST SERVER NAME on?
Version Rust network protocol 2332 on Windows is reported by TEST SERVER NAME. Steam updates your game for you, but the protocol must match to join.
How reliable is TEST SERVER NAME, and is it up?
The latest sample has TEST SERVER NAME offline, with a last sighting 20 days 16 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 2 October 2026.
In which location is TEST SERVER NAME hosted?
There is no region published for TEST SERVER NAME. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 62.129.150.101:28022.
Rules, settings, map
Which settings and rules does TEST SERVER NAME run?
You will not find a gather rate in the string TEST SERVER NAME. No group limit is published. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The VAC field reads off.
Which map has TEST SERVER NAME loaded?
Size 3,000, seed 1234567: the procedural map on TEST SERVER NAME, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does TEST SERVER NAME wipe, and how often?
A rhythm cannot be read from the wipes of TEST SERVER NAME on record, which are too few. 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 25 days 19 hours ago.
Lists and tags
Where does TEST SERVER NAME appear among Rust Data lists and filters?
The Rust Data lists that TEST SERVER NAME fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded.
How should you read the server tags on TEST SERVER NAME?
These tags are published by TEST SERVER NAME and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; v2332 (Protocol): Protocol 2332 is required; a different game version cannot connect; ptrak (Networking): Network traffic runs over RakNet, the game standard; oxide (Oxide): The plugin framework in use is Oxide (uMod); modded (Modded): The Modded section lists it, because plugins or settings change the game; h955eb6e7 (Custom tag): A plugin or the owner added this; standard Rust does not define it; stok (Custom tag): A plugin or the owner added this; standard Rust does not define it. 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.
How to join
What is the way into TEST SERVER NAME?
In Rust, F1 opens the console: type client.connect 62.129.150.101:28022. Launch Rust on this page does the same by opening the game through Steam and connecting.