Rust HeatmapInfrared · players
IR live Players103,751 Servers11,890 Warm3,994 Fresh wipes · 3h411 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–40° · slots

workinbio.

Online 51.38.155.207:29378 checked 10m ago

moddedoxide
Sp1 · players now 0/ 40
0% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 4°
Tue 19:00flare: a wipe in that hourThu 17:00
0
7-day average
peak 4
#4,365
rank
top 20%
7d ago
last wipe
no schedule published
–
next wipe
no rhythm it keeps
UTC checked 10m ago

Li2Players

AveragePeak
0123419:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Li3Server performance

010020030040019:0004:0013:0023:0008:0017:00

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Li4Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 20% of all ranked servers. Ranked on player hours over the last seven days.

Bx1Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

10.9 days
usual gap
between real wipes
0%
on rhythm
of its recent wipes
2
wipe-day peak
players, last three wipes
0%
crowd held
else halves by day 9

The first 48 hours of its last wipes

Thu 22 OctThu 1 OctWed 30 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 18:31 UTC7d ago 1 – running 0
Thu 1 Oct, 18:07 UTC FW28d ago 3 halved by day 9 21 days 2
Wed 30 Sep, 21:41 UTC28d ago 3 – 0.9 days 1

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 · 151 on average
126 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
128 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 118 on average
197 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 95 on average
77 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10
EU · groups of 16+ · monthly · 89 on average
226 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 84 on average
349 / 350

LogQuick answers

from the figures on this page

Wipe schedule

What does wipe day look like on workinbio.?

The average peak across its recent wipes is 2 players. 0 hours into the latest wipe, player numbers topped out. Above half the peak until the next wipe: that held in 0% of its recent wipes. It fell below half by day 9 when it did not hold.

What is the wipe schedule on workinbio.?

Wipes come at irregular times on workinbio., so no next wipe can be predicted. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world in play now was made 7 days ago.

Player counts

How busy is workinbio.?

The current population of workinbio. is 0, against 40 slots. A seven-day average of 0 players, with a peak of 4. Its busiest point in the last 48 hours was 19:00 UTC, averaging 3 players.

How does workinbio. rank against other Rust servers?

Player hours over seven days put workinbio. at #4,365, in the top 20% of ranked servers.

Rules and settings

Which map does workinbio. run?

workinbio. runs a procedural map of size 1,500 with seed 50000, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map.

What are the rules and settings on workinbio.?

The name workinbio. does not specify a gather rate. 8 players is the default group size, and that is the limit here. survival is the game mode, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. Plugins or settings change the game, and it is listed under Modded in the server browser. Oxide plugins run on this server. The server has VAC, Valve's anti-cheat, turned off.

Server details

Which version of Rust does workinbio. run?

The build on workinbio. is Rust network protocol 2635 and build 168909, running on Linux. To join, your game must match the protocol; Steam handles the update.

Is workinbio. online, and how reliable is it?

Right now workinbio. shows as online. The uptime it reports puts the last restart at about 3 days 6 hours ago. 149 of 168 hours up over the last 7 full days, which is 89%. The first record of it on Rust Heatmap is 13 September 2026.

Where is workinbio. located?

Nothing about a region comes from workinbio.. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. 51.38.155.207:29378 is its address.

Does workinbio. run smoothly?

Average server fps over the last 48 hours was 237; it never dropped below 209. Entities peaked at 8,428, counting buildings, deployables and all the rest of the world. The highest memory use was 3,053 MB. Players feel lag when fps falls and the entity count climbs.

Lists and filters

Which Rust Heatmap lists and filters include workinbio.?

Modded Rust servers, by live population are the Rust Heatmap lists that workinbio. fits. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

What do the server tags on workinbio. mean?

These are the tags workinbio. publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp40 (Max players): The slot count is 40; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): The game build here is 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by settings or plugins, so it sits under Modded. 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 workinbio.?

Press F1 in Rust to open the console, then enter client.connect 51.38.155.207:29378. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.

KeyServer tags

what each one means

Published as mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust form.
mp40
Max players The slot count is 40.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol The server runs game protocol 2635, so your game has to match it.
cs168909
Build The game build here is 168909.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code A region code is not set.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded The game is changed by settings or plugins, so it sits under Modded.

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.