Bitget spot breakeven price is not necessarily your average buy price. Under the spot model described in Bitget’s published guides, it relates the unrecovered trading outlay to the quantity tracked by that calculation. A partial sale can change that figure, while an inbound transfer can change your total balance without representing another purchase in the same trading cycle.
First match the product, field definition, covered transactions and fees. The examples below explain a documented spot model and a separate cash-flow check; they do not reproduce every current Bitget app, account mode or accounting report.
Written and official documents checked: November 2, 2026 (KST). All transaction amounts are hypothetical, not market quotes or executed trades. Scope: ordinary spot interpretation, not futures, margin borrowing, UTA collateral calculations, bots, copy trading or tax reporting.
Which number are you trying to reconcile?
- Average buy price: a quantity-weighted average of the buys you selected. It answers what those purchases cost per coin.
- Trading breakeven: a recovery measure for the transactions and quantity included in that particular calculation. It is not automatically the acquisition cost of every coin in the wallet.
- Total balance: the amount currently held. Transfers and other balance movements can make it different from a trade-based quantity.
Bitget’s October 2024 spot-analysis guide separates transaction holdings from total holdings. That distinction explains why multiplying a trading figure by the entire wallet balance can produce the wrong comparison. “Cost price” also needs its own field definition; it is not a universal synonym for either measure.
What do the different official document versions establish?
| Document | Useful scope | Limit |
|---|---|---|
| September 29, 2024 update | Introduces the spot breakeven indicator and a reset when tracked quantity reaches zero. | A dated product announcement, not a current screen test. |
| October 11, 2024 guide | Distinguishes trading coverage from a legacy asset-cost measure. | Labels the asset-cost comparison as an old version and discusses an offline feature. |
| December 30, 2024 help article | Explains analysis tabs, cost/breakeven labels and transaction fees. | Listing both labels does not prove they are simultaneously available in every current account. |
The introduction notice specifies a calculation start of September 19, 2024 at 10:15:44 (UTC+8). Do not assume a displayed series reconstructs an unlimited trading history. Nor should the later help article be treated as proof that a legacy feature was restored. For a current account, use the explanation beside the actual field and retain its product and date context.
A worked ledger: the same BTC, different quantities
Assume a new tracked cycle, no borrowing and no fees for this first illustration. Buy 0.4 BTC at 30,000 USDT per BTC, then 0.1 BTC at 40,000 USDT. The buys cost 16,000 USDT for 0.5 BTC, giving an average buy price of 32,000 USDT per BTC.
| Hypothetical event | Total BTC | Tracked BTC | Unrecovered trading outlay, USDT |
|---|---|---|---|
| Buy 0.4 BTC at 30,000 | 0.4 | 0.4 | 12,000 |
| Buy 0.1 BTC at 40,000 | 0.5 | 0.5 | 16,000 |
| Transfer in another 0.25 BTC | 0.75 | 0.5 | 16,000 for this trading cycle |
| Sell 0.2 BTC at 36,000 | 0.55 | 0.3 | 8,800 |
The partial sale brings in 7,200 USDT. The remaining trading outlay is therefore 16,000 − 7,200 = 8,800 USDT, against 0.3 BTC of tracked quantity. The fee-free recovery price for that cycle is 8,800 ÷ 0.3 = 29,333.33 USDT per BTC, rounded for display.
The original buys still average 32,000. Under a simple average-cost illustration, the 0.2 BTC sale realizes 800 USDT before fees, and the remaining cost allocation is 9,600 USDT. By contrast, the recovery calculation credits the cycle with all sale proceeds. These answer different questions; neither number alone establishes the tax basis or total return of the transferred BTC.
For this fee-free, partially open model: remaining outlay = previous outlay − sale proceeds; recovery price = remaining outlay ÷ remaining tracked quantity. When adding a buy, add its payment and quantity first. The denominator must stay positive.
A loss-making partial sale moves the calculation the other way
Start again from the same 0.5 BTC and 16,000 USDT of buys. These are alternative outcomes, not successive sales:
| Price for a 0.2 BTC sale | Outlay left, USDT | Recovery price for 0.3 BTC, USDT/BTC |
|---|---|---|
| 36,000 | 8,800 | 29,333.33 |
| 28,000 | 10,400 | 34,666.67 |
A changed breakeven figure is not evidence that the exchange changed your historical fill prices. Reconcile the cash flows first. A lower displayed recovery figure also does not erase a previous loss, justify buying more or predict the next price.
How do you check costs without counting fees twice?
Keep a separate economic check rather than assuming a screen includes every charge. For illustration only, assume a 0.1% fee on each buy and sale, paid separately in USDT, unchanged net BTC quantities and no other costs. This is an assumed rate and fee currency, not a promise about your Bitget account.
- Buys plus fees: 16,000 + 16 = 16,016 USDT.
- Partial-sale proceeds after fees: 7,200 − 7.2 = 7,192.8 USDT.
- Outlay still to recover: 16,016 − 7,192.8 = 8,823.2 USDT.
- If selling the remaining 0.3 BTC incurs the same 0.1% fee, solve 0.3 × exit price × (1 − 0.001) = 8,823.2. The resulting price is approximately 29,440.11 USDT per BTC.
The last value is a BitQED cash-flow estimate under those assumptions, not a prediction of Bitget’s displayed field or an executable exit quote. Actual average fills replace estimates when available. If the fee was taken from received BTC, use the actual net quantity; if paid in BGB, record that separate cost in a stated comparison unit. Do not subtract a charge again when the source result already includes it. Check the Bitget fee guide for account-rate and fee-currency checks.
What happens at zero quantity or after transfers?
If all 0.5 BTC from the illustrated cycle is sold at 36,000, proceeds are 18,000 USDT and the completed result is 2,000 USDT before fees. There is no remaining quantity to divide by. The introduction notice describes a reset at zero tracked quantity; keep completed-cycle results separately rather than carrying a division-by-zero result into the next purchase.
Another arithmetic boundary occurs if earlier proceeds already recover the cycle’s outlay. Selling 0.2 BTC at a hypothetical 90,000 yields 18,000 USDT, exceeding the original 16,000. A raw recovery equation then has a negative numerator. This only indicates net recovery in that chosen ledger; it does not establish that Bitget must display a negative price, or that the remaining asset has no market risk.
For transfers, do not invent an acquisition price from the deposit-time quote, and do not force unmatched withdrawals or sells into a ledger with insufficient tracked quantity. Rebuild the covered records first. Converted assets may form part of the documented trading coverage, but the conversion quote and actual receipt must still be identified; see the Convert versus spot comparison.
A practical reconciliation checklist
- Write down the exact product and field label. Do not mix ordinary spot figures with futures, margin, bot or copy-trading statistics.
- Match the asset, quote currency, date range and valuation time. Separate total holdings from transaction-tracked quantity.
- List the covered buys, sells, conversions and transfers. Check actual quantities and average fills, not merely submitted orders.
- Record fee amounts and currencies, and whether the displayed result already includes them. Treat an estimated future selling fee separately.
- Mark zero-quantity resets and missing records. If a number remains inconsistent, retain the field explanation and relevant records for official support; never share passwords, seed phrases or API secrets.
The transaction-history export guide explains the record types to collect. The futures PnL guide covers a different product and should not be used as a spot formula. No account connection, file upload or trade is required to read this article.
Limits: This is educational accounting arithmetic, not investment, legal or tax advice. BitQED is independent of Bitget and may use affiliate links elsewhere; this article adds no referral link. Product access, field definitions and fee treatment can vary or change. The documented calculations do not guarantee fills, recovery of funds or future returns.