OpenFront In-Game Gold Rates: Read the Leaderboard Before You Invest or Attack

Direct answer: read stock, rate, source, and military capacity together

Open the leaderboard gear, add Gold Income/min and its ship, train, and piracy columns, then compare at least two readings. Current Gold is spending power now; the rates are gross income over a rolling two-minute game-time window. Attack or embargo only when a named route explains the rival’s advantage. If the source is unclear, preserve troops, observe another interval, and avoid treating the largest number as the safest target.

This guide applies to the released v34 line and was checked against the immutable v0.34.17 tag on 25 September 2026. The four rate columns entered the official v0.34.0 release: total Gold Income/min, Ship Trade Gold/min, Piracy Gold/min, and Train Trade Gold/min. They remain optional rather than part of the default compact view. The default player table shows clan, territory, current Gold, and maximum troops alongside the non-hideable rank and player fields; the gear opens the larger column set. That distinction matters because a player who never opens the picker may not realize the game already exposes the evidence needed to separate a rich stockpile from a working income engine.

The stable question answered here is not “who is winning?” and it is not a replacement for inspecting the map. It is: which visible economic change should alter your next investment, attack, embargo, donation, or wait decision? The Threat Assessment guide owns whole-board target selection, the Trade versus Piracy guide owns the choice between legal arrivals and captures, and the Train Network guide owns rail topology. This page teaches how to read the shared measurement surface before you choose one of those plans.

Use four objects, always in the same order. Stock is current Gold and answers what can be bought immediately. Rate is gross Gold received per minute and answers how quickly buying power can return. Source is the visible part attributed to ship trade, train trade, or piracy and suggests which route may be protected or disrupted. Capacity combines current troops, maximum troops, territory, and structures and asks whether the economy can actually survive contact. None of the four can replace another. A player can hold 8,000,000 Gold with a collapsed route, show 900,000 Gold/min while having almost no current reserve, or own many Factories whose trains have stopped paying.

The decision rule is deliberately conservative: require a named cause and a feasible response. “Blue has the largest Gold/min number” is an observation. “Blue’s ship-trade component has stayed high across two readings, the only active Port route crosses an exposed strait, and one patrol would force escort spending” is a plan. The leaderboard supplies the first half; the map, event feed, relations, and route geometry supply the second. If those surfaces disagree, believe the narrower claim: the rate shows that income arrived, not which future arrival is guaranteed or which attack will be profitable.

Configure the table before interpreting any rank

Open the in-game statistics table and use the gear at its trailing edge to choose the columns relevant to the current question. Rank and player name are always present in the player table; team name is always present in the team table. Other fields are selectable, including player type, territory share, current Gold, the four income rates, current troops, maximum troops, Cities, Ports, Factories, Missile Silos, SAM Launchers, Warships, allies, and betrayals. The interface displays them in a fixed logical order even when you select only a subset: identity, territory, economy, military, structures, then diplomacy.

For a first economic read, show territory, current Gold, Gold Income/min, the three source rates, current troops, maximum troops, Ports, Factories, and Warships. Add Silos and SAMs when nukes are enabled, and add allies or betrayals when a relation change could explain a route or threat. This is intentionally wider than the default view, so horizontal scrolling may be necessary on a small screen. Do not respond by hiding the very source columns that answer the question. Instead, choose a compact audit set for the current decision and switch back after the check.

Every numeric header is sortable. The first click selects the column in descending order, and clicking it again reverses the direction. That means the displayed rank is not a permanent overall rating; it is the position within the column you currently chose. Sorting by current Gold answers who can spend now. Sorting by Gold Income/min answers who has recently received Gold fastest. Sorting by ship trade or piracy changes the order again. Always name the sort in your own reasoning. Saying “the number-one player” without naming the column invites exactly the error this tool was built to prevent.

