Online 157.85.85.43:23120 checked 11m ago
Testserver
Connect
srv = rust.server("157.85.85.43:23121")
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 1 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 54% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 20 Oct, 14:50 UTC7d ago | 1 | NaN | running | 0 |
| 1 | Thu 1 Oct, 15:21 UTC26d ago | 1 | halved by day 1 | 19 days | 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
1500 · seed 50000
- map
- Procedural Map
- size
- 1500
- seed
- 50000
Server
srv.info()- address
- 157.85.85.43:23120
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Oct 2026, 14:50 UTC
- hostname
- –
- first seen
- 1 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 · 155 on average | 174/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 178/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 139/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 16/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 53/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Testserver rank?
Player hours over seven days put Testserver at #12,118, in the top 54% of the ranked set.
What population does Testserver carry?
The sample now reads 0 players for Testserver, out of 1 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server data
What does performance look like on Testserver?
Server fps over the last 48 hours averages 238; the floor is 226. The entity count peaked at 8,374, covering buildings, deployables and the rest of the world. Memory peaked at 3,472 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does Testserver run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by Testserver. Steam updates your game for you, but the protocol must match to join.
Is Testserver up, and what does its uptime show?
The current sample puts Testserver online. A restart about 5 days ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. The first row Rust Data holds for it is dated 1 October 2026.
Where does Testserver sit?
For Testserver, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.85.43:23120 is its address.
Map and rules
Which settings and rules does Testserver run?
No gather rate appears in the name: Testserver. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Testserver selected?
Testserver runs a procedural map of size 1,500 with seed 50000, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does Testserver wipe, and how often?
The record for Testserver holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 7 days 20 hours ago.
What is wipe day on Testserver like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The drop under half arrived by day 1 in the other cases.
Lists and tags
Which lists on Rust Data hold Testserver, and which filters?
On Rust Data, Testserver appears in these lists: 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; Last wipe: In the last 2 weeks.
Which meanings do the tags on Testserver hold?
Read by the game's server browser, the tags Testserver publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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.
How to join
How can I connect to Testserver?
In Rust, F1 opens the console: type client.connect 157.85.85.43:23120. Launch Rust on this page does the same by opening the game through Steam and connecting.