Offline 118.68.62.79:28015 checked 3d ago
TEST SERVER
Connect
srv = rust.server("118.68.62.79:28017")
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. 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 41% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 118.68.62.79:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 16:05 UTC
- hostname
- –
- first seen
- 25 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 · 149 on average | 115/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 · 118 on average | 184/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 57/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 24/1000 |
Quick answers
From the figures on this page.
Population data
What position does TEST SERVER take in the server rankings?
Player hours over seven days put TEST SERVER at #9,078, in the top 41% of the ranked set.
How many players does TEST SERVER hold at once?
TEST SERVER returns no live count at this refresh, having last been seen 3 days 15 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server data
Which Rust version is TEST SERVER on?
Rust network protocol 2635 and build 168909 on Windows is what TEST SERVER runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TEST SERVER, and is it up?
The latest sample has TEST SERVER offline, with a last sighting 3 days 15 hours ago. 0 of 72 hours up over the last 3 full days, or 0%. Rust Data logged it first on 25 October 2026.
Where does TEST SERVER sit?
No region is published by TEST SERVER. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 118.68.62.79:28015.
Settings and map
Which settings and rules does TEST SERVER run?
No gather rate appears in the name: TEST SERVER. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
Which map has TEST SERVER selected?
A procedural map runs on TEST SERVER, generated by the game.
Wipe schedule
On what schedule does TEST SERVER wipe?
A rhythm cannot be read from the wipes of TEST SERVER on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 4 days 17 hours ago.
Tags, lists
Which lists on Rust Data hold TEST SERVER, and which filters?
The Rust Data lists that TEST SERVER fits are: 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 week.
How should you read the server tags on TEST SERVER?
The game's server browser reads these tags from TEST SERVER: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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.
Join steps
What is the way into TEST SERVER?
Enter client.connect 118.68.62.79:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.