Online 51.83.150.41:28015 checked 13m ago
TESTING
Connect
srv = rust.server("51.83.150.41:28016")
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 40% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 | Sat 17 Oct, 19:12 UTC10d ago | 1 | NaN | running | 0 |
| 1 | Thu 15 Oct, 14:58 UTC12d ago | 18 | held half | 2.2 days | 3 |
| 2 | Mon 12 Oct, 14:59 UTC15d ago | 25 | held half | 3 days | 0 |
| 3 | Thu 8 Oct, 14:58 UTC19d ago | 12 | held half | 4 days | 4 |
| 4 | Mon 5 Oct, 15:00 UTC22d ago | 24 | held half | 3 days | 2 |
| 5 | Thu 1 Oct, 17:57 UTC FW26d ago | 23 | halved by day 1 | 3.9 days | 1 |
| 6 | Mon 28 Sep, 15:58 UTC29d ago | 24 | held half | 3.1 days | 2 |
| 7 | Fri 25 Sep, 17:03 UTC32d ago | 22 | held half | 3 days | 2 |
| 8 | Mon 21 Sep, 15:57 UTC36d ago | 6 | halved by day 1 | 4 days | 0 |
| 9 | Mon 14 Sep, 15:56 UTC43d ago | 25 | halved by day 2 | 7 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
1000 · seed 612351
- map
- Procedural Map
- size
- 1000
- seed
- 612351
Server
srv.info()- address
- 51.83.150.41:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 19:12 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 · 156 on average | 121/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 125/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 49/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 23/1000 |
Quick answers
From the figures on this page.
Population data
What position does TESTING take in the server rankings?
Player hours over seven days put TESTING at #8,846, in the top 40% of the ranked set.
How full does TESTING run?
TESTING reports 0 players at this refresh, with 500 slots configured. Over the last seven days it averaged 0 players and peaked at 4. Peak hour in the last 48 hours: 09:00 UTC, mean 0 players.
Server data
What does performance look like on TESTING?
Averaged over 48 hours: 128 server fps, never under 125. Buildings, deployables and all else in the world took the count as high as 4,021 entities. The memory field tops out at 1,061 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is TESTING on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by TESTING. Steam updates your game for you, but the protocol must match to join.
How reliable is TESTING, and is it online now?
Online is the state at the latest refresh for TESTING. Count back 2 days 11 hours from its reported uptime to get the last restart. 127 of 168 hours up over the last 7 full days, or 76%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is TESTING hosted?
There is no region published for TESTING. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 51.83.150.41:28015.
Settings and map
Which rules apply on TESTING, and what settings?
No gather rate appears in the name: TESTING. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
What is the map on TESTING?
Size 1,000, seed 612351: the procedural map on TESTING, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does TESTING wipe, and how often?
Irregular wipe times on TESTING leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 10 days 12 hours ago.
What is wipe day on TESTING like?
Across recent wipes the busiest point averaged 15 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 80% of recent wipes. In the wipes where it did not hold, half was lost by day 1.
Tags and filters
Which Rust Data filters and lists contain TESTING?
These Rust Data lists include TESTING: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on TESTING hold?
The game's server browser reads these tags from TESTING: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): 500 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. 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 into TESTING?
Enter client.connect 51.83.150.41:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.