Bitfufu: June mining yields 125 BTC; hashrate at 15.3 EH/s
Bitfufu produced 125 BTC in June-70 BTC from self-mining and 55 BTC from cloud services. Total hashrate under management fell to 15.3 EH/s; self-owned rose to 3.5 EH/s.
Bitfufu (NASDAQ: FUFU) produced 125 BTC in June 2026, with 70 BTC generated by self-mining operations and 55 BTC from cloud-mining services. Daily bitcoin production averaged 4.2 BTC in June, down from 5.7 BTC in May.
Total hashrate under management declined to 15.3 exahashes per second (EH/s) at June 30. Self-owned hashrate increased 9.4% to 3.5 EH/s after the deployment of 1,200 S21 XP miners in June. The company signed agreements to acquire and deploy an additional 2,000 S21 XP units in July.
Power capacity under management fell to 273 megawatts (MW) from 346 MW in May. Hashrate supplied by third-party providers and hosting customers accounted for 11.8 EH/s of the total 15.3 EH/s at month-end. Average fleet efficiency for June was 17.9 joules per terahash (J/TH), compared with 17.8 J/TH in May.
Bitfufu held 1,671 BTC on its balance sheet at June 30, down from 1,855 BTC at the end of May. The company attributed the reduction to the net effect of client receipts and upfront payments tied to 5.3 EH/s of future hashrate capacity secured under a nine-month agreement scheduled to begin in August 2026.
The nine-month agreement beginning in August 2026 and the timing of customer receipts affected month-end bitcoin holdings and are reflected in the June operational figures.
The material on GNcrypto is intended solely for informational use and must not be regarded as financial advice. We make every effort to keep the content accurate and current, but we cannot warrant its precision, completeness, or reliability. GNcrypto does not take responsibility for any mistakes, omissions, or financial losses resulting from reliance on this information. Any actions you take based on this content are done at your own risk. Always conduct independent research and seek guidance from a qualified specialist. For further details, please review our Terms, Privacy Policy and Disclaimers.
Articles by this author
