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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 2, 9 hours in.
The current map
Friday 2 October 2026, 02:07 UTC
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.
The average peak across its recent wipes is 2 players. Peak population on the latest wipe came 9 hours after it.
3over's wipe history is too thin on record to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world dates from 26 days 3 hours.
These are the Rust Live Stats lists 3over fits: Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more it appears on the server list.
These are the tags 3over makes public: gmrust (Game mode): Survival here follows standard Rust; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2634 (Protocol): You need protocol 2634 on your game to get in; cs166494 (Build): The game build is 166494; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game changes here through plugins or settings, so it is Modded. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
0 of 3over's 50 slots are filled right now. Across the past week the average was 0 players.
Player hours over seven days put 3over at #15,423, in the top 69% of all ranked servers.
No gather rate appears in the name 3over. No custom limit is set, so groups hold the default 8 players. It runs survival, the standard game: gather, build, raid. Raiding and player combat are both permitted. The server browser files it under Modded: plugins or settings alter the game. Oxide plugins are in use. VAC is enabled: Valve's anti-cheat.
3over runs a game-generated procedural map: size 4,500, seed 50000. Size and seed repeat the same map, so RustMaps can show it from this page.
Nothing on 3over states a region. 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 162.43.25.136:28015.
The average server fps was 111 over the last 48 hours; the lowest was 69. Entity count reached 118,323: buildings, deployables and the rest of the world. The highest memory usage was 3,414 MB. Lag, as players feel it, comes from low fps and a rising entity count.
Rust network protocol 2634 and build 166494 on Linux is what 3over runs. To join, your game must use the same protocol; Steam handles the update for you.
At the time of this update, 3over is live. The uptime it reports puts the last restart at about 8 hours ago. 168 of 168 hours were online in the last 7 full days, giving 100% uptime. The first sighting by Rust Live Stats was on 13 September 2026.
Enter client.connect 162.43.25.136: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.