Telegram RegisterThe public register of Telegram
Telegram profile photo for bitsCrunch Announcements

Channel

bitsCrunch Announcements

@bitsCrunchAnn

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

690subscribers

+3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001450933095
TypeChannel
Username@bitsCrunchAnn
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/bitsCrunchAnn

Growth

6846906877 August 2026 — 687 subscribers8 August 2026 — 687 subscribers15 August 2026 — 684 subscribers22 August 2026 — 690 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net +3. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 683–691 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 13:44690+6
15 Aug 2026, 16:47684-3
8 Aug 2026, 02:30687no change
7 Aug 2026, 11:30687first reading

Engagement

20 posts held, back to 11 February 2026the 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 6 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
6s
Average length
6s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

127 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 58.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7458.3%
4233.1%
👍53.94%
🤬43.15%
🎉21.57%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 127reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 11 February 2026 to 6 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

6 Jul 2026, 16:30 UTC604 views5 reactionsread 8 August 2026

No, we have NOT launched any token on Solana or any other chain. Please be cautious - any such information circulating is false / spam. ✅ Always verify updates only through our official channels: Official website Verified social handles CoinMarketCap listing (search: bitsCrunch) Stay safe and don’t interact with unknown contract addresses.

👍41

4 Jul 2026, 11:11 UTC450 views5 reactionsread 8 August 2026
Photo

https://x.com/bitscrunch/status/2073351066083795192

🔥5

23 Jun 2026, 16:11 UTC725 views7 reactionsread 8 August 2026

Thanks for sharing your thoughts. The team is focused on ongoing development and strengthening the overall ecosystem. As progress continues, more details around roadmap and next steps will be shared. bitsCrunch is actively building.

4🤬3

2 Jun 2026, 09:08 UTC666 views6 reactionsread 8 August 2026

5 years of bitsCrunch data → AI just ignited. ⚡ Blockchain data isn't scarce anymore. Understanding it is. https://x.com/bitsCrunch/status/2061736261514375670

🔥6

21 May 2026, 13:15 UTC524 views10 reactionsread 8 August 2026
Photo

bitsCrunch earns CertiK Spotlight recognition Proud to announce that bitsCrunch has been featured in CertiK Spotlight: AI Data & Content Economy. https://x.com/bitsCrunch/status/2057449156155978015

🔥91

19 May 2026, 09:10 UTC444 viewsread 8 August 2026

On-chain data availability isn’t the bottleneck anymore. Interpretation is. There’s more data than ever across chains, but extracting signal still requires technical effort. 🧵👇 Simplifying how users move from data → understanding. https://x.com/bitscrunch/status/2056663306392506863

12 May 2026, 05:59 UTC499 views3 reactionsread 8 August 2026

https://x.com/bitscrunch/status/2054078645615071606

3

8 May 2026, 13:37 UTC433 views6 reactionsread 8 August 2026
Video

https://x.com/bitsCrunch/status/2052743298029322520

6

8 May 2026, 13:36 UTC402 views5 reactionsread 8 August 2026

https://x.com/bitsCrunch/status/2052743298029322520

5

6 May 2026, 07:44 UTC395 views4 reactionsread 8 August 2026

5+ years in Web3. Multiple cycles. Noise, hype, and resets. At bitsCrunch, one thing hasn’t changed: We’re still building. 🧵👇 → Structuring blockchain data → Building scalable pipelines → Making data actually usable Behind the scenes, we’ve been focused on what matters. https://x.com/bitscrunch/status/2051930184195215517

3🤬1

7 Apr 2026, 06:02 UTC484 views8 reactionsread 8 August 2026

https://x.com/bitscrunch/status/2041395326662353167

8

23 Mar 2026, 09:18 UTC438 views14 reactionsread 8 August 2026

Hey Crunchers! $BCUT to Exit MEXC Assessment Zone We’re pleased to share that $BCUT has successfully passed the review and will be removed from the MEXC Assessment Zone by March 23. This reflects continued progress in meeting exchange requirements and maintaining operational standards. The team will continue to ensure that all necessary criteria are consistently met going forward. Thank you to our community for t

🔥13👍1

Showing the 12 most recent of 20 posts we hold for @bitsCrunchAnn. 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.

Cite this entry

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 22 August 2026 — this entry's latest reading, not the date you are reading this.

“bitsCrunch Announcements” (@bitsCrunchAnn), 690 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/bitsCrunchAnn.

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.