Telegram RegisterThe public register of Telegram

Channel

金年会招商中心

@xcty_gfzszx

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,589subscribers

-3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001629477153
TypeChannel
Username@xcty_gfzszx
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/xcty_gfzszx

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

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 word for word on 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@jinnianhui011/14214 Jun 2026, 23:34 UTC@xcty_gfzszx/506 · this entry14 Jun 2026, 23:35 UTC1.00under a minute
@jinnianhui011/14318 Jun 2026, 07:05 UTC@xcty_gfzszx/508 · this entry18 Jun 2026, 07:07 UTC1.0072 seconds
@jinnianhui011/14626 Jun 2026, 16:49 UTC@xcty_gfzszx/512 · this entry26 Jun 2026, 16:49 UTC1.00under a minute
@jinnianhui011/14729 Jun 2026, 02:45 UTC@xcty_gfzszx/514 · this entry29 Jun 2026, 02:46 UTC1.00under a minute
@jinnianhui011/1506 Aug 2026, 05:25 UTC@xcty_gfzszx/526 · this entry6 Aug 2026, 05:26 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@jinnianhui0115 (5/5 hand-verifiable sample passed)1.00under a minute@jinnianhui011 (50)

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. 1 of the 5 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 11 comparable posts for this entry, running 14 June 2026 to 6 August 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).

Across the whole group of 2, the earliest publisher we hold is @jinnianhui011. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

2,5892,5922,590.57 August 2026 — 2,592 subscribers7 August 2026 — 2,592 subscribers10 August 2026 — 2,589 subscribers7 August 202610 August 2026
3 measurements spanning 3 days, net -3. 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 2,589–2,592 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 22:212,589-3
7 Aug 2026, 19:482,592no change
7 Aug 2026, 19:032,592first reading

Engagement

19 posts held, back to 14 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.452%
avg views ÷ 2,589 subscribers
Avg views / post
11.7
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 19 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
WindowRolling 30 days · latest post in window 6 August 2026
Posts held19 (14 June 20266 August 2026)
Views total82
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 19:03 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.0%

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

Measured over the 19 most recent posts we hold, published 14 June 2026 to 6 August 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

6 Aug 2026, 05:26 UTC6 viewsread 7 August 2026
Photo

年关已过大半,五大联赛即将开始,金年会数字站豪客首选平台,世界杯待遇如下: 😂活动1:长期55%佣金 五个有效新增即可享受 😂活动2:人头费最高239999人民币 🪙活动3:不计输赢流水佣金每月最高77777 😂活动4:会员高额首存日存彩金实时派发 🚀活动5:介绍朋友最高可享8%介绍佣金 🪙会员u存u取可绑定TG,世界杯恭候各大豪客前来娱乐 😂😂😂开线扶持拉满欢迎优质大代洽谈业务!一切待遇可谈😄😄😄 🫥🫥🫥 🪙🪙游戏链接: jnh707.cc 😀 洽谈合作 😀 😀 😀 😀 最靠谱招商-景天TG:@jnh707 😀 赛事红单推荐: @TIYU83 #金年会 #代理 #pg电子 #麻将糊了 #美加墨世界杯

3 Aug 2026, 18:21 UTC8 viewsread 7 August 2026

— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。

27 Jul 2026, 18:20 UTC14 viewsread 7 August 2026

— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。

27 Jul 2026, 08:12 UTC10 viewsread 7 August 2026
Photo

重要提醒♾重要提醒♾重要提醒♾ 重要的事情说三遍!!! 📌活跃人数不足5人是拿不到佣金的,临近月底一定要及时查看, 看看自己线上 新增活跃不够的 ,抓紧时间上人了哦,抓紧时间冲刺新增,避免因人数不足拿不到佣金或者是更高的佣金比例。 【温馨提醒:不要卡着每个等级刚刚好的数,避免被风控了导致人数不足那就亏了,一定要多发展几个,稳妥将钱拿到手🍔🍔🍔】 有问题请及时联系 @JNH707 😀😀😀

27 Jul 2026, 08:12 UTC12 viewsread 7 August 2026
Photo