Your own row remains available when you fall below the always-visible top ranks: the table pins it separately rather than making you scroll and lose your reference point. Use that row as a baseline. Compare a rival’s rate to yours, not only to the absolute top. A 300,000 Gold/min rival may be a major threat when you earn 80,000, but ordinary when three nearby players earn 500,000. The same principle applies to team mode, where the team table adds the numeric values of living members. A strong team total can hide one exposed economic carrier, so switch between team and player reads instead of assuming the aggregate tells you who must be protected.

The player-type column distinguishes human players, Nations, and Tribes. That prevents another false comparison: an AI-controlled position may have a visible economy and land share but different diplomatic and tactical behavior. Type is not a threat score; it tells you which decision model to use. Likewise, the structure columns count total levels, not merely icons. They are evidence of installed capacity, not evidence that a route is currently valid. Two Port levels do not prove two profitable lanes, and three Factory levels do not prove any connected foreign stop is still paying.

Finish configuration with a repeatable snapshot. Record the game time, selected sort, your row, the two rows you are comparing, and the source column that appears to explain the difference. Then return after one useful interval or a visible event such as an arrival, embargo, station loss, capture, donation, or naval interception. The value of the leaderboard comes from change, not from staring longer at one refresh. Two labeled snapshots turn a rank into evidence; one unlabeled screenshot turns it into a story you may tell yourself after the decision has already failed.

Understand the two-minute gross-income window

The four rates are computed from cumulative counters over a rolling window of up to two minutes of simulation time. The tracker records a player’s total Gold received, ship-trade Gold, train Gold, and piracy Gold together with the current game tick. OpenFront runs the relevant clock at ten ticks per second, so two in-game minutes are 1,200 ticks. For each column, the client takes the latest cumulative value minus the oldest retained value, divides by the elapsed game minutes between those samples, and presents the result as a per-minute rate.

This design has three consequences. First, Gold Income/min is gross received, not profit. Spending on a City, Silo, Warship, donation, or attack does not subtract from that rate. Current Gold shows the remaining stock after spending; the rate shows how quickly Gold entered. A player can therefore have the best gross rate and almost no balance because they just bought infrastructure. Conversely, a player can have a huge balance and a low rate because they banked earlier income or received a windfall before the current window.

Second, the source rates are parts of the explanation, not guaranteed to sum exactly to the total in every situation. Ship trade, train trade, and piracy have their own cumulative counters, while total income includes every Gold source the game records in its overall earned value. Base income, other rewards, and timing differences can leave a remainder. Use that remainder as a prompt to inspect the position, not as proof of a hidden exploit. If total income is 700,000 per minute and the three visible source columns explain 480,000, the safe statement is that 220,000 is not attributed by those three displayed components in the current measurement; the unsafe statement is that the player secretly owns a route you cannot see.

Third, trade and piracy arrive in lumps. One ship docking or one capture can make a short interval look explosive. The two-minute window smooths those arrivals, but it also reacts slowly after a route dies. A Port may be captured at 12:00 while its earlier successful arrivals remain in the window until about 14:00 of simulation time. The displayed rate can therefore describe recent history after the future has already changed. Look for the event that invalidates the route, then treat the falling rate as confirmation rather than waiting for zero before acting.

Pauses and frozen simulation do not make the figure decay through wall-clock time. When the tick count does not advance, the rate returns zero for a zero-length comparison rather than pretending two real-world minutes passed. Speed changes should also be read through game time, not through how long you have been sitting at the computer. This protects the measurement from menu delays, but it means your own stopwatch is a poor substitute for the in-game clock.

The first reading after the tracker has too little history can also be zero or unstable. It needs at least two samples and enough elapsed ticks to make the slope useful. Do not launch an attack because a rival briefly shows zero immediately after a table reset, client transition, or new observation. Wait for the window to accumulate, then compare again. The tracker resets between games because player identifiers are reused, so a previous match cannot legitimately carry its rates into the next one.

