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,336subscribers

-765 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 官方公告 @tiancheng 担保负责人 @tctc 出海负责人 @bcbc 仲 裁 组 @tczc 24小时客服机器人 @tckf 免费记账机器人 :@tcjz
CreatedBetween 1 September 2021 and 31 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 10 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
@JiuDingSAD359 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (352–7)
@tcdbgxpdd342 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (336–6)
@tdgx988330 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (325–5)

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. 18 of the 18 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,044 comparable posts for this entry, running 7 August 2026 to 11 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 12 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,3367 August 202610 November 2026
64 measurements spanning 95 days, net -765. 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 64
Measured (UTC)SubscribersChange
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,141-89
22 Oct 2026, 14:19194,230-44
21 Oct 2026, 11:19194,274first reading

Engagement

3,207 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 199 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.324%
avg views ÷ 193,336 subscribers
Avg views / post
626
1,029 posts measured
Reaction rate
0.283%
reactions ÷ views · ER floor
Posts in window
1,042
of 3,207 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 353 of 1,029 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 12 November 2026
Posts held3,207 (7 August 2026 – 12 November 2026)
Views total643,884
Reactions total683
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 15:46 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,650

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

673 reactions across 293 posts, in 17 distinct kinds. The most used accounts for 32.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍21932.5%
❤16925.1%
💔649.51%
💩608.92%
🔥334.90%
😱324.75%
🤮324.75%
👎162.38%
🤬162.38%
🤔152.23%
🤡60.892%
🤣50.743%
👏20.297%
🎉10.149%
🏆10.149%
👌10.149%
🥰10.149%

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 344 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 673 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 15 October 2026 to 12 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: 214 of 1,042 posts held from the last 30 days (20.5%) 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).

12 Nov 2026, 15:39 UTC94 viewsread 12 November 2026

【OK游戏中心】 🔥富贵集团旗下富贵娱乐综合U台 🎰电子 📹视讯 🇨🇦彩票 ⚽️体育 🎣 捕鱼 ♠️棋牌 上千款官方正版厂商游戏 实时反水最高5% 代理合作返佣最高50% 储备金上亿U 大玩家最稳首选 ✅OK游戏中心-公群520 上押150万U 富贵娱乐: @FGYL 官方客服: @FGKF 官方网站: Fugui.game ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

12 Nov 2026, 15:29 UTC184 views1 reactionsread 12 November 2026

公群001 代客寻找海外多国支付通道 长期寻找一类BC海外一手源头实力支付通道,支持上押合作/通道稳定/成功率高/费率合理,实力盘口嘎嘎有量 联系人:@BCBC https://t.me/+SMSAA3fpwScyYzdl ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

👍1

12 Nov 2026, 15:07 UTC356 views7 reactionsread 12 November 2026

公群3468 押金1588.8u 菠菜直盘高价招U商/直拿模式车队 点位22,零风险模式,bc直盘,赌客人民币换U上分,小白可全程指导,手把手带你赚钱,保证做一周本金翻倍,准备1万U起做,支持验盘100%保证,可签订免责合同 联系人:@III662 https://t.me/+3HdkyVdqTZs1YzI8 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

👍2🤬2❤1👏1🥰1

12 Nov 2026, 14:52 UTC421 views1 reactionsread 12 November 2026

公群1618 押金5000u 淘宝拉单支付宝代付码必过 淘宝拉单 -支付宝代付码 单笔200-999连刷必过 支付宝余额 花呗 储蓄卡 信用卡 联系人:@f5666888 https://t.me/+PdHR5vf4yUFmNjg1 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

👍1

12 Nov 2026, 14:33 UTC478 viewsread 12 November 2026

