Offline 45.140.128.90:10700 checked 8d ago
Rust EBIMAYO
Connect
srv = rust.server("45.140.128.90:10701")
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 69% 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 6d 17h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 17h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 17h | 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, 19:15 UTC FW28d 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
3000 · seed 6738
- map
- Procedural Map
- size
- 3000
- seed
- 6738
Server
srv.info()- address
- 45.140.128.90:10700
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:15 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 | 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.
Population
How does Rust EBIMAYO compare in the rankings?
Rank #15,426 on seven-day player hours for Rust EBIMAYO, within the top 69% of all ranked servers.
How many players does Rust EBIMAYO hold at once?
Offline now for Rust EBIMAYO, with the last sample 8 days 6 hours ago.
Server facts
What Rust version does Rust EBIMAYO run?
Rust network protocol 2634 and build 167781 on Windows is what Rust EBIMAYO runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Rust EBIMAYO, and is it online now?
The latest sample has Rust EBIMAYO offline, with a last sighting 8 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.
In which location is Rust EBIMAYO hosted?
For Rust EBIMAYO, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 45.140.128.90:10700.
Rules, settings, map
What rules and settings are recorded for Rust EBIMAYO?
You will not find a gather rate in the string Rust EBIMAYO. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: 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. Plugins installed: Oxide. Anti-cheat status: VAC on.
What is the map on Rust EBIMAYO?
Rust EBIMAYO runs a procedural map of size 3,000 with seed 6738, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does Rust EBIMAYO wipe, and how often?
A single wipe each month, the force wipe, is all Rust EBIMAYO does. 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 28 days 6 hours ago.
On Rust EBIMAYO, what happens on wipe day?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which lists on Rust Data hold Rust EBIMAYO, and which filters?
These Rust Data lists include Rust EBIMAYO: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Rust EBIMAYO hold?
The game's server browser reads these tags from Rust EBIMAYO: gmvanilla (Game mode): The mode is vanilla survival; mp20 (Max players): Slot count: 20; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Connecting
How can I connect to Rust EBIMAYO?
The manual route: launch Rust, F1, then client.connect 45.140.128.90:10700. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.
