Offline 123.50.149.73:28019 checked 13d ago
RetroPVE
Connect
srv = rust.server("123.50.149.73:28020")
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 65% 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 15:46 UTC13d ago | 1 | 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
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 123.50.149.73:28019
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 16:18 UTC
- hostname
- –
- first seen
- 16 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 · 150 on average | 40/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 84/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 34/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 87/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 301/310 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does RetroPVE rank?
Rank #14,066 on seven-day player hours for RetroPVE, within the top 65% of all ranked servers.
How many players does RetroPVE hold at once?
The current row shows RetroPVE offline; the last response was 13 days 5 hours ago.
About the server
What Rust version does RetroPVE run?
Rust network protocol 2634 and build 167781 on Linux is what RetroPVE runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is RetroPVE, and is it up?
The latest sample has RetroPVE offline, with a last sighting 13 days 5 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 16 October 2026.
Which location does RetroPVE run from?
There is no region published for RetroPVE. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 123.50.149.73:28019 is its address.
Map and rules
What rules and settings are recorded for RetroPVE?
You will not find a gather rate in the string RetroPVE. No custom cap; the default of 8 players per group stands. survival is the game mode here, and 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. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
When does RetroPVE wipe, and on what schedule?
Too few wipes are on record for RetroPVE to reveal its rhythm. 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 13 days 6 hours ago, and that is the one in play.
On RetroPVE, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold RetroPVE, and which filters?
The Rust Data lists that RetroPVE fits are: 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 RetroPVE?
These tags are published by RetroPVE and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; 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
How can I connect to RetroPVE?
In Rust, F1 opens the console: type client.connect 123.50.149.73:28019. Launch Rust on this page does the same by opening the game through Steam and connecting.