Online 5.83.170.102:11200 checked 12m ago
No life required
Connect
srv = rust.server("5.83.170.102:11201")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 23 Oct. 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
2500 · seed 6738
- map
- Procedural Map
- size
- 2500
- seed
- 6738
Server
srv.info()- address
- 5.83.170.102:11200
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 22:37 UTC
- hostname
- –
- first seen
- 23 Oct 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 · 163 on average | 48/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 61/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 58/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 14/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does No life required rank?
Player hours over seven days put No life required at #15,409, in the top 69% of the ranked set.
How full does No life required run?
Current row: 0 players on No life required, against 50 slots. Over the last seven days it averaged 0 players.
Server facts
How well does No life required perform?
Server fps over the last 48 hours averages 10; the floor is 10. The entity count peaked at 31,609, covering buildings, deployables and the rest of the world. Memory peaked at 1,503 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does No life required run?
Rust network protocol 2635 and build 168909 on Windows is what No life required runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is No life required, and is it online now?
No life required reports itself online at the current refresh. Count back 18 hours from its reported uptime to get the last restart. Over the last 4 full days the hours up number 72 of 96, 75%. Rust Data logged it first on 23 October 2026.
Which location does No life required run from?
For No life required, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 5.83.170.102:11200.
Settings and map
Which settings and rules does No life required run?
No gather rate appears in the name: No life required. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on No life required?
Size 2,500, seed 6738: the procedural map on No life required, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does No life required wipe, and on what schedule?
A rhythm cannot be read from the wipes of No life required on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 4 days 1 hours ago.
Lists and tags
Which lists on Rust Data hold No life required, and which filters?
On Rust Data, No life required appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on No life required?
The game's server browser reads these tags from No life required: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join No life required?
Enter client.connect 5.83.170.102:11200 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.