Telegram RegisterThe public register of Telegram
Telegram profile photo for 天才供需频道

Channel

天才供需频道

@tcgx

2 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

193,038subscribers

-1,063 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001599443040
TypeChannel
Usernames@tcgx @tdgx708
Description供需频道 @tcgx 公群频道 @tcgq 招商频道 @tczs 官方大群 @tcdb 每日公群 @tcxq 官方公告 @jdtc 担保负责人 @tctc 出海负责人 @bcbc 仲 裁 组 @tczc 24小时客服机器人 @tckf 免费记账机器人 :@tcjz
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/tcgx

Topic

Gambling & betting — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 71% 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 3 other registered channels. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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)
Posted firstThenOverlapGap
@tcgx/99765 · this entry8 Aug 2026, 08:05 UTC@JiuDingSAD/100228 Aug 2026, 08:06 UTC1.00under a minute
@tcgx/100080 · this entry17 Aug 2026, 08:28 UTC@JiuDingSAD/1037718 Aug 2026, 09:57 UTC1.0025 hours
@tcgx/100365 · this entry27 Aug 2026, 10:18 UTC@JiuDingSAD/1062227 Aug 2026, 10:18 UTC1.00under a minute
@tcgx/100434 · this entry29 Aug 2026, 13:39 UTC@JiuDingSAD/1069129 Aug 2026, 13:39 UTC1.00under a minute
@tcgx/102312 · this entry7 Oct 2026, 13:07 UTC@JiuDingSAD/142423 Nov 2026, 13:07 UTC1.0027 days
@tcgx/104132 · this entry5 Nov 2026, 18:04 UTC@JiuDingSAD/143845 Nov 2026, 18:04 UTC1.00under a minute
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
ChannelMatching postsText overlapTypical gapPublished first
@JiuDingSAD408 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (398–10)
@tcdbgxpdd385 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (375–10)
@tdgx988374 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (364–10)

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. 30 of the 30 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 3,194 comparable posts for this entry, running 7 August 2026 to 16 November 2026. 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 4 channels, the one whose matching posts we hold earliest is @tcgx — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 17 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 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.

Growth

189,744195,441192,592.5193,0387 August 202616 November 2026
66 measurements spanning 101 days, net -1,063. 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 188,889–196,296 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
16 Nov 2026, 20:48193,038-289
13 Nov 2026, 08:18193,327-9
10 Nov 2026, 19:49193,336-16
9 Nov 2026, 03:15193,352-108
7 Nov 2026, 19:47193,460-18
6 Nov 2026, 17:29193,478-113
5 Nov 2026, 15:47193,591-176
4 Nov 2026, 17:57193,767-332
3 Nov 2026, 17:56194,099-82
2 Nov 2026, 19:47194,181+90
1 Nov 2026, 22:21194,091+2
31 Oct 2026, 20:30194,089-13
30 Oct 2026, 19:38194,102-49
29 Oct 2026, 19:39194,151-83
28 Oct 2026, 16:07194,234+56
27 Oct 2026, 13:36194,178-36
26 Oct 2026, 16:25194,214-61
25 Oct 2026, 13:19194,275+76
24 Oct 2026, 10:30194,199+58
23 Oct 2026, 11:15194,141first reading

Engagement

3,343 posts held, back to 7 August 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 208 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.32%
avg views ÷ 193,038 subscribers
Avg views / post
619
997 posts measured
Reaction rate
0.304%
reactions ÷ views · ER floor
Posts in window
1,009
of 3,343 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. It is computed over the 352 of 997 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held3,343 (7 August 2026 – 17 November 2026)
Views total616,771
Reactions total717
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 04:02 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

Links
≈5,790

Lifetime counters from Telegram’s own channel header, read 17 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.

Reaction mix

717 reactions across 305 posts, in 16 distinct kinds. The most used accounts for 35.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍25235.1%
❤18425.7%
👎8011.2%
💩547.53%
🔥456.28%
🤮446.14%
🤬243.35%
🤔152.09%
🤡60.837%
🤣50.697%
👏20.279%
💔20.279%
🎉10.139%
🏆10.139%
👌10.139%
🥰10.139%

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 351 of the 1,000 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 717 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 October 2026 to 17 November 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: 228 of 1,009 posts held from the last 30 days (22.6%) 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).

17 Nov 2026, 03:51 UTC103 views2 reactionsread 17 November 2026

公群152 押金2188u 1TRX闪租转u 招代理 一笔能量1TRX节约7trx手续费 两笔能量2TRX节约14trx手续费 百分百能量长期稳定 购买TRX全网最高兑换TRX汇率 联系人:@jinyiTRX @bdqsgstbot https://t.me/+sdLawZfacvFiY2I9 ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

👍2

17 Nov 2026, 03:45 UTC151 views2 reactionsread 17 November 2026

公群1864 押金5088u 群引导/中油下载付 中油下载付24小时在开,可贴号 可引导,来会打的实力水房盘口。 联系人:@Xx_0008 @vip_xy888 https://t.me/+7pFqjIZ7t9dmNDc1 ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

👍2

17 Nov 2026, 03:40 UTC189 views2 reactionsread 17 November 2026

公群984 押金10099u 【九星集团】出售·全行业精准数据(可指定要求)24小时在线接单 头部数据商(WPK/DPI/SDK/体彩/棋牌/bc/六合彩/3D福彩/各类游戏/贷款/助贷/催收/外贸/换汇/相亲/全球华侨华人/银行内鬼) 联系人:@jxsj333 https://t.me/+TLNrvTAg8Bc4ODc8 ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

👍2

17 Nov 2026, 02:00 UTC458 viewsread 17 November 2026