Treat the window as a rear-view mirror with a known length. It is excellent for answering “what has funded this player during the last phase?” It cannot answer “will the next ship survive?”, “is the rail still connected?”, or “did this purchase leave enough troops?” Those are map and state questions. Pair the smoothed rate with live route observations and a stock reading, and the delayed average becomes useful evidence instead of false precision.

Use RATE to turn columns into one bounded decision

Use the RATE framework whenever the leaderboard changes your attention: Reserve, Attribution, Trend, Exposure. It deliberately ends with exposure because an economic lead matters only when you can exploit or protect it without losing the board. Run RATE on one player or one team, name one action, and write one stop signal. Do not use it to rank everyone at once.

Reserve compares current Gold, current troops, maximum troops, and immediate deadlines. Ask what the player can buy now and what military force remains while they buy it. Ten million Gold with 80,000 troops on an open border is not the same position as ten million with 800,000 behind a narrow line. For your own row, reserve also includes the force and Gold you refuse to spend. A plan without a reserve is only a guess that nobody will react.

Attribution asks which visible source explains the rate. A high ship-trade component points you toward Ports, partners, and sea lanes. A high train component points toward a Factory cluster and valid stations. A piracy spike points toward captured Trade Ships and may be temporary, politically dangerous, or dependent on prey. If no displayed component explains most of the total, do not invent a precise target. Inspect Cities, territory, recent donations, captures, and the event feed, then mark the cause as unresolved.

Trend requires at least two labeled readings. Classify each important value as rising, stable, falling, or reset by an event. The absolute rate matters less than the direction after a route change. A ship-trade rate of 500,000 that falls to 320,000 and then 140,000 after an embargo tells a clearer story than a single 500,000 screenshot. Account for the two-minute lag: the route can be dead while the rate remains positive. Trend is your confirmation layer, not permission to ignore the map.

Exposure identifies the cheapest legal point where a response can change the trend. It might be an exposed Port, a rail station, a strait, a Warship patrol, a relation that can be embargoed, or simply the player’s under-defended troop reserve. Exposure must include your cost and the opponent’s counter. If blocking one sea lane requires three expensive Warships while the player can reroute to another partner, the number is attractive but the response is weak. If a single controlled strait carries most arrivals, the same rate can justify a bounded patrol.

RATE step	Evidence to read	Decision it may justify	Stop signal
Reserve	Gold, troops, maximum troops, structures	Spend, hold, donate, or prepare defence	Reserve falls below the fastest credible response
Attribution	Total rate plus ship, train, piracy components	Protect or disrupt a named engine	Source does not explain the total or route is already invalid
Trend	Two or more timed readings and event feed	Continue pressure or abandon a failed theory	Next full observation does not move the expected column
Exposure	Map route, relations, units, travel time	One bounded attack, embargo, patrol, or investment	Counter-cost exceeds the income you can actually deny

RATE produces a sentence, not a score: “Blue has 2.4M Gold, ship income is falling from 620k to 310k after the western Port was captured, their reserve remains 700k troops, and the eastern strait is still open; patrol the strait with one existing Warship, then stop if arrivals reroute.” That sentence separates observation, inference, action, and exit. It also makes disagreement useful: a teammate can challenge the route or reserve instead of arguing about whether Blue is generally strong.

For adjacent execution, use Embargo Timing and Trade Control when the response is diplomatic, Warship Fleet Decisions when it is naval, and Adaptive Build Order when your own next purchase is the question. RATE decides which branch deserves a test; those pages own the mechanics after the branch is selected.

Scenario one: a ship-trade lead that is worth disrupting

Assume a normal-speed public FFA on a coastal map at 14:00. These numbers are a worked hypothetical, not a promise about a playlist or payout. You have 1.8 million Gold, 620,000 current troops, an 850,000 maximum, one Warship, and no active naval fight. Blue has 3.1 million Gold, 540,000 troops, a 900,000 maximum, two Port levels, and one Warship. Your first timed reading shows Blue at 760,000 Gold Income/min, of which 510,000 is Ship Trade Gold/min, 40,000 is train income, and zero is piracy. Your own total is 250,000 per minute.

