Rust HeatmapInfrared · players
IR live Players38,590 Servers11,700 Warm2,938 Fresh wipes · 3h91 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–10° · slots

box64-benchmark

Offline 141.145.202.158:28015 checked 41d ago

moddedoxide
Sp1 · players now 0/ 10
0% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
0
7-day average
peak –
#15,523
rank
no region published
41d ago
last wipe
no schedule published
–
next wipe
no wipe seen yet
UTC checked 41d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

Li3Server performance

This server has not answered a direct query in the last 48 hours.

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.

Li4Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep

Bx1Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers 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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 155 on average
27 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
133 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 117 on average
32 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 93 on average
11 / 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
0 / 1000

LogQuick answers

from the figures on this page

Wipe day

What is the wipe schedule on box64-benchmark?

box64-benchmark has too few wipes on record yet for its rhythm to show. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world it runs now dates from 41 days 23 hours ago.

Population

How busy is box64-benchmark?

Last seen 41 days 23 hours ago, box64-benchmark is offline at the moment.

How does box64-benchmark rank against other Rust servers?

The top – of ranked servers includes box64-benchmark, at #15,523 for player hours over the last seven days.

Settings and rules

Which map does box64-benchmark run?

box64-benchmark runs a procedural map, which the game generates.

What are the rules and settings on box64-benchmark?

The name box64-benchmark does not specify a gather rate. Groups can contain up to 8 players, the default in the game. The server runs survival, gather, build and raid in the standard game. Combat between players and raiding are both possible. Plugins or settings change the game, and it is listed under Modded in the server browser. Oxide plugins run on this server. Anti-cheat: Valve's VAC is on.

About the server

Which version of Rust does box64-benchmark run?

The build on box64-benchmark is Rust network protocol 2633 and build 163794, running on Linux. To join, your game must match the protocol; Steam handles the update.

Is box64-benchmark online, and how reliable is it?

box64-benchmark is down just now; the last sighting was 41 days 23 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. It first appears in Rust Heatmap records on 17 September 2026.

Where is box64-benchmark located?

A region is not published for box64-benchmark. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. You can reach it at 141.145.202.158:28015.

Lists and filters

Which Rust Heatmap lists and filters include box64-benchmark?

These Rust Heatmap lists include box64-benchmark: Modded Rust servers, by live population. You will find it under these filters 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?

gmrust (Game mode): Rust survival, standard rules; mp10 (Max players): Slot count: 10; ts8 (Group limit): The game default applies: 8 per team at most; v2633 (Protocol): Your game must match protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Listed as Modded, since settings or plugins change the game are the tags box64-benchmark publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.

Connect

How do I join box64-benchmark?

To join by console, open it with F1 in Rust and enter client.connect 141.145.202.158:28015. Or press Launch Rust on this page, which connects you through Steam.

KeyServer tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode Rust survival, standard rules.
mp10
Max players Slot count: 10.
ts8
Group limit The game default applies: 8 per team at most.
v2633
Protocol Your game must match protocol 2633 to get in.
cs163794
Build Build 163794.
ptrak
Networking Standard game networking here, which is RakNet.
$r?
Region code The region code is blank.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Listed as Modded, since settings or plugins change the game.

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.