Online 85.190.132.70:25565 checked 8m ago
ZergRust3000
Connect
srv = rust.server("85.190.132.70:25567")
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 16 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 46% 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 1001898781
- map
- Procedural Map
- size
- 2500
- seed
- 1001898781
Server
srv.info()- address
- 85.190.132.70:25565
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 12:59 UTC
- hostname
- –
- first seen
- 16 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 · 151 on average | 51/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 89/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 20/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 78/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 64/200 |
Quick answers
From the figures on this page.
Population
What position does ZergRust3000 take in the server rankings?
Player hours over seven days put ZergRust3000 at #10,325, in the top 46% of the ranked set.
How many players does ZergRust3000 hold at once?
ZergRust3000 reports 0 players at this refresh, with 500 slots configured. Over the last seven days it averaged 0 players and peaked at 1.
Server data
How smoothly does ZergRust3000 run?
Averaged over 48 hours: 218 server fps, never under 159. The entity count peaked at 30,387, covering buildings, deployables and the rest of the world. A high of 1,698 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 ZergRust3000?
The build is Rust network protocol 2635 and build 168909 on Linux, run by ZergRust3000. Joining needs the same protocol on your game; Steam handles the update.
Is ZergRust3000 up, and what does its uptime show?
Online is the state at the latest refresh for ZergRust3000. A restart about 6 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 16 October 2026.
Which location does ZergRust3000 run from?
For ZergRust3000, 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 85.190.132.70:25565.
Settings and map
What rules and settings are recorded for ZergRust3000?
You will not find a gather rate in the string ZergRust3000. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has ZergRust3000 loaded?
The game generates the map on ZergRust3000: procedural, size 2,500, seed 1001898781. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does ZergRust3000 wipe, and on what schedule?
A rhythm cannot be read from the wipes of ZergRust3000 on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 13 days 18 hours ago.
Tags, lists
Which Rust Data filters and lists contain ZergRust3000?
These Rust Data lists include ZergRust3000: 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 2 weeks.
How should you read the server tags on ZergRust3000?
Read by the game's server browser, the tags ZergRust3000 publishes are: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): Slot count: 500; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 into ZergRust3000?
In Rust, F1 opens the console: type client.connect 85.190.132.70:25565. Launch Rust on this page does the same by opening the game through Steam and connecting.