box64-benchmark
Offline 141.145.202.158:28015 checked 41d ago
Vital stats
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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Lists and tags
Which Rust Pop Watch lists and filters include box64-benchmark?
These Rust Pop Watch lists include box64-benchmark: Modded Rust servers, live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What do the server tags on box64-benchmark mean?
The game's server browser picks up these tags from box64-benchmark: gmrust (Game mode): Plain vanilla Rust survival, nothing bolted on; mp10 (Max players): It has 10 slots; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): The game protocol is 2633, so your client has to match it to join; cs163794 (Build): The game build is 163794; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region is listed; ^o (Oxide): Oxide (uMod), a plugin framework, is what it runs; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You'll find players now, queue length and world creation time in the tags, printed at the top of this page.
Player counts
How does box64-benchmark rank against other Rust servers?
A seven-day player-hours placing of #15,523 puts box64-benchmark in the top – of all ranked servers.
How many players are on box64-benchmark right now?
Offline now, box64-benchmark was last spotted 41 days 16 hours ago.
Server details
Is box64-benchmark online, and how reliable is it?
Down at the moment: box64-benchmark was last seen 41 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours in total. It came to Rust Pop Watch's attention on 17 September 2026.
Where is box64-benchmark located?
No region is published by box64-benchmark. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. You'll find it at 141.145.202.158:28015.
Which Rust version is box64-benchmark on?
On Linux, box64-benchmark runs Rust network protocol 2633 and build 163794. Joining requires your game to match the protocol, which Steam updates for you.
The wipe schedule
What is the wipe schedule on box64-benchmark?
box64-benchmark's rhythm stays hidden while so few of its wipes are on record. On Thursday 5 November at 19:00 UTC the force wipe arrives, and every Rust server wipes with it at monthly intervals. Its current world has been live for 41 days 17 hours.
Map and rules
Which map does box64-benchmark run?
The map on box64-benchmark is procedural, made by the game.
What are the rules and settings on box64-benchmark?
No gather rate appears in the name of box64-benchmark. Eight players per group: that is the game's default. survival is the game mode, gather, build and raid, as standard. Fighting and raiding between players is allowed. Plugins or settings alter the game, and the browser lists it as Modded. Oxide plugins power it. The VAC anti-cheat from Valve is on.
Join up
How do I join box64-benchmark?
The console method: start Rust, press F1, and type client.connect 141.145.202.158:28015. Launch Rust on this page is another way, opening Rust via Steam and connecting.