box64-benchmark
Offline 141.145.202.158:28015 checked 42d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 31/500
- 122/100
- 42/225
- 11/700
- 3/200
- 1/1000
Quick answers
from the figures on this pageWipe timing
How often does box64-benchmark wipe, and when?
The rhythm of box64-benchmark's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 42 days 1 hours ago.
Tags
How should you read the tags on box64-benchmark?
These are the tags box64-benchmark publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show box64-benchmark?
Rust Metrics lists featuring box64-benchmark: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does box64-benchmark sit in the rankings?
Ranking for box64-benchmark: #15,523 on seven-day player hours, top – of all ranked servers.
How full does box64-benchmark get?
Reading for box64-benchmark: offline at this moment; last seen 42 days ago.
Operator and location
Where does box64-benchmark sit?
Reading: location. box64-benchmark gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 141.145.202.158:28015.
What Rust version is box64-benchmark on?
Reading: box64-benchmark, Rust network protocol 2633 and build 163794, Linux. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on box64-benchmark, and is it online?
box64-benchmark reports offline. The last reading came 42 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 17 September 2026, recorded by Rust Metrics.
Rules and settings
How is box64-benchmark configured, and what rules are in force?
No gather rate appears in the name: box64-benchmark. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.
What map is box64-benchmark on?
The game generates a procedural map for box64-benchmark.
How to join
What do you do to join box64-benchmark?
Press F1 in Rust and enter client.connect 141.145.202.158:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.