Offline 86.85.213.120:28015 checked 2d ago
RF Rework Test (local)
Connect
srv = rust.server("86.85.213.120: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 bestTop 64% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 00:16 UTC3d 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
- 86.85.213.120:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 00:16 UTC
- hostname
- –
- first seen
- 26 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 | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 93/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 31/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Population
What position does RF Rework Test (local) take in the server rankings?
Player hours over seven days put RF Rework Test (local) at #14,217, in the top 64% of the ranked set.
How full does RF Rework Test (local) run?
The current row shows RF Rework Test (local) offline; the last response was 2 days 17 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
What Rust version does RF Rework Test (local) run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by RF Rework Test (local). The protocol has to match before you can join, and Steam does the updating.
How reliable is RF Rework Test (local), and is it online now?
RF Rework Test (local) is offline at this refresh; the last response came 2 days 17 hours ago. Uptime of 0% across the last 2 full days: 0 hours of 48. Rust Data logged it first on 26 October 2026.
In which location is RF Rework Test (local) hosted?
There is no region published for RF Rework Test (local). The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 86.85.213.120:28015 is its address.
Rules, settings, map
Which rules apply on RF Rework Test (local), and what settings?
The name RF Rework Test (local) carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are 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 RF Rework Test (local) loaded?
The game generates its map: procedural, on RF Rework Test (local).
Wipe schedule
When does RF Rework Test (local) wipe, and how often?
Too few wipes are on record for RF Rework Test (local) to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 3 days 6 hours ago.
On RF Rework Test (local), what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does RF Rework Test (local) appear among Rust Data lists and filters?
These Rust Data lists include RF Rework Test (local): 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 week.
How should you read the server tags on RF Rework Test (local)?
Read by the game's server browser, the tags RF Rework Test (local) publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is 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.
Join steps
What is the way into RF Rework Test (local)?
The manual route: launch Rust, F1, then client.connect 86.85.213.120:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.