Offline 76.169.105.214:28015 checked 36d ago
APtestServer
Connect
srv = rust.server("76.169.105.214:28016")
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 22 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 best
Top 57% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 22 Sep, 16:50 UTC36d ago | 1 | NaN | running | 1 |
| 1 | Sun 20 Sep, 23:58 UTC38d ago | 1 | NaN | 1.7 days | 1 |
# 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
2000 · seed 1234
- map
- Procedural Map
- size
- 2000
- seed
- 1234
Server
srv.info()- address
- 76.169.105.214:28015
- region
- –
- max players
- 250
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Sep 2026, 17:26 UTC
- hostname
- –
- first seen
- 17 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 · 149 on average | 170/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 75/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 16/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 83 on average | 252/700 |
Quick answers
From the figures on this page.
Player counts
How does APtestServer compare in the rankings?
Player hours over seven days put APtestServer at #13,225, in the top 57% of the ranked set.
What population does APtestServer carry?
Offline now for APtestServer, with the last sample 36 days 10 hours ago.
Server data
What is the Rust version on APtestServer?
Rust network protocol 2633 and build 165217 on Windows is what APtestServer runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is APtestServer, and is it online now?
The latest sample has APtestServer offline, with a last sighting 36 days 10 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 17 September 2026.
Where does APtestServer sit?
There is no region published for APtestServer. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 76.169.105.214:28015.
Map and rules
Which settings and rules does APtestServer run?
The name APtestServer carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are 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 APtestServer selected?
The game generates the map on APtestServer: procedural, size 2,000, seed 1234. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
On what schedule does APtestServer wipe?
Too few wipes are on record for APtestServer to reveal its 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 36 days 19 hours ago.
What is wipe day on APtestServer like?
Across recent wipes the busiest point averaged 1 players. 1 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold APtestServer, and which filters?
These Rust Data lists include APtestServer: 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.
How should you read the server tags on APtestServer?
Read by the game's server browser, the tags APtestServer publishes are: gmrust (Game mode): Survival play, standard Rust; mp250 (Max players): The server lists 250 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
Connecting
What is the way into APtestServer?
In Rust, F1 opens the console: type client.connect 76.169.105.214:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.