🔥8G国际娱乐全网最稳综合U台 官网: 8G.COM okpay钱包—ok游戏中心上押300万美金:61公群8G国际娱乐上押300万U 🎰电子 📹视讯 🇨🇦彩票 ⚽️体育 🎣 捕鱼,上千款官方正版厂商游戏 真人视讯全网最高反水1%,投注输口赢口双边计算都计算反水 PC28综合U台全网最高赔率,投注输口赢口双边计算都计算反水 全网福利最多:活动救援金、亏损金、返佣金、充值金、闯关奖、充值额外奖、周福利、月福利,频道每日6个红包 🥇储备金上亿U 两大头部担保 全网上押1300万U 大玩家最稳首选 📹真人视讯下注20万U一口 🎰PG电子麻将糊了2000U一注 🤝代理合作返佣最高达50% 官方网址: 8G.COM 官方客服:@KF8G 官方投注:@TG8G ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

12 Nov 2026, 14:15 UTC494 viewsread 12 November 2026

公群151 押金4158u 抢单平台/刷单平台/交易所/蜘蛛池/发卡搭建/机器人 刷单,抢单,交易所,虚拟币平台,机器人搭建,落地页,搭建维护,暗箭,ios源码,二开,海外平台,刷单包网,刷单盘,抢单,仿站,平台包网,谷歌,商城平台,爆单抢单,能量机器人,发卡, 联系人: @ymw388 https://t.me/+hZLMamJ9i4YxMTE1 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

12 Nov 2026, 14:08 UTC473 viewsread 12 November 2026

【OK游戏中心】 南宫旗下:万豪集团入驻OK游戏中心 🫥游戏中心上押【140万U】 @OK28 😁万豪PC2.0 超级🈵 13/14也赔2倍 公群288 🤖点击PC2.0私聊下注🤖 ———————————————— 😁万豪PC网盘 超级🈵 13/14正常赔付 公群388 🤖点击PC网盘私聊下注🤖 ———————————————— 😁万豪PC流水 超级🈵💦一万返水320 公群866 🤖点击PC2.0流水私聊下注🤖 ———————————————— 😁万豪PC2.84 超级🈵赔 组合高倍玩法 公群788 🤖点击PC2.84私聊下注🤖 ———————————————— 不限制玩法,支持一把下分! 官方客服: @WH66 @WH88 🛡祝各位老板,旗开得胜! ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

12 Nov 2026, 13:30 UTC568 views1 reactionsread 12 November 2026

🤩【天成百万业务增长计划】正式开启! 💰百万专项资金已上线,做单就有机会拿激励! 🔥 公群老板|做单小弟|购买供需 都可申请加入 ✅ 做单越多,激励越高 ✅ 群人数增长,红包雨持续发放 📢 官方活动群 【天成做单百万补贴交流群】 进群审核请联系: 活动专员 担保选天成,万事皆可成。

👍1

12 Nov 2026, 13:29 UTC579 views1 reactionsread 12 November 2026

公群2439 押金3198u 云捷|阿里云|腾讯云|AWS|免实名服务器 阿里云备案域名 腾讯云备案域名 华为云 微软云 亚马逊 谷歌云 短信宝实名 网易云信实名 聚名网实名 西部数码 dcloud实名 联系人: @HHHYYY @HHHNNN https://t.me/+-r7GntS6uEM1MWQ0 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

👍1

12 Nov 2026, 13:24 UTC517 views1 reactionsread 12 November 2026

公群906 押金5999u 众诚海外苹果/贝宝/泽尔/礼品卡核销公群 批量核销苹果/雷蛇/steam/xbox/psn/Roblox/塔吉特/丝芙兰/梅西.露露/优步,沃尔玛/劳氏,始祖鸟/游戏驿站等礼品卡 联系人:@zc998802 https://t.me/+E8KJ6Vp6AfxkOWVk ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

👍1

12 Nov 2026, 13:07 UTC541 viewsread 12 November 2026

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

12 Nov 2026, 13:04 UTC470 viewsread 12 November 2026

公群370 押金6666u 智博体育/内幕红单/精准球料不中包赔 体育红单|精准球料|足球料|NBA料|不中包赔,赢了提现带走输了本金还你! 联系人:@zb925 https://t.me/+8rqh3UznOXE4NDA1 ⭐️交易必须走天成担保,所有业务联系 天成客服 @TCKF ⭐️

Showing the 12 most recent of 3,207 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“天成供需频道” (@tcgx), 193,336 subscribers as measured 10 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.