box64-benchmark
Offline 141.145.202.158:28015 checked 41d ago
Measurements
Players
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
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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.
Quick answers
Player counts
How does box64-benchmark rank against other Rust servers?
By player hours over the last seven days, box64-benchmark places at #15,523, within the top – of ranked servers.
How busy is box64-benchmark?
We have no live count for box64-benchmark right now. It was last seen 41 days 9 hours ago.
Tags
What do the server tags on box64-benchmark mean?
The game's server browser reads the tags box64-benchmark publishes: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default limit; v2633 (Protocol): The protocol is 2633; a different version will not connect; cs163794 (Build): Game build: 163794; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): The region code is left blank; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): This server appears under Modded because plugins or settings alter the game. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include box64-benchmark?
On Rust Population, box64-benchmark is filed under these lists: Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more and it will show up.
Wipe schedule
What is the wipe schedule on box64-benchmark?
Its rhythm cannot be told yet: too few of box64-benchmark's wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. The world it runs now dates from 41 days 10 hours ago.
Map and rules
Which map does box64-benchmark run?
box64-benchmark uses a map the game generates: procedural.
What are the rules and settings on box64-benchmark?
Nothing in box64-benchmark's name says how gather works. Eight players per group is the default, and it applies here. This server runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players is allowed. The server browser files it under Modded, where plugins or settings alter the game. The plugins it runs are Oxide. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does box64-benchmark run?
The setup is Rust network protocol 2633 and build 163794 on Linux for box64-benchmark. Your game needs the same protocol to join; Steam takes care of updating it.
Is box64-benchmark online, and how reliable is it?
We last saw box64-benchmark 41 days 9 hours ago, and it is offline now. Over the last 7 full days, 0 of 168 hours were online, or 0%. On 17 September 2026, Rust Population saw it for the first time.
Where is box64-benchmark located?
Nothing published by box64-benchmark states a region. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 141.145.202.158:28015.
How to join
How do I join box64-benchmark?
Open the console with F1 in Rust and enter client.connect 141.145.202.158:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.