Offline 102.135.245.21:29031 checked 15h ago
Rust-CPT-TEST
Connect
srv = rust.server("102.135.245.21:29032")
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 20 Sep. 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 30% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 | Wed 21 Oct, 17:47 UTC8d ago | 1 | NaN | running | 1 |
| 1 | Fri 16 Oct, 19:56 UTC12d ago | 2 | held half | 4.9 days | 0 |
| 2 | Sun 4 Oct, 13:12 UTC25d ago | 0 | NaN | 12.3 days | 0 |
| 3 | Mon 21 Sep, 08:50 UTC38d ago | 0 | NaN | 13.2 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
3000 · seed 19845
- map
- Procedural Map
- size
- 3000
- seed
- 19845
Server
srv.info()- address
- 102.135.245.21:29031
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 21 Oct 2026, 17:47 UTC
- hostname
- –
- first seen
- 20 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 · 151 on average | 114/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 195/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 75/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 221/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Population data
What position does Rust-CPT-TEST take in the server rankings?
Player hours over seven days put Rust-CPT-TEST at #6,720, in the top 30% of the ranked set.
How many players does Rust-CPT-TEST hold at once?
The current row shows Rust-CPT-TEST offline; the last response was 15 hours ago. Over the last seven days it averaged 0 players and peaked at 2. Peak hour in the last 48 hours: 22:00 UTC, mean 1 players.
Server data
How well does Rust-CPT-TEST perform?
Server fps over the last 48 hours averages 231; the floor is 77. The entity count peaked at 54,767, covering buildings, deployables and the rest of the world. Memory peaked at 2,360 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on Rust-CPT-TEST?
Rust network protocol 2635 and build 168909 on Linux is what Rust-CPT-TEST runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Rust-CPT-TEST, and is it up?
Rust-CPT-TEST is offline at this refresh; the last response came 15 hours ago. Count back 8 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 81 of 168, 48%. The first row Rust Data holds for it is dated 20 September 2026.
Where does Rust-CPT-TEST sit?
There is no region published for Rust-CPT-TEST. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 102.135.245.21:29031 is its address.
Settings and map
Which settings and rules does Rust-CPT-TEST run?
The name Rust-CPT-TEST carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and 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 plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Rust-CPT-TEST loaded?
Size 3,000, seed 19845: the procedural map on Rust-CPT-TEST, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does Rust-CPT-TEST wipe, and on what schedule?
Rust-CPT-TEST wipes on no fixed rhythm, so there is nothing to predict. 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 8 days 1 hours ago, and that is the one in play.
What is wipe day on Rust-CPT-TEST like?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags and filters
Which lists on Rust Data hold Rust-CPT-TEST, and which filters?
The Rust Data lists that Rust-CPT-TEST fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on Rust-CPT-TEST hold?
Read by the game's server browser, the tags Rust-CPT-TEST publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 to join Rust-CPT-TEST?
In Rust, F1 opens the console: type client.connect 102.135.245.21:29031. Launch Rust on this page does the same by opening the game through Steam and connecting.