Lead by PAKA.Fund and jointly created by multiple TG/TON ecosystem project teams, it aims to synchronise ecosystem information and expand its influence.
由PAKA.FUND牵头，联合多个TG/TON生态项目团队，共同创建，旨在同步生态信息，扩大生态影响力。
Created
Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
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 21 August 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 14 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 8 August 2024 to 24 October 2024. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 2 channels, the one whose matching posts we hold earliest is @ceshitest0. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
68 measurements spanning 99 days, net -7,198. 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 42,621–51,979 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 68
Measured (UTC)
Subscribers
Change
13 Nov 2026, 00:49
43,701
-113
10 Nov 2026, 21:08
43,814
-55
9 Nov 2026, 07:56
43,869
-84
7 Nov 2026, 20:56
43,953
-70
6 Nov 2026, 20:25
44,023
-70
5 Nov 2026, 22:55
44,093
-44
5 Nov 2026, 02:11
44,137
-50
4 Nov 2026, 03:30
44,187
-31
3 Nov 2026, 04:47
44,218
-65
2 Nov 2026, 00:55
44,283
-67
1 Nov 2026, 00:15
44,350
-42
30 Oct 2026, 23:14
44,392
-66
29 Oct 2026, 22:56
44,458
-35
29 Oct 2026, 01:58
44,493
-93
28 Oct 2026, 00:06
44,586
-77
26 Oct 2026, 22:15
44,663
-38
25 Oct 2026, 19:41
44,701
-47
24 Oct 2026, 18:09
44,748
-85
23 Oct 2026, 19:37
44,833
-61
22 Oct 2026, 16:50
44,894
first reading
Engagement
20 posts held, back to 8 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 198 pages 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 24 October 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
39
Videos
2
Links
63
Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
253 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 50.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
127
50.2%
❤
65
25.7%
🔥
27
10.7%
🎉
11
4.35%
😭
9
3.56%
👏
4
1.58%
🤬
3
1.19%
💔
2
0.791%
🫡
2
0.791%
❤🔥
1
0.395%
😐
1
0.395%
🤷♀
1
0.395%
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 19 of the 20 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 253 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 August 2024 to 24 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Showing the 12 most recent of 20 posts we hold for @tgtoncn. 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
Named by 3 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.
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 27 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.
TBook Announcement @tbookincentive · 53,494 Telegram ranks this channel #30 of 87 here — alongside 86 others — read 27 August 2026
DeepLink Announcements Official @deeplinkchannel · 25,237 Telegram ranks this channel #51 of 58 here — alongside 57 others — read 10 September 2026
Mokoko Game Offical @MokokoGameChannel · 29,024 Telegram ranks this channel #60 of 66 here — alongside 65 others — read 5 September 2026
Bot Gameyard @BotGameyard · 28,287 Telegram ranks this channel #62 of 75 here — alongside 74 others — read 6 September 2026
Scalr News @scalr_dex · 36,111 Telegram ranks this channel #64 of 69 here — alongside 68 others — read 30 August 2026
PixelSwap @PixelSwap_io · 463,211 Telegram ranks this channel #67 of 85 here — alongside 84 others — read 27 August 2026
Pumpkin | Community 🎃 @pumpkin_global · 22,440 Telegram ranks this channel #69 of 72 here — alongside 71 others — read 15 September 2026
AKEFish News @akefishchannel · 600,740 Telegram ranks this channel #82 of 87 here — alongside 86 others — read 27 August 2026
BOOM UP @boomup_game · 54,836 Telegram ranks this channel #87 of 87 here — alongside 86 others — read 27 August 2026
This channel appears in 9 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 13 November 2026 — this
entry's latest reading, not the date you are reading this.
“TG/TON Community（华语）” (@tgtoncn), 43,701 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/tgtoncn.
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.
