10 Aug 2024, 14:00 UTCviews —
Channel created
Channel
Crypto《⁷》♡≠$
@bbxbdjdhdvjdjdh
On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
739subscribers
-7 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 | -1002162233142 |
|---|---|
| Type | Channel |
| Username | @bbxbdjdhdvjdjdh |
| Created | 10 August 2024 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/bbxbdjdhdvjdjdh |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 08:54 | 739 | -7 |
| 8 Aug 2026, 02:02 | 746 | no change |
| 7 Aug 2026, 13:54 | 746 | first reading |
Engagement
1 post held, back to 10 August 2024 — 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 1 post for this entry, the most recent from 10 August 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
Showing the 1 most recent of 1 post we hold for @bbxbdjdhdvjdjdh. 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Ali Hasani
@alihasanivip · 498,038
Telegram ranks this channel #17 of 65 here — alongside 64 others — read 12 August 2026
@alihasanivip · 498,038
Telegram ranks this channel #17 of 65 here — alongside 64 others — read 12 August 2026
کریپتو گلکسی | 𝗦𝗜𝗚𝗡𝗔𝗟
@Galaxy_XSignal · 111,301
Telegram ranks this channel #18 of 66 here — alongside 65 others — read 14 August 2026
@Galaxy_XSignal · 111,301
Telegram ranks this channel #18 of 66 here — alongside 65 others — read 14 August 2026
𝑪𝑹𝒀𝑷𝑻𝑶𝑶_𝑨𝑩
@cryptoo_ab · 390,560
Telegram ranks this channel #23 of 64 here — alongside 63 others — read 10 August 2026
@cryptoo_ab · 390,560
Telegram ranks this channel #23 of 64 here — alongside 63 others — read 10 August 2026
دلقک نباشیم
@DontBeAnClown · 156,840
Telegram ranks this channel #38 of 76 here — alongside 75 others — read 12 August 2026
@DontBeAnClown · 156,840
Telegram ranks this channel #38 of 76 here — alongside 75 others — read 12 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Crypto《⁷》♡≠$” (@bbxbdjdhdvjdjdh), 739 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/bbxbdjdhdvjdjdh.
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.