Offline 162.244.80.220:28015 checked 4d ago
Oxide Studio · Development
Connect
srv = rust.server("162.244.80.220:28017")
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 · 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 | Mon 19 Oct, 16:52 UTC9d 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 162.244.80.220:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 06:27 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 · 156 on average | 4/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 50/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 38/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Oxide Studio · Development rank?
Player hours over seven days put Oxide Studio · Development at #15,349, in the top 69% of the ranked set.
What population does Oxide Studio · Development carry?
Oxide Studio · Development returns no live count at this refresh, having last been seen 4 days 23 hours ago. Over the last seven days it averaged 0 players.
About the server
What Rust version does Oxide Studio · Development run?
Version Rust network protocol 2634 and build 167781 on Windows is reported by Oxide Studio · Development. The protocol has to match before you can join, and Steam does the updating.
How reliable is Oxide Studio · Development, and is it up?
Offline now for Oxide Studio · Development, last seen 4 days 23 hours ago. 9 of 168 hours up over the last 7 full days, or 5%. The first row Rust Data holds for it is dated 16 October 2026.
In which location is Oxide Studio · Development hosted?
There is no region published for Oxide Studio · Development. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 162.244.80.220:28015.
Map and rules
What rules and settings are recorded for Oxide Studio · Development?
The name Oxide Studio · Development carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Oxide Studio · Development selected?
Oxide Studio · Development runs a procedural map, which the game generates.
Wipes and dates
On what schedule does Oxide Studio · Development wipe?
The record for Oxide Studio · Development holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 12 days 17 hours ago, and that is the one in play.
What is wipe day on Oxide Studio · Development like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 1 hours after it began.
Tags and filters
Which lists on Rust Data hold Oxide Studio · Development, and which filters?
These Rust Data lists include Oxide Studio · Development: Modded Rust servers. It appears under these filters 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.
How should you read the server tags on Oxide Studio · Development?
The game's server browser reads these tags from Oxide Studio · Development: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Oxide Studio · Development?
Enter client.connect 162.244.80.220:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.