Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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
46 measurements spanning 76 days, net +7,491. 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 103,338–149,126 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 46
Measured (UTC)
Subscribers
Change
22 Oct 2026, 14:26
133,591
-4,011
21 Oct 2026, 10:10
137,602
-4,366
20 Oct 2026, 07:20
141,968
-901
19 Oct 2026, 05:47
142,869
-974
18 Oct 2026, 08:00
143,843
+13,897
17 Oct 2026, 10:21
129,946
-427
16 Oct 2026, 12:06
130,373
-863
15 Oct 2026, 14:37
131,236
-943
14 Oct 2026, 17:46
132,179
-1,436
13 Oct 2026, 08:36
133,615
+3,654
9 Oct 2026, 02:17
129,961
-941
4 Oct 2026, 16:56
130,902
+15,335
26 Sept 2026, 17:37
115,567
-20
19 Sept 2026, 13:54
115,587
-1,799
17 Sept 2026, 03:40
117,386
-3,273
15 Sept 2026, 05:18
120,659
-1,551
13 Sept 2026, 16:41
122,210
-2,989
12 Sept 2026, 00:58
125,199
-3,281
9 Sept 2026, 18:35
128,480
+8,918
6 Sept 2026, 08:37
119,562
first reading
Engagement
197 posts held, back to 31 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 161 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
6.12%
avg views ÷ 133,591 subscribers
Avg views / post
8,170
68 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
70
of 197 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 22 October 2026
Posts held
197 (31 July 2026 – 22 October 2026)
Views total
555,710
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
23 Oct 2026, 04:31 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
≈1,360
Videos
≈141
Links
≈1,460
Lifetime counters from Telegram’s own channel header, read 23 October 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
5m 53s
Average length
39s
Measured directly from 9 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.
Showing the 12 most recent of 197 posts we hold for @cryptogems55552. 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
@cryptogems55552 edited 6 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
19 August 2026
Most recent edit
12 October 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 1 registered channel — 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
5
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
4
vacant every time we have ever looked
@cryptogems55552 named 5 handles 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@qlim_flap named in 4 posts, 9 August 2026 – 16 August 2026 · confirmed gone 20 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@errorglitchsol named in 6 posts, 9 September 2026 – 18 September 2026
@marvin_erc20 named in 5 posts, 8 September 2026 – 13 September 2026
@solicoinx named in 4 posts, 24 August 2026 – 1 September 2026
@binancecat_portal named in 3 posts, 24 August 2026 – 1 September 2026
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 14 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
CGT ASIAN COMMUNITY @ChineasswhalesCGT · 48,446 Telegram ranks this channel #3 of 65 here — alongside 64 others — read 1 September 2026
GEMS OF CCCCN|| 中国加密跨链网络|| @CHINAGEMOFCCCN · 92,183 Telegram ranks this channel #3 of 92 here — alongside 91 others — read 18 August 2026
Moontok 月兔 @moonspace · 15,589 Telegram ranks this channel #6 of 72 here — alongside 71 others — read 4 October 2026
🐳CHINESE CRYPTO WHALES 🇨🇳🇨🇳💷 🐳 || 大鯨魚 @WHALESPUMPBANK · 23,541 Telegram ranks this channel #6 of 79 here — alongside 78 others — read 18 September 2026
𝐓𝐀𝐊𝐀𝐍𝐀 𝐄𝐓𝐇 𝐒𝐮𝐫𝐠𝐞 𝐊𝐨𝐥𝐬🪐 @takanaeth101 · 33,916 Telegram ranks this channel #6 of 74 here — alongside 73 others — read 2 September 2026
Topresale 💎 @topresale · 93,950 Telegram ranks this channel #7 of 85 here — alongside 84 others — read 18 August 2026
中国密码鲸公司 🇨🇳🐳🚀🌖 @ChinapumpWXC · 110,767 Telegram ranks this channel #9 of 90 here — alongside 89 others — read 14 August 2026
看涨中國人 🇨🇳 DRAGON CALL ☏ @Chinese_dragon_calls · 111,088 Telegram ranks this channel #12 of 90 here — alongside 89 others — read 24 August 2026
☎️熊猫泵营销渠道 (PANDA MARKETING &CALLS[TRX ETH SOL BSC TON]🈵 ⛩️🇨🇳 @pandacallslonge3 · 55,653 Telegram ranks this channel #19 of 86 here — alongside 85 others — read 24 August 2026
Shakers Calls @marine_CryptoCalls · 72,810 Telegram ranks this channel #41 of 91 here — alongside 90 others — read 20 August 2026
Yono Upay @Free_ke_Loots · 28,065 Telegram ranks this channel #44 of 59 here — alongside 58 others — read 7 September 2026
ᗰᗩYᗷᗩᑕᕼ 鲸鱼 💮 @maybac_whales · 53,259 Telegram ranks this channel #46 of 75 here — alongside 74 others — read 30 August 2026
𝐙𝐄𝐔𝐒 𝐆𝐄𝐌 💎 @zeus_gem · 64,596 Telegram ranks this channel #47 of 81 here — alongside 80 others — read 21 August 2026
Tesla Calls Official @Teslacallsofficial · 75,650 Telegram ranks this channel #63 of 76 here — alongside 75 others — read 30 August 2026
DeFi Doxx Calls @Defidoxxcalls · 32,707 Telegram ranks this channel #65 of 76 here — alongside 75 others — read 5 September 2026
Global Explore Calls 📉📈 @GlobalExploreCalls · 30,158 Telegram ranks this channel #70 of 71 here — alongside 70 others — read 24 September 2026
Angry Birds Calls™📢 @Angrybirdscalls · 42,231 Telegram ranks this channel #71 of 80 here — alongside 79 others — read 4 September 2026
Crypto 100X Gems 🚨️ @TheCrypto100XGems · 22,408 Telegram ranks this channel #72 of 79 here — alongside 78 others — read 9 September 2026
Crypto Panda Gems💎 @CryptoPandaGems_1 · 19,535 Telegram ranks this channel #73 of 75 here — alongside 74 others — read 1 September 2026
Crypto King Call @Crypto_KingCall · 105,597 Telegram ranks this channel #73 of 91 here — alongside 90 others — read 15 August 2026
Cookie sale's 🍪 @Cookiesales · 78,299 Telegram ranks this channel #74 of 93 here — alongside 92 others — read 18 August 2026
🦄 𝗔𝗹𝗽𝗵𝗮 𝗪𝗵𝗮𝗹𝗲𝘀 𝗖𝗮𝗹𝗹𝘀🐳 @AlphaWhale_Calls · 21,192 Telegram ranks this channel #75 of 75 here — alongside 74 others — read 30 September 2026
𝐂𝐫𝐲𝐩𝐭𝐨 𝐒𝐮𝐩𝐞𝐫 𝐆𝐞𝐦𝐬 🚀🚀 @CryptoSuper_Gems · 15,861 Telegram ranks this channel #76 of 78 here — alongside 77 others — read 8 September 2026
MiniDraft Calls @minidraftcalls · 78,161 Telegram ranks this channel #86 of 93 here — alongside 92 others — read 20 August 2026
This channel appears in 24 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 22 October 2026 — this
entry's latest reading, not the date you are reading this.
“☎️中国宝石-匚卄丨几乇丂乇🐳” (@cryptogems55552), 133,591 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/cryptogems55552.
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.