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 9 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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
54 measurements spanning 86 days, net -1,367. 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 36,534–38,311 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 54
Measured (UTC)
Subscribers
Change
31 Oct 2026, 06:27
36,739
-21
30 Oct 2026, 03:47
36,760
-80
29 Oct 2026, 03:36
36,840
-20
28 Oct 2026, 02:50
36,860
-16
27 Oct 2026, 01:30
36,876
-26
26 Oct 2026, 01:09
36,902
-10
25 Oct 2026, 00:54
36,912
-7
23 Oct 2026, 21:46
36,919
-11
22 Oct 2026, 22:36
36,930
-19
21 Oct 2026, 23:29
36,949
-26
20 Oct 2026, 20:10
36,975
-11
19 Oct 2026, 22:09
36,986
-18
18 Oct 2026, 20:37
37,004
-10
17 Oct 2026, 21:36
37,014
-6
16 Oct 2026, 21:05
37,020
-12
15 Oct 2026, 19:11
37,032
-19
14 Oct 2026, 16:55
37,051
-33
13 Oct 2026, 06:59
37,084
-60
9 Oct 2026, 04:38
37,144
-90
4 Oct 2026, 19:39
37,234
first reading
Engagement
128 posts held, back to 23 July 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 158 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
3.01%
avg views ÷ 36,739 subscribers
Avg views / post
1,110
18 posts measured
Reaction rate
0.558%
reactions ÷ views · ER floor
Posts in window
32
of 128 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
128 (23 July 2026 – 30 October 2026)
Views total
19,902
Reactions total
111
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
31 Oct 2026, 02:04 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.
Reaction mix
609 reactions across 75 posts, in 23 distinct kinds. The most used accounts for 50.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
310
50.9%
😭
83
13.6%
👍
63
10.3%
🔥
48
7.88%
😁
19
3.12%
🍌
13
2.13%
👏
11
1.81%
🙏
11
1.81%
🗿
8
1.31%
🥰
7
1.15%
🤩
6
0.985%
☃
5
0.821%
🎄
5
0.821%
🤔
5
0.821%
🤯
4
0.657%
❤🔥
2
0.328%
💔
2
0.328%
😈
2
0.328%
🌚
1
0.164%
🎉
1
0.164%
3 further kinds
3
0.493%
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 75 of the 128 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 609 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 128 most recent posts we hold, published 23 July 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.
Some things are worth the wait.
Our Halloween gift for VIPs, crafted in black, orange and green.
Become a VIP and unlock more perks ahead.
https://my.cwallet.com/vip
With gratitude, Cwallet.
---
🔗 Official Website | Help Center | Community | Blog | Learn
👛 Web Wallet | App Store | Google Play | Telegram Bot
📱Twitter | 📱Facebook | 📱 Ins | 📱 TikTok
Trade everything in one wallet. 🟢
Spot, perps, xStocks, swaps and cards, all inside Cwallet.
No more jumping between apps.
👉 https://cwallet.com/
Your whole portfolio, one tap away.
---
🔗 Official Website | Help Center | Community | Blog | Learn
👛 Web Wallet | App Store | Google Play | Telegram Bot
📱Twitter | 📱Facebook | 📱 Ins | 📱 TikTok
3 days to Halloween. 🎃
Something spooky is brewing at Cwallet: trading events, surprises, and rewards. 👻
👉 Stay tuned in our community: https://discord.gg/gJWPuQQ3bu
Trick or trade? You’ll find out soon. 🦇
---
🔗 Official Website | Help Center | Community | Blog | Learn
👛 Web Wallet | App Store | Google Play | Telegram Bot
📱Twitter | 📱Facebook | 📱 Ins | 📱 TikTok
Spread Rush is live on Cwallet! ⚡
Pick a time (5s or 15s), call Up or Down, and get up to +65% payout in seconds. 🔥
👉 Try it now: https://my.cwallet.com/trade/spread
Quick calls. Fast results. Ready to rush? 🚀
---
🔗 Official Website | Help Center | Community | Blog | Learn
👛 Web Wallet | App Store | Google Play | Telegram Bot
📱Twitter | 📱Facebook | 📱 Ins | 📱 TikTok
Attention | SUI Network Infrastructure Upgrade
Dear Users,
To ensure a more stable and high-performance trading experience, Cwallet is currently conducting a critical upgrade to our SUI network infrastructure.
The maintenance period is scheduled to last for approximately one week.
During this upgrade window, service adjustments will be as follows:
· Deposits for SUI and tokens on the SUI network will remain fully…
Two traders. One price move. Who’s right?
Market Battle on Cwallet: pick your side and go head-to-head. 🔥
👉 Enter the battle: https://my.cwallet.com/trade/market-battle
Make your call and win the battle. 🏆
---
🔗 Official Website | Help Center | Community | Blog | Learn
👛 Web Wallet | App Store | Google Play | Telegram Bot
📱Twitter | 📱Facebook | 📱 Ins | 📱 TikTok
Every trend starts with a prediction. 🔮
Prediction on Cwallet lets you back your view on the market in just a few taps. ⚡
👉 Try it now: https://my.cwallet.com/predict/trending
Trust your instincts and make your call today. ✨
---
🔗 Official Website | Help Center | Community | Blog | Learn
👛 Web Wallet | App Store | Google Play | Telegram Bot
📱Twitter | 📱Facebook | 📱 Ins | 📱 TikTok
Showing the 12 most recent of 128 posts we hold for @CwalletNews. 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.
Posts edited after publishing
@CwalletNews edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
20 August 2026
Most recent edit
7 September 2026
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@CwalletNews named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@cwalletofficial named in 3 posts, 8 August 2026 – 10 August 2026
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 31 October 2026 — this
entry's latest reading, not the date you are reading this.
“Cwallet News” (@CwalletNews), 36,739 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/CwalletNews.
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.