Channel
@ThunderProtocolAnnBSC
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
31subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001340703111 |
|---|---|
| Type | Channel |
| Username | @ThunderProtocolAnnBSC |
| Created | Between 1 March 2018 and 5 April 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ThunderProtocolAnnBSC |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 02:46 | 31 | no change |
| 6 Aug 2026, 23:32 | 31 | first reading |
20 posts held, back to 5 April 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 April 2021. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
$Thunder Q2 Roadmap ✅ Smart contract ✅ Contract Audit: ✅ Website: ✅ Medium: ✅ Audit ☑️ Website Redesigning ☑️ NFT Platform ☑️ NFT Conceptualization ☑️ Partnerships ☑️ Coingecko ☑️ Coinmarketcap ☑️ CEX Listing
Solidity Finance finished auditing Thunderstorm token and here is their report. 🟢🟢🟢 https://solidity.finance/audits/Thunderstorm/ https://twitter.com/ProtocolStorm/status/1380161255600717825 🟢🟢🟢 https://t.me/ThunderProtocolBSC https://www.thunder-protocol.net/
Yup should be ready for your review pretty soon!
We had a response with CMC! Let's hope we get in
We are currently redesigning our website to add more information about the protocol and a prospect roadmap. https://www.thunder-protocol.net/about
🌩 Thunderstorm [Thunder Protocol] 🌩 Deflationary Supply and Elasticity 🌩 ⚡️ Thunder Protocol has the same concept of Lightning Protocol that works through a dynamic burn rate of [5 to 12%], which is applied at each Buy/Sell order. Transactions transactions that interact with the future ecosystem are not taxed, to ensure the usability of the protocol. ⚡️ Concept: There are a total of 156 cycles, each cycle has a TA…
https://youtu.be/LrPGJxwUCgU
If you have followed my call in twitter yesterday about ThunderBolt - congratulations!! You should be sitting on at least 2x profits! Enjoy the profits guys and don't forget to follow me on twitter too. I share great stuff there as well! https://twitter.com/Overdose_AI/status/1379448602368610311
Photo, posted without a caption
I really hope you followed this call about ThunderProtocol 🚀🚀🚀 Mooning so hard right now 🔥 https://poocoin.app/tokens/0xee84e260fae848f55ebde322b9595682590c456c
https://t.me/cryptopowerchannel/343
We are officially audited by Techrate. Our contract is safe. Solidity Finance audit is also under way. https://twitter.com/ProtocolStorm/status/1379232344742055937
Showing the 12 most recent of 20 posts we hold for @ThunderProtocolAnnBSC. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Thunder Protocol Official Announcement Channel” (@ThunderProtocolAnnBSC), 31 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ThunderProtocolAnnBSC.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.