Offline 197.46.158.203:28015 checked 28d ago
oxide test server
Connect
srv = rust.server("197.46.158.203: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 bestTop 70% 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 197.46.158.203:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 02:46 UTC
- hostname
- –
- first seen
- 30 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 · 155 on average | 159/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 182/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 93/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 40/1000 |
Quick answers
From the figures on this page.
Player counts
What position does oxide test server take in the server rankings?
Rank #16,839 on seven-day player hours for oxide test server, within the top 70% of all ranked servers.
How full does oxide test server run?
oxide test server returns no live count at this refresh, having last been seen 28 days 1 hours ago.
Server data
What is the Rust version on oxide test server?
The build is Rust network protocol 2634 and build 166289 on Windows, run by oxide test server. Steam updates your game for you, but the protocol must match to join.
How reliable is oxide test server, and is it online now?
The latest sample has oxide test server offline, with a last sighting 28 days 1 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 30 September 2026.
Where does oxide test server sit?
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. You can reach it at 197.46.158.203:28015.
Settings and map
Which settings and rules does oxide test server run?
No gather rate appears in the name: oxide test server. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Wipe data
On what schedule does oxide test server wipe?
A rhythm cannot be read from the wipes of oxide test server on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 32 days 6 hours ago.
Lists and tags
Which lists on Rust Data hold oxide test server, and which filters?
These Rust Data lists include oxide test server: 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 oxide test server?
Read by the game's server browser, the tags oxide test server publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166289 (Build): Recorded game build: 166289; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is 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
How can I connect to oxide test server?
In Rust, F1 opens the console: type client.connect 197.46.158.203:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.