Offline 102.43.212.226:28015 checked 44d ago
oxide test server
Connect
srv = rust.server("102.43.212.226: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. 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
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 | Sun 13 Sep, 21:56 UTC45d ago | 1 | NaN | running | 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
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 102.43.212.226:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 13 Sep 2026, 09: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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 71/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 109/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 37/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 10/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does oxide test server rank?
Over the last seven days oxide test server sits at #12,835 on player hours, in the top – of ranked servers.
How many players does oxide test server hold at once?
The current row shows oxide test server offline; the last response was 44 days 14 hours ago.
Server data
What Rust version does oxide test server run?
The build is Rust network protocol 2633 and build 163493 on Windows, run by oxide test server. The protocol has to match before you can join, and Steam does the updating.
Is oxide test server up, and what does its uptime show?
oxide test server is offline at this refresh; the last response came 44 days 14 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does oxide test server run from?
For oxide test server, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 102.43.212.226:28015 is its address.
Settings and map
What rules and settings are recorded for oxide test server?
No gather rate appears in the name: oxide test server. 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. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe data
On what schedule does oxide test server wipe?
Too few wipes are on record for oxide test server to reveal its 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 45 days 21 hours ago, and that is the one in play.
On oxide test server, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in.
Tags, lists
Which lists on Rust Data hold oxide test server, and which filters?
On Rust Data, oxide test server appears in these lists: 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.
How should you read the server tags on oxide test server?
Read by the game's server browser, the tags oxide test server publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163493 (Build): The server runs build 163493; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join oxide test server?
The manual route: launch Rust, F1, then client.connect 102.43.212.226:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.