Offline 162.33.16.50:19900 checked 45d ago
pogfrog oxidation
Connect
srv = rust.server("162.33.16.50:19903")
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 bestWipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. # The 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
- 162.33.16.50:19900
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 12 Sep 2026, 08:55 UTC
- hostname
- –
- first seen
- 13 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 85/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 237/700 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 31/1000 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 74 on average | 116/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 68 on average | 383/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 29.10 | EU · groups of 16+ · monthly · 66 on average | 356/1000 |
Quick answers
From the figures on this page.
Population
How does pogfrog oxidation compare in the rankings?
Over the last seven days pogfrog oxidation sits at #12,910 on player hours, in the top – of ranked servers.
What population does pogfrog oxidation carry?
The current row shows pogfrog oxidation offline; the last response was 45 days 16 hours ago.
Server facts
What is the Rust version on pogfrog oxidation?
Version Rust network protocol 2633 and build 163794 on Linux is reported by pogfrog oxidation. Steam updates your game for you, but the protocol must match to join.
How reliable is pogfrog oxidation, and is it online now?
The latest sample has pogfrog oxidation offline, with a last sighting 45 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 13 September 2026.
Which location does pogfrog oxidation run from?
There is no region published for pogfrog oxidation. Rust Data does not look up where the machine stands; it shows where a server says it is. 162.33.16.50:19900 is its address.
Settings and map
What rules and settings are recorded for pogfrog oxidation?
The name pogfrog oxidation carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Vanilla, by its own description: facepunch's stock game, with rates, kits and rules untouched. VAC, Valve's anti-cheat, is enabled.
Which map has pogfrog oxidation selected?
The game generates its map: procedural, on pogfrog oxidation.
Wipes and dates
When does pogfrog oxidation wipe, and how often?
The next wipe for pogfrog oxidation is an estimate, drawn from the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 47 days 6 hours ago. A monthly wipe schedule is published in its tags.
Tags and filters
Which lists on Rust Data hold pogfrog oxidation, and which filters?
These Rust Data lists include pogfrog oxidation: Modded Rust servers. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on pogfrog oxidation?
The game's server browser reads these tags from pogfrog oxidation: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): 40 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163794 (Build): Build number: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. 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 into pogfrog oxidation?
Enter client.connect 162.33.16.50:19900 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.