LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 26% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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.
Too few wipes are recorded for JP_Solo/Duo to establish a pattern. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. This world dates from 6 days 13 hours.
On Rust Live Stats, JP_Solo/Duo is listed under Modded Rust servers live now. You will find it on the server list under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
gmrust (Game mode): The game mode is standard Rust survival; mp15 (Max players): Slots: 15; ts8 (Group limit): Team cap: 8, which is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): The server sets no region code; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): The game changes here through plugins or settings, so it is Modded: that is the tag list JP_Solo/Duo publishes for the game's server browser. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Live now: 0 players on JP_Solo/Duo, out of 15 slots. Averaged across seven days, 0 players; the peak was 1.
On player hours for the past seven days, JP_Solo/Duo sits at #5,764, inside the top 26% of ranked servers.
Nothing in the name of JP_Solo/Duo states a gather rate. The default applies: 8 players to a group. survival applies here, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. The plugin load is Oxide. Anti-cheat: VAC from Valve is enabled.
JP_Solo/Duo runs a game-generated procedural map: size 4,500, seed 85804905. Size and seed repeat the same map, so RustMaps can show it from this page.
No region is published by JP_Solo/Duo. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 163.44.98.246:28015.
The average server fps was 41 over the last 48 hours; the lowest was 28. Entity count reached 116,363: buildings, deployables and the rest of the world. Memory use peaked at 4,833 MB. Lag, as players feel it, comes from low fps and a rising entity count.
The setup on JP_Solo/Duo is Rust network protocol 2635 and build 168909 with Linux. Steam updates it for you, but your game needs the same protocol to join.
Right now JP_Solo/Duo is online. Based on the uptime it reports, the last restart was about 6 days 11 hours ago. It was online for 119 of 120 hours in the last 5 full days, or 99% of the time. Rust Live Stats has tracked it since 23 October 2026.
Enter client.connect 163.44.98.246:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.