公群3642 押金5000u 收U放料作业群 纯传销资金盘前期料子保月 保15 保7 纯传销资金盘前期料诚招支付宝微信聚合码丝滑码H5银行码马车料性温和可保月七天内客诉司法 长期招中介/实力卡车.码车.自带维护,日切百万量,来就she,秒沙市场价 联系人: @Hu_8888888 https://t.me/+-4IU0ZmGBGs2NDg0 ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

16 Nov 2026, 18:37 UTC981 viewsread 17 November 2026

公群5988 押金2000u 掴内菠菜源头数据丨任意APP/SDK/DPI/渗透 一手源头/非中介,指定APP/任意网址链接用戸抓取,可验证技术实力!主营:彩票/六合/体育/电子/综合/德州/菠菜钱包精准数据 联系人:@jiuyuejiu https://t.me/+ZKrU_EFmWTE4Y2Nl ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

16 Nov 2026, 18:02 UTC938 viewsread 17 November 2026

【OK游戏中心】 9Y.COM玩9Y赢9亿 公群9 9Y综合盘 OK游戏中心 入驻300万U 视讯 — 索莱尔/DB/CQ9高限红 电子 — PG/PP/CQ9 一注2000 彩票 — 独家综艺PC28/哈希彩 官方网址: 9Y.COM 官方小程序:@GF9Y 官方唯一客服:@KF9Y OK游戏中心PC28在押公群 🇨🇦 PC2.0超🈵赔【13/14也赔2倍】不限玩法 🇨🇦 PC2.84超🈵赔【不限玩法,秒下分】 🇨🇦 PC2.0网盘🈵赔【组合13/14正常赔付】不限玩法 ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

16 Nov 2026, 17:37 UTC779 views2 reactionsread 17 November 2026

公群70761 押金10000u 0.01TRX转U0手续费(笔笔不扣0.35TRX) 业务内容:0.01TRX转U0手续费,每天用每天省!笔笔不扣0.35TRX,一年省下来,买车更近一步。 联系人:@ameitrx @atrx https://t.me/+haOyPj0yQD42ZmFl ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

❤1🤬1

16 Nov 2026, 17:35 UTC712 views7 reactionsread 17 November 2026

公群8233 押金3888.88u 财源直盘招手机小时达 (紧急通知)直盘招苹果18手机小时达接货车队不走卡不过流水利润48点 不挑地区 全新模式 低风险不按tou 散户可扶持 联系人:@cawwww @hpuuuu https://t.me/+x1UJDQmG49xhMjI1 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

❤2👍2🔥2🤬1

16 Nov 2026, 17:01 UTC694 viewsread 17 November 2026

【OK游戏中心】 🔥富贵集团旗下富贵娱乐综合U台 🎰电子 📹视讯 🇨🇦彩票 ⚽️体育 🎣 捕鱼 ♠️棋牌 上千款官方正版厂商游戏 富贵天选|万券豪礼盛宴 🥇一等奖|保时捷 折现 88888U 🥈二等奖|奔驰C 折现 38888U 🥉三等奖|劳力士 折现 18888U 🏅四等奖|现金大奖   8888U 📱幸运奖|iPhone 18 最高 92 部 👉 活动详情 · 奖券进度 · 开奖公告 ✅OK游戏中心-公群520 上押150万U 富贵官网: 9N.COM 富贵娱乐: @FGYL 富贵客服: @FGKF ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

16 Nov 2026, 16:29 UTC731 views1 reactionsread 17 November 2026

【OK游戏中心】 🔥 九星集团入住【OK游戏中心】新群冲业绩🧧福利多多💰💰 👇九星集团OK游戏中心担保群组 ——————————————— 公群955 九星集团🇨🇦PC网盘超🈵赔 上押60万 🤖OK超满网盘游戏机器人 公群959 九星集团🇨🇦PC2.0超🈵赔 已押20万 🤖OK超满2.0游戏机器人 公群995 九星集团🇨🇦PC2.84倍超🈵 已押20万 🤖OK超满2.84游戏机器人 OK游戏中心 九星集团🇨🇦PC28系列上下分群 已押60万 ——————————————— 九星阳光客服 @jxxxpc 九星晚霞客服 @jxxxbc 九星集团PC28每晚研报频道 @jxjtvip ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

👍1

16 Nov 2026, 16:05 UTC748 viewsread 17 November 2026

公群1042 押金6888u meiguo空降涩敲/股民/华侨涩粉数据投资兼职精聊数据 meiguo,巴基斯坦,印度,印尼,尼日利亚,墨西哥,马来,新加坡(股票/ 兼职/bc) 联系人: @CRS668 https://t.me/+VEaOM5OAx0IzNjE0 ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

16 Nov 2026, 16:00 UTC731 views0 reactionsread 17 November 2026

公群6490 押金5000u 旺旺集团全天一道码接/卡接回u 各类大车直供[100-5w大小额通沙]:大额扫街码/支付宝/微信个码 经营码/大额 卡 /大额支付宝账号/各种丝滑通道需要的老板联系 24小时作业 有通道各位料主 欢迎来咨询 汇率冰点 吃大混以及大混内在开 联系人:@wanggwo168 https://t.me/+JSs8nraLukZhYjA1 ⭐️交易必须走天才担保,所有业务联系 @TCKF 官方客服 ⭐️

Showing the 12 most recent of 3,343 posts we hold for @tcgx. 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

@tcgx edited 16 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
8 August 2026
Most recent edit
7 November 2026

Mentions

Named by 22 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.

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.

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“天才供需频道” (@tcgx), 193,038 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/tcgx.

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.