Online 157.85.90.189:20148 checked 10m ago
A
Connect
srv = rust.server("157.85.90.189:20149")
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 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 62% 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 23:40 UTC4d ago | 1 | 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
3500 · seed 50000
- map
- Procedural Map
- size
- 3500
- seed
- 50000
Server
srv.info()- address
- 157.85.90.189:20148
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 23:40 UTC
- hostname
- –
- first seen
- 23 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 · 157 on average | 67/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 68/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 60/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 16/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 10/1000 |
Quick answers
From the figures on this page.
Player counts
What position does A take in the server rankings?
Over the last seven days A sits at #13,742 on player hours, in the top 62% of ranked servers.
How full does A run?
A reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
What does performance look like on A?
The 48-hour average is 125 server fps, with a low of 1. Buildings, deployables and all else in the world took the count as high as 67,841 entities. Memory peaked at 3,474 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on A?
Version Rust network protocol 2635 and build 168909 on Linux is reported by A. The protocol has to match before you can join, and Steam does the updating.
Is A up, and what does its uptime show?
A reports itself online at the current refresh. Count back 4 minutes from its reported uptime to get the last restart. 96 of 96 hours up over the last 4 full days, or 100%. Rust Data logged it first on 23 October 2026.
Where does A sit?
There is no region published for A. 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.90.189:20148.
Map and rules
Which settings and rules does A run?
You will not find a gather rate in the string A. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has A loaded?
A runs a procedural map of size 3,500 with seed 50000, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does A wipe, and how often?
The record for A holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 4 days 23 hours ago.
On A, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 1 hours in.
Lists and tags
Which lists on Rust Data hold A, and which filters?
These Rust Data lists include A: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on A?
The game's server browser reads these tags from A: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): Slot count: 40; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $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 A?
Enter client.connect 157.85.90.189:20148 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.