Offline 146.59.45.106:28315 checked 2d ago
oxide-test
Connect
srv = rust.server("146.59.45.106:28317")
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 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 17:33 UTC2d ago | NaN | NaN | running | 0 |
| 1 | Sun 25 Oct, 19:20 UTC3d ago | 0 | NaN | 1.9 days | 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
- 146.59.45.106:28315
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 17:33 UTC
- hostname
- –
- first seen
- 24 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 · 151 on average | 127/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 195/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 74/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 222/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Player counts
How does oxide-test compare in the rankings?
Player hours over seven days put oxide-test at #15,310, in the top 69% of the ranked set.
How many players does oxide-test hold at once?
oxide-test returns no live count at this refresh, having last been seen 2 days 1 hours ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does oxide-test run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by oxide-test. The protocol has to match before you can join, and Steam does the updating.
Is oxide-test up, and what does its uptime show?
The latest sample has oxide-test offline, with a last sighting 2 days 1 hours ago. 2 of 96 hours up over the last 4 full days, or 2%. Its earliest recorded date in Rust Data is 24 October 2026.
Which location does oxide-test run from?
No region is published by oxide-test. Rust Data does not look up where the machine stands; it shows where a server says it is. 146.59.45.106:28315 is its address.
Map and rules
Which settings and rules does oxide-test run?
No gather rate appears in the name: oxide-test. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has oxide-test loaded?
The game generates its map: procedural, on oxide-test.
Wipe schedule
When does oxide-test wipe, and on what schedule?
The record for oxide-test 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 2 days 1 hours ago, and that is the one in play.
What is wipe day on oxide-test like?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which Rust Data filters and lists contain oxide-test?
On Rust Data, oxide-test appears in these lists: 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; Last wipe: In the last 3 days.
Which meanings do the tags on oxide-test hold?
Read by the game's server browser, the tags oxide-test publishes are: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): 4 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into oxide-test?
In Rust, F1 opens the console: type client.connect 146.59.45.106:28315. Launch Rust on this page does the same by opening the game through Steam and connecting.