Online 51.38.155.207:29378 checked 13m ago
workinbio.
Connect
srv = rust.server("51.38.155.207:29379")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 18:31 UTC7d ago | 1 | NaN | running | 0 |
| 1 | Thu 1 Oct, 18:07 UTC FW28d ago | 3 | halved by day 9 | 21 days | 2 |
| 2 | Wed 30 Sep, 21:41 UTC29d ago | 3 | NaN | 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.
display(srv.map, srv.info())Map
1500 · seed 50000
- map
- Procedural Map
- size
- 1500
- seed
- 50000
Server
srv.info()- address
- 51.38.155.207:29378
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 18:31 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 4/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 45/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 45/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 207/215 |
Quick answers
From the figures on this page.
Population data
What position does workinbio. take in the server rankings?
Player hours over seven days put workinbio. at #4,408, in the top 20% of the ranked set.
How full does workinbio. run?
Current row: 0 players on workinbio., against 40 slots. Over the last seven days it averaged 0 players and peaked at 4. Averaged by hour over 48 hours, 19:00 UTC is the busiest, at 3 players.
Server facts
What does performance look like on workinbio.?
Averaged over 48 hours: 238 server fps, never under 209. Buildings, deployables and all else in the world took the count as high as 8,428 entities. A high of 3,053 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is workinbio. on?
Version Rust network protocol 2635 and build 168909 on Linux is reported by workinbio.. Steam updates your game for you, but the protocol must match to join.
How reliable is workinbio., and is it up?
workinbio. reports itself online at the current refresh. A restart about 3 days 12 hours ago is what its reported uptime implies. Uptime of 85% across the last 7 full days: 143 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Where does workinbio. sit?
No region is published by workinbio.. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 51.38.155.207:29378 is its address.
Rules, settings, map
Which settings and rules does workinbio. run?
The name workinbio. carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC off.
What is the map on workinbio.?
The game generates the map on workinbio.: procedural, size 1,500, seed 50000. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
On what schedule does workinbio. wipe?
No next wipe can be predicted for workinbio., which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 7 days 5 hours ago.
On workinbio., what happens on wipe day?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 9.
Tags, lists
Which lists on Rust Data hold workinbio., and which filters?
The Rust Data lists that workinbio. fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on workinbio.?
These tags are published by workinbio. and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): Slot count: 40; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into workinbio.?
Enter client.connect 51.38.155.207:29378 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.