Online 14.12.224.96:29264 checked 10m ago
BondRingage
Connect
srv = rust.server("14.12.224.96:29265")
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 65% 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 2, 28 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 12:44 UTC26d ago | 2 | 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
5000 · seed 67890
- map
- Procedural Map
- size
- 5000
- seed
- 67890
Server
srv.info()- address
- 14.12.224.96:29264
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 12:44 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 516 on average | 486/525 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 401/450 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 52/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 44/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 48/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 243 on average | 161/200 |
Quick answers
From the figures on this page.
Player counts
How does BondRingage compare in the rankings?
Over the last seven days BondRingage sits at #14,514 on player hours, in the top 65% of ranked servers.
How many players does BondRingage hold at once?
The sample now reads 0 players for BondRingage, out of 20 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server data
What does performance look like on BondRingage?
Server fps over the last 48 hours averages 124; the floor is 106. Buildings, deployables and all else in the world took the count as high as 138,003 entities. A high of 3,459 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on BondRingage?
Rust network protocol 2635 and build 168909 on Windows is what BondRingage runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is BondRingage, and is it up?
BondRingage reports itself online at the current refresh. Count back 15 hours from its reported uptime to get the last restart. 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 BondRingage run from?
No region is published by BondRingage. Rust Data does not look up where the machine stands; it shows where a server says it is. 14.12.224.96:29264 is its address.
Settings and map
Which settings and rules does BondRingage run?
No gather rate appears in the name: BondRingage. 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. Raids and player combat are enabled. Community is its browser category. VAC is running: Valve's anti-cheat is on.
Which map has BondRingage loaded?
Size 5,000, seed 67890: the procedural map on BondRingage, 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 BondRingage wipe, and on what schedule?
A rhythm cannot be read from the wipes of BondRingage 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 26 days 23 hours ago.
On BondRingage, what happens on wipe day?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 28 hours in.
Tags, lists
Which lists on Rust Data hold BondRingage, and which filters?
These Rust Data lists include BondRingage: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on BondRingage?
Read by the game's server browser, the tags BondRingage publishes are: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): 20 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; 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. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into BondRingage?
Enter client.connect 14.12.224.96:29264 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.