Telegram RegisterThe public register of Telegram
Telegram profile photo for Bomb Crypto

Channel

Bomb Crypto

@bombcrypto

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

523subscribers

-15 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001412880150
TypeChannel
Username@bombcrypto
CreatedBetween 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/bombcrypto

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 88% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

523538530.56 August 2026 — 538 subscribers6 August 2026 — 538 subscribers14 August 2026 — 535 subscribers22 August 2026 — 532 subscribers30 August 2026 — 530 subscribers7 September 2026 — 525 subscribers14 September 2026 — 523 subscribers6 August 202614 September 2026
7 measurements spanning 39 days, net -15. 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 521–540 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 13:57523-2
7 Sept 2026, 23:01525-5
30 Aug 2026, 00:46530-2
22 Aug 2026, 18:13532-3
14 Aug 2026, 19:24535-3
6 Aug 2026, 18:19538no change
6 Aug 2026, 18:00538first reading

Engagement

20 posts held, back to 31 January 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 23 January 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Dec 2023, 17:32 UTC≈5,320 viewsread 6 August 2026

$TRADE gave 9x to us. More to come. $ROUTE gave 3.5x , still running 💪 $CHR pumping too🚀 Follow us more

26 Nov 2023, 18:57 UTC≈6,040 viewsread 6 August 2026

$DFYN now 3x from our call 🤜🤛 Do share this channel with your friends if you want more such calls💪

23 Nov 2023, 09:18 UTC≈5,240 viewsread 6 August 2026
Forwarded from @chromia_announcements

👀 We're incredibly proud that VfB Stuttgart chose #Chromia to power their Digital Collectibles Marketplace! 💪 We're thrilled to provide a seamless experience for Stuttgart fans, who never need to know they're using a blockchain 🤝 ➡️ Stay tuned, more information will be shared very soon! Check out their announcement: https://twitter.com/VfB/status/1727329890918416747

13 Nov 2023, 16:42 UTC≈3,780 viewsread 6 August 2026

https://x.com/polytrade_fin/status/1724094930895986846?s=46&t=IGhRVpWtxI85NwzbaP3RDw $TRADE 💪

12 Nov 2023, 15:14 UTC≈2,890 viewsread 6 August 2026

TRADE 2.5x ROUTE 60% REEF 40% Power of Bombcrypto 💪 Keep supporting us guys🙌

30 Oct 2023, 05:01 UTC≈2,830 viewsread 6 August 2026

All of them going really good. Want more? Share the channel guys.

25 Oct 2023, 18:34 UTC≈2,880 viewsread 6 August 2026

$FRONT $DFYN $ALICE $CHR $REEF $TRADE $ROUTE Already most of them up. Just added ROUTE

4 Oct 2023, 14:34 UTC≈4,990 viewsread 6 August 2026
Forwarded from @chromia_announcementsPhoto

🌐 Check how Chromia bridges the gap between traditional models and Web3 services. This benefits developers & entrepreneurs by offering cost-effective solutions, economic scalability, tokenless dapps & more while maintaining a seamless user experience! Here's the 2nd article of our Hosting Fees series ⬇️ https://blog.chromia.com/hosting-fees-are-the-key-volume-2-developers-perspective-2/

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

Forward network

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.

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

“Bomb Crypto” (@bombcrypto), 523 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/bombcrypto.

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.