Offline 57.128.22.77:25612 checked 34d ago
Testing
Connect
srv = rust.server("57.128.22.77:25610")
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 24 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 71% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 24 Sep, 00:24 UTC34d 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 672589003
- map
- Procedural Map
- size
- 3000
- seed
- 672589003
Server
srv.info()- address
- 57.128.22.77:25612
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 00:24 UTC
- hostname
- –
- first seen
- 23 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 · 157 on average | 66/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 63/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 55/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 17/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
How does Testing compare in the rankings?
Player hours over seven days put Testing at #15,621, in the top 71% of the ranked set.
How many players does Testing hold at once?
Testing returns no live count at this refresh, having last been seen 34 days 16 hours ago.
About the server
Which Rust version is Testing on?
The build is Rust network protocol 2633 and build 165217 on Linux, run by Testing. The protocol has to match before you can join, and Steam does the updating.
How reliable is Testing, and is it up?
The latest sample has Testing offline, with a last sighting 34 days 16 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 23 September 2026.
Which location does Testing run from?
No region is published by Testing. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 57.128.22.77:25612.
Settings and map
Which rules apply on Testing, and what settings?
The name Testing carries no gather rate. 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. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has Testing loaded?
Size 3,000, seed 672589003: the procedural map on Testing, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does Testing wipe, and on what schedule?
Too few wipes are on record for Testing to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 34 days 22 hours ago, and that is the one in play.
On Testing, what happens on wipe day?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain Testing?
These Rust Data lists include Testing: 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 Testing hold?
The game's server browser reads these tags from Testing: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): 40 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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
How can I connect to Testing?
In Rust, F1 opens the console: type client.connect 57.128.22.77:25612. Launch Rust on this page does the same by opening the game through Steam and connecting.