namju solo /duo
Offline 157.85.88.84:24986 checked 30d ago
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| 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
- 268/ 275
- 583/ 600
- 506/ 575
- 138/ 200
- 408/ 325
- 197/ 200
Quick answers
Tags and listings
Where does namju solo /duo appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry namju solo /duo are: Rust community servers, going deep. You can find it on the server list by these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on namju solo /duo?
gmrust (Game mode): Survival, as standard Rust does it; mp40 (Max players): There are 40 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs164530 (Build): The build number is 164530; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code — that is the tag list namju solo /duo puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What location is namju solo /duo in?
namju solo /duo does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 157.85.88.84:24986.
Is namju solo /duo up, and how often does it stay online?
The server namju solo /duo is not reachable at the moment; the last sighting was 30 days 19 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 17 September 2026.
What is the Rust version for namju solo /duo?
Rust network protocol 2633 and build 164530 is what namju solo /duo runs, on Linux. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
When does namju solo /duo wipe?
namju solo /duo's rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 30 days 20 hours ago.
Map and rules
Which rules and settings is namju solo /duo running?
Its name does not state a gather rate for namju solo /duo. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser lists it under Community, making it a community server. VAC is on: Valve's anti-cheat is active.
Which map is active on namju solo /duo?
namju solo /duo uses a procedural map of size 2,500 with seed 500000, made by the game. You can see it on RustMaps from this page, since the same size and seed produce the same map.
Population
How many players are on namju solo /duo?
The last sighting of namju solo /duo was 30 days 19 hours ago; it is offline right now.
What position does namju solo /duo hold in the server rankings?
For player hours in the last seven days, namju solo /duo ranks #15,116, within the top – of ranked servers.
Getting in
What's the way to join namju solo /duo?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 157.85.88.84:24986.