Reserve says Blue can fund a serious purchase now, but does not have an overwhelming troop edge. You can test a lane without emptying the land front because a Warship already exists; buying an entire new fleet would change that answer. Attribution is strong: roughly two thirds of Blue’s visible total rate is associated with completed ship trade in the current window. The map shows repeated ships using one western strait toward an allied Port, while the eastern coast has no observed partner. Trend is not known yet, so the first action is observation rather than an embargo or attack.

At 15:00, another ship docks through the western route and Blue reads 820,000 total with 590,000 from ship trade. The source and route now agree. Exposure is the strait, but the bounded response is not “destroy every Port.” Move the existing Warship onto the approach while keeping the land reserve intact. Name the hypothesis: if the patrol stops completed arrivals, Blue’s ship component should begin falling as earlier payments age out of the two-minute window. The patrol succeeds strategically even if it fires no decisive shot, provided it forces escort spending, rerouting, or a trade interruption cheaper than the value denied.

At 16:30, Blue still shows 470,000 Ship Trade Gold/min. That does not prove the patrol failed; earlier arrivals remain inside the smoothed window. At 17:30, the source rate falls to 170,000, Blue has bought a second Warship, and the observed route has produced no completion. The test has changed both income and spending. You now choose between holding the blockade and leaving. Keep it only if your one Warship can still control the approach or withdraw safely. Do not buy a third ship merely because the old 820,000 headline looked threatening.

Time	Blue current Gold	Total Gold/min	Ship Gold/min	Visible event	RATE conclusion
14:00	3.1M	760k	510k	Western arrivals observed	Strong source, trend unknown
15:00	3.5M	820k	590k	Another arrival through same strait	Test existing patrol
16:30	2.7M	680k	470k	Blue buys Warship, no new completion seen	Respect window lag
17:30	2.9M	360k	170k	Route quiet, escort committed	Denial confirmed; reassess cost

The opponent has counters. Blue can change partner, protect the strait, embargo your trade, lure the patrol away, or use the saved stock before the average falls. Therefore current Gold remains in every snapshot. A falling rate does not erase 2.9 million already banked, and a route denial does not make Blue harmless on land. Your stop signal is explicit: leave if the patrol needs another purchase, if a second profitable route appears, or if your land reserve falls below the fastest neighboring attack. The leaderboard did not order a blockade. It made one route testable and told you when the test had actually changed recent income.

Scenario two: a train spike that should not trigger a bad attack

Assume a four-team match on a large continental map at 11:30. The figures are again hypothetical and exist to demonstrate the decision method. Your team has 4.6 million combined Gold, 2.8 million current troops, a 4.1 million maximum, and a protected central Factory cluster. Red shows 6.2 million Gold, 1.9 million troops, a 4.8 million maximum, five Factory levels, and a team Gold Income/min of 1.35 million. Sorting by train income places Red first at 880,000 per minute. A teammate proposes an immediate full attack because “Red is snowballing.”

Reserve rejects the full attack. Red has low current troops relative to its cap, but your team would have to cross two borders and leave the central cluster open to Green. Low current troops can mean vulnerability, recent spending, or troops already committed elsewhere; it is not proof that the route is undefended. Your combined Gold and troops are sufficient for a test, not for a blind elimination attempt. Mark a floor of 2.2 million team troops based on the fastest credible Green pivot, and refuse any plan that crosses it.

Attribution points to trains, so inspect stations before armies. Red’s five Factory levels are installed capacity, but only one corridor connects to two teammate Cities and an allied coastal Port. A recent relation warning says the Port alliance may expire. The proper first move is to watch the corridor and its paying relations, not to attack the nearest Red border. Trend makes the warning actionable: at 12:30, Red still shows 900,000 train Gold/min; at 13:30, after the alliance expires and one station is captured, the column drops to 520,000. Because the average retains earlier payments, the drop confirms a source change before it reaches zero.

