bittensorTAO
$ 355.82 USD
+2.93
%
(24H)
0.0033928 BTC
+2.63
%
(24H)
Capitalization (USD)
$2,251,178,494
24H trading volume (USD)
$47,253,774
Circulating supply
6,326,784
Max. supply
21,000,000
Markets
 # | Market | Ticker | Price | Price, USD | Volume | |
|---|---|---|---|---|---|---|
| 1 |  Bitget |  TAO_USDT | 356.97 | $ 353.97 | $ 3 361 802 | 1 sec. |
| 2 |  Mexc | TAO_USDT | 357.14 | $ 353.84 | $ 6 904 309 | 2 sec. |
| 3 |  Bitmart | TAO_USDT | 357.06 | $ 353.65 | $ 390 286 | 5 sec. |
| 4 |  GateIo | TAO_USDT | 357.07 | $ 353.87 | $ 10 225 622 | 6 sec. |
| 5 |  BingX | TAO_USDT | 357.24 | $ 354.01 | $ 584 538 | 3 sec. |
| 6 |  Bitrue | TAO_USDT | 357.25 | $ 354.01 | $ 2 643 760 | 3 sec. |
| 7 |  Kucoin | TAO_USDT | 357.07 | $ 353.79 | $ 11 441 988 | 2 sec. |
| 8 |  Coinex | TAO_USDT | 356.97 | $ 354.43 | $ 244 533 | 1 sec. |
| 9 |  Pionex | TAO_USDT | 357.17 | $ 353.77 | $ 386 304 | 1 sec. |
Cryptocurrency bittensor today is estimated at $355.82, and the market capitalization is $ 2 251 178 494. Over the past 24 hours, asset trading amounted to $ 47 253 774.
bittensor with ticker TAO has a circulating supply in 6 326 784 TAO with maximum circulating supply in 21 000 000 TAO.
Price change table TAO
| Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2025 | 440.8 | 449.5 | 326.5 | 223.8 | 355.1 | 430.2 | ||||||
| 2024 | 388.6 | 389.1 | 272.1 | 302.2 | 281.2 | 578.2 | 484.7 | 677.7 | ||||
| 2025 | +1.97% | -27.39% | -31.45% | +58.71% | +21.12% | -16.99% | ||||||
| 2024 | +0.13% | -30.07% | +11.06% | -6.95% | +105.58% | -16.19% | +39.84% | -34.93% | ||||
| AVG: | +1.97% | -27.39% | -31.45% | +58.71% | +10.62% | -23.53% | +11.06% | -6.95% | +105.58% | -16.19% | +39.84% | -34.93% |
| Year | Start price | Final price | Profit | Period |
|---|---|---|---|---|
| 2025 | $ 440.80 | $ 357.10 | -18.99% | 2025-01-01 - 2025-06-19 |
| 2024 | $ 639.60 | $ 441.00 | -31.05% | 2024-04-11 - 2024-12-31 |
Error on the page?
Let us know about it:
Thank you very much! We will check it and try to find the best solution!