Gambling & betting — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 39% 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 the other topics.
Growth
24 measurements spanning 88 days, net -781. 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 6,651–7,666 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)
Subscribers
Change
8 Nov 2026, 07:20
6,768
-28
5 Nov 2026, 10:40
6,796
-27
2 Nov 2026, 08:06
6,823
-35
30 Oct 2026, 04:07
6,858
-27
27 Oct 2026, 01:38
6,885
-20
24 Oct 2026, 04:38
6,905
-36
20 Oct 2026, 19:10
6,941
-29
18 Oct 2026, 01:17
6,970
-22
15 Oct 2026, 00:20
6,992
-17
11 Oct 2026, 21:41
7,009
-53
5 Oct 2026, 00:39
7,062
-85
25 Sept 2026, 17:40
7,147
-103
15 Sept 2026, 19:21
7,250
-50
12 Sept 2026, 04:41
7,300
-34
8 Sept 2026, 00:39
7,334
-62
3 Sept 2026, 02:38
7,396
-47
30 Aug 2026, 20:36
7,443
-27
28 Aug 2026, 02:24
7,470
+9
25 Aug 2026, 03:38
7,461
-23
21 Aug 2026, 11:34
7,484
first reading
Engagement
36 posts held, back to 17 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
1.22%
avg views ÷ 6,768 subscribers
Avg views / post
82.5
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
2
of 36 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 30 October 2026
Posts held
36 (17 June 2026 – 30 October 2026)
Views total
165
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 00:10 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈2,110
Videos
≈158
Links
≈1,540
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
49m 41s
Average length
3m 06s
Measured directly from 16 videos 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
43 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 60.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
26
60.5%
👍
13
30.2%
🔥
3
6.98%
🐳
1
2.33%
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 18 of the 36 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 43 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 17 June 2026 to 30 October 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
Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Mexc $5 CC FCFS 10K User
Go to profile and copy your
Mexc UID
Go to More & Search
"$1M Canton"
Register on the Event
Go to Learn & Earn
Scroll Down & Complete Quiz
Submit Mexc UID
Answer:
1- your mexc uid
2-A
3-B
4-B
5-A
Shin zaka iyayin kasadar $350k kimanin Naira miliyan Dari hudu da saba'in domin kawae kasamu information a wajen money launderers ?
> ZachXBT kwararren me binciken kwakwkwafi na crypto (onchain detective) mai zaman kansa yayi infiltration na wani Chinese community da suke temaka Lazarus group na North Korea wajen laundering kudin da suka sato a exchanges.
> Tun bayan exploit da Bybit suka samu last year ZachXBT ya…
Idan baka rena $2 ba sannan kanada verified X account with minimum of 100 followers, kayi wnn task din .
> ka shiga wnn link din : https://gomofamily.life/
> kayi register da X account naka, kayi connection sannan kayi authorize
> zasu baka post da zakyi akan X account naka, zakayi post din saika dauko link kayi submit
> zasuyi verify na task din sannan suyi approved na $2 din, saika jira har zuwa su sa maka ita…
> Rikici ya 6arke tsakanin Bitget Ceo Gracy , StarOKX , Goplus labs da Thorchain
> Duk kansu suna tuhumar Thorchian da cewar da saninsu suke bari ake amfani da blockchain nasu wajen exchange na kudin da akayi hacking a exchanges
> Gracy ta bayyana cewar despite that sun wallafa addresses da suke da alaqa da hacking din da aka musu publicly hakan bai hana Thorchain barin ayi amfani da routes dinsu wajen juya kudin…
> 15hrs ago Hacker din da yyi hacking bitget exchange yayi withdrawal na $1.23M dollars daga Binance zuwa address din da yake rike da kudin daya sace na bitget
> Thether da Circle masu issuing USDT & USDC sun samu nasarar freezing $318k dollars daga cikin kudin da hacker y sata.
> Bitget sun sanar cewar zasu dawo da withdrawal ranar 28 sept jibi knn , zasu fara dana bitcoin, on 29th suyi na ETH across chain , then…
> Jiya anyi hacking daya dga cikin manyan exchange mafi girma a duniya Bitget Exchange
> Kamar ydda suka sanar hackers sun saci kudi a hot and warm wallets nasu fiye da $350 million dollars
> Bitget suna zargin North korean hackers ne wato Lazarus group sukayi musu wannan ta'asa duba da ynayin hacking din da kuma tracing Ips nasu da sukayi
> Bitget sun kulle withdrawal amma har ynxu ana deposits and trading a ex…
Showing the 12 most recent of 36 posts we hold for @cryptodige. 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.
Mentions
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.
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.
AREWA STRIVERS @arewastrivers · 168,260 Telegram ranks this channel #4 of 84 here — alongside 83 others — read 11 August 2026
SCTv Africa @Sunusicryptotv · 55,389 Telegram ranks this channel #5 of 84 here — alongside 83 others — read 22 August 2026
Aminu Crypto Labs @AminuCryptoLabs · 116,878 Telegram ranks this channel #8 of 87 here — alongside 86 others — read 13 August 2026
WAZOBIA CRYPTO @wazobiacryptoo · 75,176 Telegram ranks this channel #43 of 86 here — alongside 85 others — read 24 August 2026
Arewa Trading Academy @arewatradingacademyO1 · 52,439 Telegram ranks this channel #51 of 86 here — alongside 85 others — read 24 August 2026
This channel appears in 5 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 8 November 2026 — this
entry's latest reading, not the date you are reading this.
“CRYPTO DIGEST 💰💲💪” (@cryptodige), 6,768 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/cryptodige.
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.