Exposure is the remaining teammate station, but Team mode changes ownership and coordination. Capturing it might require an expensive two-front push, while a bounded attack on the connecting rail tile or pressure on the station owner could interrupt the same engine. Assign one player to hold Green, one to threaten the corridor, and one to preserve the central economy. The team table reveals the aggregate advantage; the player table reveals which Red member owns the vulnerable route and which member still carries troops. Do not treat a summed row as a single target.

Suppose the corridor pressure costs 350,000 troops and leaves the team at 2.45 million, above the agreed floor. By 15:00, Red’s train rate is 210,000, but its current Gold remains 5.4 million. The response has bought time, not victory. Spend the time on a protected City level, a shorter border, or a decisive territory route rather than chasing every Factory icon. If Red reconnects through another City and the rate rebounds, the original exposure is gone; stop repeating the same attack and reassess.

This scenario exposes the main leaderboard trap: acceleration is not position. Red had the best income flow but a relation-dependent rail network, a low current-force ratio, and a large saved stock. Each fact changes a different decision. The source column selects the corridor to inspect, the two-minute trend verifies whether disruption worked, current Gold keeps the near-term threat visible, and troops plus geography cap what your team may risk. The correct answer can be “do not attack yet” even when the rival is first in the most alarming column.

Failure modes, deception, and the counter-reading

The first failure is confusing gross income with net profit. The rate never subtracts purchases, protection, repairs, or the troops lost defending a route. A player earning 700,000 per minute and spending 800,000 on escorts is not automatically compounding. Counter this by pairing rate with current Gold across two readings. If the rate stays high while the stock falls, the economy may be financing a costly response rather than building a future strike.

The second failure is attacking the sorted leader instead of the exposed system. Sorting makes one row appear first, but the header defines the ranking. A high train earner on the opposite side of the map may be less actionable than the third-ranked ship trader crossing your strait. Counter this with exposure: name the tile, relation, route, or unit your action changes. If you cannot name one, the table has given you attention, not a target.

The third failure is reading the smoothed window as live route health. Earlier arrivals remain in the two-minute average after a Port is lost or a railway breaks. An opponent can exploit this lag by moving the route while you continue hitting its old location. Counter it with the event feed and visible completions. Mark the invalidating event first, then use the delayed decline only to confirm what already changed. A positive historical rate is not evidence that a destroyed route is secretly working.

The fourth failure is assuming source components explain the entire total. Base and other income can sit outside the displayed ship, train, and piracy components. Donations, captures, and current stock also change spending power without making your chosen route the cause. Counter this by labeling unexplained income rather than forcing the numbers to add up. “Unattributed in these columns” is a useful state; it prevents a precise but fictional blockade.

The fifth failure is ignoring payer, owner, and beneficiary. A Factory owner, station owner, trade partner, and team defender can be different players. The Team row sums living members, which is useful for side strength and dangerous for target selection. An opponent can deliberately distribute routes so the visible carrier is protected by someone else’s troops. Counter by switching to player rows, clicking the relevant player to locate them, and tracing ownership before committing. In Team, communicate whose income you are reducing and whose border you are actually opening.

The sixth failure is letting the rival manipulate your attention. They can save Gold while showing a falling rate, spend visibly to bait an attack, shift trade partners, run piracy for a short spike, or keep a decoy Port while trains fund the real plan. The leaderboard is public information and sophisticated players know you can see it. Counter by demanding agreement between two independent surfaces: rate plus arrivals, rate plus route ownership, stock plus construction, or troop change plus visible attack. One number can be bait; two connected observations are harder to fake.