重要提醒♾重要提醒♾重要提醒♾ 重要的事情说三遍!!! 📌活跃人数不足5人是拿不到佣金的,临近月底一定要及时查看, 看看自己线上 新增活跃不够的 ,抓紧时间上人了哦,抓紧时间冲刺新增,避免因人数不足拿不到佣金或者是更高的佣金比例。 【温馨提醒:不要卡着每个等级刚刚好的数,避免被风控了导致人数不足那就亏了,一定要多发展几个,稳妥将钱拿到手🍔🍔🍔】 有问题请及时联系 @JNH707 😀😀😀

20 Jul 2026, 18:14 UTC15 viewsread 7 August 2026

— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。

14 Jul 2026, 17:29 UTC17 viewsread 7 August 2026
Photo

世界杯火热进行中,买球,收单,做代理正是入手好时机,金年会数字站豪客首选平台,世界杯待遇如下: 😂活动1:长期55%佣金 五个有效新增即可享受 😂活动2:人头费最高239999人民币 🪙活动3:不计输赢流水佣金每月最高77777 😂活动4:会员高额首存日存彩金实时派发 🚀活动5:介绍朋友最高可享8%介绍佣金 🪙会员u存u取可绑定TG,世界杯恭候各大豪客前来娱乐 😂😂😂开线扶持拉满欢迎优质大代洽谈业务!一切待遇可谈😄😄😄 🫥🫥🫥 🪙🪙游戏链接: jnh707.cc 😀 洽谈合作 😀 😀 😀 😀 最靠谱招商-景天TG:@jnh707 😀 赛事推荐频道: @jnh03 #金年会 #代理 #pg电子 #麻将糊了 #美加墨世界杯

13 Jul 2026, 18:18 UTC21 viewsread 7 August 2026

— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。

6 Jul 2026, 18:15 UTC77 viewsread 7 August 2026

— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。

4 Jul 2026, 04:33 UTC101 viewsread 7 August 2026
Photo

世界杯火热进行中,买球,收单,做代理正是入手好时机,金年会数字站豪客首选平台,世界杯待遇如下: 😂活动1:长期55%佣金 五个有效新增即可享受 😂活动2:人头费最高239999人民币 🪙活动3:不计输赢流水佣金每月最高77777 😂活动4:会员高额首存日存彩金实时派发 🚀活动5:介绍朋友最高可享8%介绍佣金 🪙会员u存u取可绑定TG,世界杯恭候各大豪客前来娱乐 😂😂😂开线扶持拉满欢迎优质大代洽谈业务!一切待遇可谈😄😄😄 🫥🫥🫥 🪙🪙游戏链接: jnh707.cc 😀 洽谈合作 😀 😀 😀 😀 最靠谱招商-景天TG:@jnh707 😀 赛事推荐频道: @jnh03 #金年会 #代理 #pg电子 #麻将糊了 #美加墨世界杯

29 Jun 2026, 18:13 UTC129 views1 reactionsread 7 August 2026

— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。

1

29 Jun 2026, 02:46 UTC118 viewsread 7 August 2026
Photo

世界杯期间开户转化都是异常丝滑,金年会代理中心提供全网最高会员首存复存优惠, 🥰🥰两个有效新增会员即可领取佣金, 世界杯资源转化:个人收单,圈子分享,全网都在赌博,为什么不借此机会让自己成为庄家,成为受益人之一? 只要愿意做事,任何时间都不算晚,欢迎咨询开线,金年会单日取款无上限一千万照样秒出,欢迎大户前来爆庄 点击查阅详细代理活动 🫥🫥🫥 😀 洽谈合作 😀 😀 😀 😀 最靠谱招商-景天TG:@jnh707 😀 赛事红单推荐: @TIYU83 🪙🪙游戏链接: 数字站: jnh707.cc 国内站: 137036.cc #金年会 #代理 #pg电子 #麻将糊了 #美加墨世界杯

Showing the 12 most recent of 19 posts we hold for @xcty_gfzszx. 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

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

“金年会招商中心” (@xcty_gfzszx), 2,589 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/xcty_gfzszx.

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.