Online 162.43.25.136:28015 checked 12m ago
3over
Connect
srv = rust.server("162.43.25.136:29015")
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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 2, 9 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 02:07 UTC25d ago | 2 | NaN | running | 0 |
# 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
4500 · seed 50000
- map
- Procedural Map
- size
- 4500
- seed
- 50000
Server
srv.info()- address
- 162.43.25.136:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 02:07 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 · 164 on average | 160/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 136/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 28/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 148/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 46/1000 |
Quick answers
From the figures on this page.
Player counts
How does 3over compare in the rankings?
Over the last seven days 3over sits at #15,400 on player hours, in the top 69% of ranked servers.
What population does 3over carry?
Current row: 0 players on 3over, against 50 slots. Over the last seven days it averaged 0 players.
About the server
What does performance look like on 3over?
Server fps over the last 48 hours averages 110; the floor is 69. Entity numbers reached 118,250, and that includes buildings, deployables and the rest. A high of 3,414 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on 3over?
Version Rust network protocol 2634 and build 166494 on Linux is reported by 3over. Steam updates your game for you, but the protocol must match to join.
How reliable is 3over, and is it up?
The current sample puts 3over online. Count back 5 minutes from its reported uptime to get the last restart. 168 of 168 hours up over the last 7 full days, or 100%. Rust Data logged it first on 13 September 2026.
Where does 3over sit?
For 3over, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 162.43.25.136:28015.
Map and rules
What rules and settings are recorded for 3over?
No gather rate appears in the name: 3over. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has 3over selected?
The game generates the map on 3over: procedural, size 4,500, seed 50000. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does 3over wipe, and on what schedule?
Too few wipes are on record for 3over to reveal its rhythm. 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 25 days 18 hours ago.
On 3over, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. The crowd on the latest wipe topped out 9 hours after it began.
Tags and filters
Which lists on Rust Data hold 3over, and which filters?
These Rust Data lists include 3over: 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.
Which meanings do the tags on 3over hold?
These tags are published by 3over and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join 3over?
The manual route: launch Rust, F1, then client.connect 162.43.25.136:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.