The seventh failure is measurement without an exit. Players keep a patrol, embargo, or land attack running because the targeted column once looked large. RATE requires a stop signal before action: one full observation window without the expected decline, a newly valid alternate route, an escort cost above the denied income, or your reserve crossing its floor. When the signal fires, stop even if the rival remains rich. Your test can be correct and still cease to be profitable.

Finally, do not turn the guide into surveillance paralysis. Reading every column every few seconds costs attention that belongs on the map. Use scheduled audits: after an important arrival, relation change, structure loss, major purchase, or at a quiet checkpoint. Configure only the columns that answer the current question, capture two readings, make one bounded decision, and close the table. Good use of statistics reduces uncertainty; bad use replaces play with monitoring.

Adjust for mode and map, then keep a four-line ledger

In public FFA, the player table is the primary surface because each human ultimately owns their own stock, routes, and win condition. Alliances can make ship or train income possible, but they are timed and can expire or be broken. Read allies beside source rates when a major route depends on that relation. Piracy income also carries diplomatic consequences: a spike may be lucrative and may simultaneously make the player a coalition target. Do not convert a temporary capture burst into a claim that their stable economy is strongest.

In Team, start with the team table to identify which side is accelerating, then switch to player rows to locate the carrier, defender, donor, and exposed route. Numeric columns are summed across living teammates. That makes territory, Gold, rates, troop capacity, and structure levels useful aggregate signals, but the sum does not say which member can respond at the threatened tile. A team with 4 million troops can still have a 200,000-troop player guarding the rail junction. Coordinate the response through roles rather than ordering everyone toward the biggest team rate.

In Ranked 1v1, there is no coalition to distribute the response. Rates can reveal whether the opponent’s branch is paying, yet the short timer and direct route often make troops, maximum troops, territory, and immediate stock more important than a fully matured two-minute trend. Use the income columns to validate an economic choice, not to postpone a required defence. In Ranked 2v2, alternate between team and player views: the side total shows pace, while individual rows reveal whether one partner is carrying the economy and the other the front.

Singleplayer and Humans versus Nations need a type check. The player-type column distinguishes humans, Nations, and Tribes, but their decisions are not interchangeable. A Nation with a high visible rate is still governed by AI targeting and relation behavior. Use the number to understand capacity, then apply the correct AI guidance instead of assuming a human bluff. Custom lobbies can change Gold multipliers, disabled systems, teams, or pace; remove irrelevant columns rather than reading zero ship income as weakness in a lobby where Ports are disabled.

Map shape changes exposure. On an ocean map, ship trade can dominate and one strait, Port cluster, or Warship patrol may explain the whole difference. On a connected continental map, train income can depend on a small set of stations and relation-owned corridors. On compact maps, the two-minute window may be long relative to how quickly a border reaches the route, so live troop and path information outrank the trailing average. On huge maps, a leading rate may be economically important but physically unreachable; denial is not a plan until travel time and a defensible exit exist.

Keep a four-line ledger to prevent the interface from becoming noise:

Line	Write this	Example
State	Time, mode, map, selected sort	18:00, Team, ocean, ship rate descending
Evidence	Stock, total rate, source, reserve	3.2M; 720k/min; 500k ship; 610k/900k troops
Action	One bounded test and owner	Existing Warship patrols west strait for one window
Exit	Observable stop or pivot	Stop on reroute, second escort purchase, or reserve below 500k

After the action, label the result observed, inferred, or unknown. A completed ship disappearing is observed. The patrol causing the decline is inferred if an embargo happened at the same time. Whether the rival can establish another partner may remain unknown. Change one trigger or stop condition in the next match rather than rewriting the entire framework around one outcome. The Replay Review guide provides the broader evidence method for that comparison.

The official boundaries are the v0.34.0 Release, the tagged GoldRateTracker, column registry, sortable table, and Team aggregation. Recheck the method if a later formal Release changes the rolling window, cumulative counters, default columns, or team aggregation. Until then, use rates as delayed gross-flow evidence, never as a universal strength score.