Offline 66.94.101.80:28200 checked 26d ago
A-Mex
Connect
srv = rust.server("66.94.101.80:28215")
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 best
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 5h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 5h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:24 UTC FW27d ago | 0 | 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
2000 · seed 2147483647
- map
- Procedural Map
- size
- 2000
- seed
- 2147483647
Server
srv.info()- address
- 66.94.101.80:28200
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:24 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 513 on average | 524/550 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 431/450 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 61/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 63/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 54/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 238 on average | 165/200 |
Quick answers
From the figures on this page.
Population data
What position does A-Mex take in the server rankings?
Rank #15,967 on seven-day player hours for A-Mex, within the top 70% of all ranked servers.
How full does A-Mex run?
A-Mex returns no live count at this refresh, having last been seen 26 days 6 hours ago.
Server facts
Which Rust version is A-Mex on?
Version Rust network protocol 2634 and build 166586 on Windows is reported by A-Mex. The protocol has to match before you can join, and Steam does the updating.
How reliable is A-Mex, and is it online now?
A-Mex is offline at this refresh; the last response came 26 days 6 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 13 September 2026.
Where does A-Mex sit?
There is no region published for A-Mex. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 66.94.101.80:28200.
Rules, settings, map
Which rules apply on A-Mex, and what settings?
No gather rate appears in the name: A-Mex. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Community is its browser category. Joining requires Rust's premium status. VAC, Valve's anti-cheat, is enabled.
Which map has A-Mex selected?
The game generates the map on A-Mex: procedural, size 2,000, seed 2147483647. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does A-Mex wipe?
Once a month A-Mex wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 27 days 18 hours ago.
What is wipe day on A-Mex like?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does A-Mex appear among Rust Data lists and filters?
These Rust Data lists include A-Mex: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: Premium; Server tag: Premium ^q; Group limit: 5 or more.
How should you read the server tags on A-Mex?
Read by the game's server browser, the tags A-Mex publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^q (Premium): Joining requires Rust's premium status. 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 to join A-Mex?
Enter client.connect 66.94.101.80:28200 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. Joining requires Rust's premium status.