Online NA 66.51.98.57:28000 checked 12m ago
MexRust
Connect
srv = rust.server("66.51.98.57:28001")
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 bestTop 33% of all ranked servers, top 60% in NA. 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 6d 14h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 14h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 14h | Thu 3 Dec, 19:00 UTC | FW force wipe |
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 29 Oct, 18:26 UTC9h ago | NaN | NaN | running | 0 |
| 1 | Thu 29 Oct, 00:26 UTC1d ago | NaN | NaN | NaN | 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
4000 · seed 5107
- map
- Procedural Map
- size
- 4000
- seed
- 5107
Server
srv.info()- address
- 66.51.98.57:28000
- region
- NA
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 29 Oct 2026, 18:26 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 | [NA] Willjum's Casual Solo/Duo Monthly | NA · groups of 8+ · monthly · 14 on average | 11/175 |
| 1 | Hempville 420 No Kos Low Decay / Limited PvP | NA · groups of 8+ · monthly · 7 on average | 7/90 |
| 2 | Made in Quebec & France! QC FR EN (Website 9 Languages) | NA · groups of 8+ · monthly · 4 on average | 3/1000 |
| 3 | Testing Grounds | NA · groups of 8+ · monthly · 2 on average | 2/15 |
| 4 | [US] Exile PvE | Noob Friendly | Raidable Bases | Skill Tree | | NA · groups of 8+ · monthly · 1 on average | 0/50 |
| 5 | Apocrypha-Linux | PvE | PvP | NA · groups of 20+ · monthly · 1 on average | 1/50 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does MexRust rank?
Player hours over the last seven days: #7,342 for MexRust, #1,124 in North America, within the top 33% of the ranked set.
What population does MexRust carry?
MexRust reports 1 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 21:00 UTC is the busiest, at 2 players.
About the server
How smoothly does MexRust run?
Server fps over the last 48 hours averages 13; the floor is 5. The entity count peaked at 90,911, covering buildings, deployables and the rest of the world. A high of 2,610 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does MexRust run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by MexRust. The protocol has to match before you can join, and Steam does the updating.
How reliable is MexRust, and is it online now?
The current sample puts MexRust online. Count back 7 hours from its reported uptime to get the last restart. 24 of 168 hours up over the last 7 full days, or 14%. The first row Rust Data holds for it is dated 13 September 2026.
Where does MexRust sit?
The NA tag is what MexRust uses to list itself in North America. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 66.51.98.57:28000 is its address.
Map and rules
Which rules apply on MexRust, and what settings?
You will not find a gather rate in the string MexRust. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has MexRust selected?
Size 4,000, seed 5107: the procedural map on MexRust, 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 MexRust wipe, and how often?
Once a month MexRust wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 9 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
Tags, lists
Where does MexRust appear among Rust Data lists and filters?
On Rust Data, MexRust appears in these lists: Modded Rust servers and North America Rust servers. Under these filters on the server list, it is listed: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 24 hours.
How should you read the server tags on MexRust?
Read by the game's server browser, the tags MexRust publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): The server browser files it under North America. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to MexRust?
In Rust, F1 opens the console: type client.connect 66.51.98.57:28000. Launch Rust on this page does the same by opening the game through Steam and connecting.