Offline 136.49.50.202:28515 checked 8d ago
o13 test
Connect
srv = rust.server("136.49.50.202:28516")
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 best
Top 69% 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
- 136.49.50.202:28515
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 21:35 UTC
- hostname
- –
- first seen
- 19 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 · 155 on average | 173/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 179/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 137/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 15/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 53/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does o13 test rank?
Player hours over seven days put o13 test at #15,326, in the top 69% of the ranked set.
What population does o13 test carry?
The current row shows o13 test offline; the last response was 8 days 13 hours ago.
About the server
What is the Rust version on o13 test?
Rust network protocol 2634 and build 167781 on Linux is what o13 test runs. The protocol has to match before you can join, and Steam does the updating.
Is o13 test up, and what does its uptime show?
The latest sample has o13 test offline, with a last sighting 8 days 13 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 19 October 2026.
Where does o13 test sit?
There is no region published for o13 test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 136.49.50.202:28515.
Map and rules
Which settings and rules does o13 test run?
The name o13 test carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
What is the map on o13 test?
The game generates its map: procedural, on o13 test.
Wipe schedule
When does o13 test wipe, and how often?
A rhythm cannot be read from the wipes of o13 test on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 8 days 13 hours ago.
Lists and tags
Which Rust Data filters and lists contain o13 test?
The Rust Data lists that o13 test fits are: 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.
How should you read the server tags on o13 test?
These tags are published by o13 test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join o13 test?
In Rust, F1 opens the console: type client.connect 136.49.50.202:28515. Launch Rust on this page does the same by opening the game through Steam and connecting.