Microstrategy Buys 3,907 More Bitcoins, Company Now Hodls 108,992 BTC – Featured Bitcoin News


Microstrategy Buys 3,907 More Bitcoins, Company Now Hodls 108,992 BTC

Microstrategy has purchased 3,907 additional bitcoins for about $177 million. The Nasdaq-listed company now owns 108,992 bitcoins.

Microstrategy Has Purchased More Bitcoins

The pro-bitcoin Nasdaq-listed company Microstrategy has purchased more bitcoins. CEO Michael Saylor tweeted Tuesday:

Microstrategy has purchased an additional 3,907 bitcoins for ~$177 million in cash at an average price of ~$45,294 per bitcoin. As of 8/23/21 we hodl ~108,992 bitcoins acquired for ~$2.918 billion at an average price of ~$26,769 per bitcoin.

The company also informed the U.S. Securities and Exchange Commission (SEC) Tuesday of its bitcoin purchase in a filing dated Aug. 24.

Out of all public companies, Microstrategy owns the most bitcoin in its treasury. Another public company with a sizable bitcoin stash is Elon Musk’s electric car company, Tesla. In July, Musk hinted that Tesla owned about 42,069 bitcoins. He also revealed at the “B Word” Bitcoin event that both he himself and his other company Spacex also owned BTC.

Tags in this story
bitcoin treasury, Buy Bitcoin, Elon Musk, michael saylor, microstrategy, microstrategy bitcoin, Purchase Bitcoin, Tesla, tesla bitcoin

What do you think about Microstrategy buying more bitcoin? Let us know in the comments section below.

Kevin Helms

A student of Austrian Economics, Kevin found Bitcoin in 2011 and has been an evangelist ever since. His interests lie in Bitcoin security, open-source systems, network effects and the intersection between economics and cryptography.

Image Credits: Shutterstock, Pixabay, Wiki Commons

Disclaimer: This article is for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. Bitcoin.com does not provide investment, tax, legal, or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any content, goods or services mentioned in this article.

Read disclaimer
Show comments