Last checked: November 2026
Short answer
Record each shared bill once, at the site. Then split it between mining and GPU hosting with one documented basis, ideally metered kWh per circuit, otherwise rated power times hours run. Use the same basis every month, keep company overhead outside site results, and review the split with your accountant.
Why a mixed site needs a split
Mining operators adding GPU servers next to ASICs face a practical accounting question: how should one utility bill, one hosting invoice or one cooling contract reach the two activities? Without a documented split, one activity can look better than it is because the other carries its costs.
Lenders and accountants ask how shared costs were assigned. Keep the bill, the supporting readings and the calculation together. A repeatable method lets someone follow the site total through to mining and GPU results without counting the same expense again.
Which costs are shared
Power, cooling, hosting or colocation fees, site rent, internet, security and site staff can serve both activities. Check the contract before allocating: a hosting invoice may already include electricity or cooling. Adding a separate estimate for an included service counts it twice.
Direct costs belong to the activity that incurred them: pool fees to mining, marketplace or platform fees to GPU hosting, and machine repairs and hardware depreciation to the relevant hardware. Keep company overhead, including head office, company software and legal costs, outside site results.
Allocation bases, from best to roughest
| Basis | Suitable costs | What to check |
|---|---|---|
| Sub-metered kWh per circuit or PDU | Power and cooling | Best when available. Identify which circuits serve each activity and any common loads. |
| Measured server power from PDUs or device telemetry | Power and cooling estimates | Prefer a server or PDU meter. GPU telemetry alone misses the rest of the server. |
| Rated power times hours run | Power and cooling estimates | Rougher: machines rarely draw exactly rated power. Include idle operation. |
| Rack space or floor share | Rent and security | Document occupied space and treatment of common areas. |
| Machine count | A simple fallback for shared site services | Ignores power differences. Usually a poor proxy for electricity. |
The NVIDIA nvidia-smi documentation describes GPU power draw as covering the entire board. That does not include CPUs, chassis fans, drives or power supply losses. A whole-server or PDU reading gives a better starting point for the bill. Cooling may need its own meter or a documented estimate for common plant.
Steps each month
- Record each bill once at site level, for the period it covers.
- Pick the basis per cost line and write it down. Power can follow kWh while rent follows space.
- Collect meter readings or operating hours for the same period. Keep the evidence with the bill.
- Compute each activity's share: its measured or estimated usage divided by combined usage, multiplied by the shared cost.
- Post the shares to mining and GPU activity. Check that they add back to the original bill.
- Keep idle GPU time in the GPU line. Idle servers still draw power even without rental earnings.
- Review and lock the month. Reuse the same basis next month and note any change, including why it was needed.
Worked example
Illustrative only. Invented amounts.
One site receives a $20,000 power bill for 160,000 kWh. Sub-meters show ASIC circuits at 120,000 kWh and GPU circuits at 40,000 kWh. Assume those readings cover all billed consumption in this example.
Mining's share is 120,000 ÷ 160,000 = 75%, so $20,000 × 75% = $15,000. GPU hosting's share is 40,000 ÷ 160,000 = 25%, so $20,000 × 25% = $5,000.
Site rent is $3,000. A documented floor share of 70% mining and 30% GPU gives $2,100 and $900.
| Shared cost | Mining | GPU hosting | Site total |
|---|---|---|---|
| Power | $15,000 | $5,000 | $20,000 |
| Rent | $2,100 | $900 | $3,000 |
| Total allocated | $17,100 | $5,900 | $23,000 |
Pool fees and marketplace fees stay direct. Company overhead of $1,500 is not allocated to the site. The table shows shared costs only, not activity profit.
For comparison, suppose rated power times hours run estimates 96,000 kWh for ASICs and 64,000 kWh for GPUs. That is a 60%/40% split: the same $20,000 bill becomes $12,000 mining and $8,000 GPU. Rent stays $2,100/$900, making totals $14,100/$8,900. Both methods allocate $23,000, but the activity results differ. The basis matters; prefer the meter evidence when it is complete.
Common mistakes
- Counting a shared bill twice, once per activity, instead of allocating one site total.
- Changing the basis month to month without noting the reason and effect.
- Putting company overhead into site profit and hiding the operating comparison.
- Forgetting idle GPU power because no rental earnings appeared that period.
- Mixing payout timing with cost timing. A later payout does not move the electricity consumption to a later month.
How Flash fits
Flash for GPU operators: Keep ASIC miners and GPU servers at the same site. Record a shared bill once, then split it between mining and GPU activity. Bring mapped QuickBooks costs into the close for review.
One physical site can hold ASIC miners and GPU servers. Record shared bills once and allocate them between the two activities, while keeping company overhead separate. See the result by site and machine group in the same monthly close and lender pack.
Profit by site and machine group. Hardware depreciation. Review the records and lock the month. Later corrections are recorded, so the version you shared stays intact.
Any Vast.ai host can connect today in early access. Add your read-only key to bring in machine inventory, earnings, platform fees and payouts. Review earnings and fees by machine, and confirm each payout when the money arrives.
Braiins Pool connects directly with a read-only API token. Flash is the CFO layer for compute operators.
Honest limitations
Flash does not read power meters or PDUs. You record the allocation; the allocation basis is yours and your accountant's decision. The Vast.ai connection is in early access. Tax and accounting treatment of allocations is for your accountant.
Questions
How do I split a power bill between Bitcoin mining and GPU hosting?
Record the bill once at site level. Divide each activity's metered kWh by total kWh, then apply those shares to the bill. Document how you treat common cooling and other site loads with your accountant.
Is rated power good enough to allocate electricity?
It can be a documented estimate when meters are unavailable. Multiply rated power by hours run for each activity and divide by the combined estimate. Machines rarely draw exactly rated power, so review the estimate against actual consumption when possible.
Does nvidia-smi power draw cover the whole server?
No. NVIDIA describes GPU power draw as covering the entire board. It does not cover CPUs, chassis fans, drives or power supply losses. Prefer a server or PDU meter for allocating the electricity bill.
Should idle GPU servers carry power costs?
Yes. Idle servers still draw power. Keep that consumption in the GPU activity, including periods without rental earnings. Allocating only rented periods understates GPU costs and pushes the remainder onto mining.
Where does company overhead go?
Keep head office, company software and legal costs outside site results. Show them separately when reviewing the wider business with your accountant, rather than making a site allocation appear to be a complete company profit figure.
Can one site be in the same lender pack for mining and GPU?
Yes. One physical site can hold ASIC miners and GPU servers. Record shared bills once and allocate them between the two activities, while keeping company overhead separate. See the result by site and machine group in the same monthly close and lender pack: a pack your lender can check.
Run your own numbers
Start with Flash's calculator to run the math with your own inputs.
For a GPU estimate, use the GPU rental profit calculator.
Get started
Review the shared bills and allocation evidence with your accountant before closing the month.
Sources
Checked 17 November 2026.