Statistical profileOffline
RF Rework Test (local)
86.85.213.120:28015 checked 2d ago
Connect to this server
1. Main points
Players now
0/ 10
0% full
7-day average
0
peak 1
Rank
#14,221
top 64%
Last wipe
3d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 10 slots.
- Over the last seven days it averaged 0 players, with a peak of 1.
- It ranks #14,221 of all ranked servers, the top 64%, on player hours over the last seven days.
- Its current map went up 3d ago.
2. Players
Figure 1: Players on RF Rework Test (local)
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 64% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipe-day peak
1
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 26 Oct, 00:16 UTC3d ago | 1 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of RF Rework Test (local)
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of RF Rework Test (local)
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 150 on average | 105 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 136 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 47 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19 / 1000 |
10. Quick answers
From the figures on this page.
Wipe schedule
On what schedule are wipes carried out on RF Rework Test (local)?
Too few wipes of RF Rework Test (local) are on record to establish its rhythm. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. 3 days 8 hours have passed since this world was made.
How is wipe day run on RF Rework Test (local)?
An average of 1 players attended at peak across recent wipes. On the latest wipe, 0 hours passed before the crowd peaked.
Server record
What does the record show for the uptime and current status of RF Rework Test (local)?
Last seen 2 days 19 hours ago, RF Rework Test (local) is offline in this release. A total of 0 of 48 hours were up over 2 full days, which is 0% of the time. The first sighting of it by Rust Census was on 26 October 2026.
Which location does RF Rework Test (local) run from?
No region is published by RF Rework Test (local). No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. 86.85.213.120:28015 is its address.
Which Rust version is RF Rework Test (local) running?
The version in use on RF Rework Test (local) is Rust network protocol 2635 and build 168909 on Windows. To join, your game has to be on the same protocol; Steam handles the update.
Player figures
What population has been recorded on RF Rework Test (local)?
RF Rework Test (local) is offline at present; its last recording was 2 days 19 hours ago. Averaged over seven days: 0 players, with a peak of 1.
How does RF Rework Test (local) compare with other servers in the rankings?
The rank for RF Rework Test (local) is #14,221 on seven-day player hours, in the top 64% of ranked servers.
Tags, lists
Which Rust Census filters and lists cover RF Rework Test (local)?
Included in these Rust Census lists is RF Rework Test (local): Modded Rust servers, counted. 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.
Which meanings do the tags on RF Rework Test (local) carry?
gmrust (Game mode): The game mode is standard survival as Rust runs it; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): To connect, your game version must match protocol 2635; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game on this modded server are the tags RF Rework Test (local) publishes, and the game's server browser reads them. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Settings and map
What map is listed for RF Rework Test (local)?
The game generates the procedural map on RF Rework Test (local).
What settings and rules have been listed for RF Rework Test (local)?
No gather rate is given in the name of RF Rework Test (local). The default applies: groups are capped at 8 players. survival is the game mode recorded, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings alter the game. Plugins on it number Oxide. Anti-cheat is active: VAC, Valve's system, is on.
Connecting
How can you connect to RF Rework Test (local)?
Enter client.connect 86.85.213.120:28015 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp10 | Max players 10 slots are available. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol To connect, your game version must match protocol 2635. |
cs168909 | Build The server runs game build 168909. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code No region code is set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded Plugins or settings alter the game on this modded server. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.