Offline 157.85.85.132:25321 checked 25d ago
EVAL team production
Connect
srv = rust.server("157.85.85.132:25322")
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 23 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 best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 28 Sep, 16:52 UTC31d ago | 1 | NaN | running | 0 |
| 1 | Sun 27 Sep, 10:40 UTC32d ago | 2 | NaN | 1.3 days | 0 |
| 2 | Thu 24 Sep, 12:04 UTC35d ago | 2 | held half | 2.9 days | 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())
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 · 150 on average | 21/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 44/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 182/215 |
Quick answers
From the figures on this page.
Player counts
What position does EVAL team production take in the server rankings?
Over the last seven days EVAL team production sits at #16,001 on player hours, in the top 71% of ranked servers.
What population does EVAL team production carry?
Offline now for EVAL team production, with the last sample 25 days 10 hours ago.
About the server
Which Rust version is EVAL team production on?
Rust network protocol 2633 and build 165217 on Linux is what EVAL team production runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is EVAL team production, and is it online now?
Offline now for EVAL team production, last seen 25 days 10 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 23 September 2026.
Where does EVAL team production sit?
No region is published by EVAL team production. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 157.85.85.132:25321.
Settings and map
Which rules apply on EVAL team production, and what settings?
No gather rate appears in the name: EVAL team production. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on EVAL team production?
EVAL team production runs a procedural map of size 6,000 with seed 50000, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.
Wipe schedule
On what schedule does EVAL team production wipe?
No next wipe can be predicted for EVAL team production, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 31 days 8 hours ago, and that is the one in play.
On EVAL team production, what happens on wipe day?
Recent wipes averaged 2 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags, lists
Which lists on Rust Data hold EVAL team production, and which filters?
The Rust Data lists that EVAL team production fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on EVAL team production hold?
The game's server browser reads these tags from EVAL team production: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): The server runs build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to EVAL team production?
Enter client.connect 157.85.85.132:25321 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.