Offline 146.59.45.106:28045 checked 5d ago
OxideTest
Connect
srv = rust.server("146.59.45.106:28047")
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
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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 146.59.45.106:28045
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 12:46 UTC
- hostname
- –
- first seen
- 23 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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does OxideTest rank?
Player hours over seven days put OxideTest at #15,426, in the top 69% of the ranked set.
How full does OxideTest run?
OxideTest returns no live count at this refresh, having last been seen 5 days 5 hours ago. Over the last seven days it averaged 0 players.
About the server
What Rust version does OxideTest run?
The build is Rust network protocol 2634 and build 167781 on Windows, run by OxideTest. Steam updates your game for you, but the protocol must match to join.
Is OxideTest up, and what does its uptime show?
The latest sample has OxideTest offline, with a last sighting 5 days 5 hours ago. Uptime of 0% across the last 4 full days: 0 hours of 96. Its earliest recorded date in Rust Data is 23 October 2026.
Which location does OxideTest run from?
No region is published by OxideTest. Rust Data does not look up where the machine stands; it shows where a server says it is. 146.59.45.106:28045 is its address.
Rules, settings, map
Which settings and rules does OxideTest run?
You will not find a gather rate in the string OxideTest. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has OxideTest loaded?
OxideTest runs a procedural map, which the game generates.
Wipes and dates
On what schedule does OxideTest wipe?
A rhythm cannot be read from the wipes of OxideTest on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 5 days 5 hours ago, and that is the one in play.
Tags, lists
Which lists on Rust Data hold OxideTest, and which filters?
On Rust Data, OxideTest 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 week.
Which meanings do the tags on OxideTest hold?
Read by the game's server browser, the tags OxideTest publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join OxideTest?
Enter client.connect 146.59.45.106:28045 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.