Rust StatisticsWorking papers on every public Rust server · 76,222 players now

ZergRust3000

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 7m ago · 85.190.132.70:25565

Abstract

We describe the public Rust server ZergRust3000, reached at 85.190.132.70:25565. At the last check it held 0 of 500 places, against a seven-day mean of 0 and a peak of 11. It ranks #10,284 of all servers, the top 46%. It last wiped 13d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/5000% full
In the queue0no queue
Seven-day mean0peak 1
Rank2#10,284top 46%
Last wipe13d agono schedule published
Next wipe3–no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123423:0008:0017:0003:0012:0021:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
010020030040023:0008:0017:0003:0012:0021:00
Figure 2: 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 16 Oct.

4Rank

The server stands in the top 46% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k16 Oct19 Oct21 Oct24 Oct26 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of ZergRust3000
Figure 4: The map: Procedural Map, size 2500, seed 1001898781. Open on RustMaps.
Table 3: The server's published settings.
Address85.190.132.70:25565
Region–
Max players500
Group limit8, the default
Wipe schedule–
Last wipe16 Oct 2026, 12:59 UTC
Hostname–
First seen16 Oct 2026
MapProcedural Map
Size2500
Seed1001898781

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and Rust wipe forecast [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 150 on average38/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average121/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 120 on average74/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average30/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 92 on average77/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average296/310

Appendix AQuick answers

From the figures on this page.

Server details

A.1How well does ZergRust3000 run?

Over the past 48 hours, it ran at an average of 215 server fps, with a low of 130. The highest number of entities it carried was 30,387, comprising buildings, deployables and all other objects. The peak memory usage was 1,698 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2In which location is ZergRust3000 based?

A region is not published by ZergRust3000. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 85.190.132.70:25565 is its address.

A.3How reliable is ZergRust3000, and is it currently online?

ZergRust3000 is online at this time. Based on the uptime it reports, the last restart occurred about 21 hours ago. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. It was first observed on 16 October 2026 by Rust Statistics.

A.4What is the Rust version for ZergRust3000?

The version of Rust on ZergRust3000 is network protocol 2635 and build 168909, and the operating system is Linux. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5What schedule does ZergRust3000 follow for wipes?

The record of ZergRust3000's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 13 days 9 hours have passed since the current world was generated.

Population

A.6What position does ZergRust3000 occupy in the ranking of Rust servers?

Ranked by player hours across seven days, ZergRust3000 holds #10,284, in the top 46% of all ranked servers.

A.7How would you characterise the player activity on ZergRust3000?

At this moment 0 players are on ZergRust3000, which has 500 slots in total. Over the last week the count averages 0 players and reaches 1 at its height.

Tags, lists

A.8What is the meaning of the tags on ZergRust3000?

gmrust (Game mode): Survival on standard Rust rules; mp500 (Max players): 500 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags ZergRust3000 publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.9Where can ZergRust3000 be found among the Rust Statistics lists and filters?

These Rust Statistics lists include ZergRust3000: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Settings and map

A.10Under what rules and settings does ZergRust3000 operate?

The name of ZergRust3000 states no gather rate. No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Oxide. VAC is active: that is Valve's anti-cheat.

A.11What is the map for ZergRust3000?

The game generates ZergRust3000's procedural map at size 2,500, from seed 1001898781. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

Connection

A.12How do you connect to ZergRust3000?

Press F1 inside Rust to open the console and enter client.connect 85.190.132.70:25565. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp500Max players. 500 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. The game protocol is 2635; your client must match it to join.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. No region code is set.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.