Online 208.73.203.30:7781 checked 8m ago
[GNG] Development Server | Staging & Plugin Testing
Connect
srv = rust.server("208.73.203.30:27017")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 69% 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 3, 11 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 30 Sep, 18:35 UTC29d ago | 3 | 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 1337![Map of [GNG] Development Server | Staging & Plugin Testing](https://files.facepunch.com/rust/map-images/c07de75a2e221c75a052f599d9a6355716c4bf9db61fb185b7a6c24e72a99bbb/proceduralmap.3000.1790793337711.289_c07de75a2e221c75a052f599d9a63557.jpg)
- map
- Procedural Map
- size
- 3000
- seed
- 1337
Server
srv.info()- address
- 208.73.203.30:7781
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 30 Sep 2026, 18:35 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)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 · 151 on average | 121/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 197/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 76/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 228/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 347/350 |
Quick answers
From the figures on this page.
Player counts
How does [GNG] Development Server | Staging & Plugin Testing compare in the rankings?
Rank #15,310 on seven-day player hours for [GNG] Development Server | Staging & Plugin Testing, within the top 69% of all ranked servers.
How full does [GNG] Development Server | Staging & Plugin Testing run?
[GNG] Development Server | Staging & Plugin Testing reports 0 players at this refresh, with 2 slots configured. Over the last seven days it averaged 0 players.
About the server
How smoothly does [GNG] Development Server | Staging & Plugin Testing run?
The 48-hour average is 205 server fps, with a low of 186. Entity numbers reached 47,230, and that includes buildings, deployables and the rest. A high of 4,350 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does [GNG] Development Server | Staging & Plugin Testing run?
The build is Rust network protocol 2634 and build 166406 on Windows, run by [GNG] Development Server | Staging & Plugin Testing. The protocol has to match before you can join, and Steam does the updating.
How reliable is [GNG] Development Server | Staging & Plugin Testing, and is it online now?
[GNG] Development Server | Staging & Plugin Testing reports itself online at the current refresh. A restart about 10 days 5 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does [GNG] Development Server | Staging & Plugin Testing run from?
There is no region published for [GNG] Development Server | Staging & Plugin Testing. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 208.73.203.30:7781 is its address.
Settings and map
Which settings and rules does [GNG] Development Server | Staging & Plugin Testing run?
You will not find a gather rate in the string [GNG] Development Server | Staging & Plugin Testing. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has [GNG] Development Server | Staging & Plugin Testing loaded?
Size 3,000, seed 1337: the procedural map on [GNG] Development Server | Staging & Plugin Testing, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
When does [GNG] Development Server | Staging & Plugin Testing wipe, and how often?
A rhythm cannot be read from the wipes of [GNG] Development Server | Staging & Plugin Testing 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. This world was created 29 days ago.
On [GNG] Development Server | Staging & Plugin Testing, what happens on wipe day?
Recent wipes averaged 3 players at their peak. The crowd on the latest wipe topped out 11 hours after it began.
Tags and filters
Where does [GNG] Development Server | Staging & Plugin Testing appear among Rust Data lists and filters?
The Rust Data lists that [GNG] Development Server | Staging & Plugin Testing fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on [GNG] Development Server | Staging & Plugin Testing?
The game's server browser reads these tags from [GNG] Development Server | Staging & Plugin Testing: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166406 (Build): The server runs build 166406; 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): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to [GNG] Development Server | Staging & Plugin Testing?
In Rust, F1 opens the console: type client.connect 208.73.203.30:7781. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://www.greatnorthgaming.com.