Telegram RegisterThe public register of Telegram

Channel

银河体育推单

@yhtytd

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

762subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002151009020
TypeChannel
Username@yhtytd
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/yhtytd

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 96% 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. They sit inside a group of 5 channels that share the same post bodies 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
@cftiyu/584029 Jul 2026, 15:17 UTC@yhtytd/2035 · this entry29 Jul 2026, 15:24 UTC1.007 minutes
@cftiyu/586331 Jul 2026, 12:44 UTC@yhtytd/2037 · this entry31 Jul 2026, 12:50 UTC1.005 minutes
@yhtytd/2039 · this entry1 Aug 2026, 13:34 UTC@cftiyu/58801 Aug 2026, 13:35 UTC1.0072 seconds
@cftiyu/58841 Aug 2026, 15:31 UTC@yhtytd/2040 · this entry1 Aug 2026, 15:31 UTC1.00under a minute
@cftiyu/58992 Aug 2026, 14:03 UTC@yhtytd/2043 · this entry2 Aug 2026, 14:03 UTC1.00under a minute
@yhtytd/2044 · this entry4 Aug 2026, 12:31 UTC@cftiyu/59234 Aug 2026, 12:31 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@cftiyu11 (8/8 hand-verifiable sample passed)1.00under a minute@cftiyu (83)

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. 2 of the 8 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 19 comparable posts for this entry, running 21 July 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 5, the earliest publisher we hold is @cftiyu. 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 4 other registered channels, 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

7627647637 Aug 2026, 05:32 — 764 subscribers7 Aug 2026, 22:03 — 762 subscribers7 Aug 2026, 05:327 Aug 2026, 22:03
2 measurements taken within a single day, net -2. 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 762–764 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 22:03762-2
7 Aug 2026, 05:32764first reading

Engagement

20 posts held, back to 21 July 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
9.63%
avg views ÷ 762 subscribers
Avg views / post
73.3
20 posts measured
Reaction rate
1.54%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 1 of 20 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 6 August 2026
Posts held20 (21 July 20266 August 2026)
Views total1,467
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 05:32 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 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 1reactions 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 21 July 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, 15:46 UTC23 viewsread 7 August 2026

--同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 欧罗巴 01:00 队伍:萨尔茨堡红牛-帕福斯 推荐:全场小(3) 欧协联 01:00 队伍:德布勒森-哥本哈根 推荐:哥本哈根进球大(1.5/2) 欧协联 02:00 队伍:阿贾克斯-舒尔本 ♥️ 推荐:阿贾克斯(-3) 欧协联 02:00 队伍:特温特-斯特里达 推荐:特温特(-2 ) 欧协联 02:45 队伍:布咸美恩斯-米迪兰特 推荐:米迪兰特(-1/1.5) 欧罗巴 03:00 队伍:本菲卡-赫斯 推荐:全场大(3.5/4) 三串一:阿贾克斯+特温特+本菲卡

6 Aug 2026, 08:25 UTC35 viewsread 7 August 2026

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- WNBA 【07:00】 队伍:狂热 vs 王牌 推荐:全场小196.5 WNBA 【09:00】 队伍:山猫 vs 火花 推荐:火花+15.5 WNBA 【10:00】 队伍:火焰 vs 节奏 ❤️ 推荐:全场大186.5

4 Aug 2026, 12:31 UTC65 views1 reactionsread 7 August 2026

东南锦21:00 菲律宾VS泰国 推荐:全场大3球 欧冠杯00:00 米亚尔比VS布拉迪斯拉发 推荐:全场小2.5球 欧冠杯02:00 萨格勒布VS考诺萨 荐:全场大3球 欧冠杯02:00 圣吉罗斯VS博德闪耀 推荐:全场大3球 玻利甲03:00 学术VS奥鲁罗 推荐:全场大3.5球 欧罗巴杯03:00 拉恩VS提比利锡1999 推荐:全场小2.25球 玻利甲06:00 佩特莱罗独立VS欧若拉 推荐:全场大3球 中北美杯08:00 夏洛特VS普马斯 推荐:全场大2.25球

1

2 Aug 2026, 14:03 UTC91 viewsread 7 August 2026

2026-08-02 22:30 瑞士超级联赛 草蜢 v 卢加诺 足球 让球 卢加诺 -0.5 --------------------------- 2026-08-02 22:30 瑞士超级联赛 锡永 v 卢塞恩 足球 让球 卢塞恩 +0.5 / 1 --------------------------- 2026-08-03 00:00 丹麦超级联赛 锡尔克堡 v 哥本哈根 足球 让球 哥本哈根 -1 --------------------------- 2026-08-03 00:00 荷兰超级杯 PSV埃因霍温 v 阿尔克马尔 足球 角球数 - 大 / 小 大 9.5 --------------------------- 2026-08-03 01:15 挪威超级联赛 白兰恩 v 洛辛堡 足球 让球 洛辛堡 +0.5 ---------------------------

2 Aug 2026, 11:25 UTC72 viewsread 7 August 2026

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 芬兰超级联赛 20:00 队伍:VPS瓦萨-图尔库国际 推荐:全场角球大(9.5) 中超 19:30 队伍:辽宁铁人-上海申花 推荐:辽宁铁人(+1/1.5) 中超 20:00 队伍:深圳新鹏城-重庆铜梁龙 推荐:总进球(2/3球) 早场三串一 可单可串!

2 Aug 2026, 10:27 UTC62 viewsread 7 August 2026

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- WNBA 【01:00】 队伍:山猫 vs 狂热 ❤️ 推荐:全场大194.5 WNBA 【03:30】 队伍:火焰 vs 火花 推荐:火花+2.5 WNBA 【07:00】 队伍:飞翼 vs 太阳 推荐:飞翼 -11.5 WNBA 【08:30】 队伍:女武神 vs 节奏 推荐:节奏+14.5

1 Aug 2026, 15:31 UTC69 viewsread 7 August 2026

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 挪超 00:00 队伍:斯达-维京 ♥️ 推荐:全场小(3/3.5) 丹麦 00:00 队伍:宁比-奥胡斯 推荐:全场大(2.5/3) 芬超 00:00 队伍:格尼斯坦-古比斯 推荐:格尼斯坦(+0.5) 奥地利 01:30 队伍:萨尔茨堡红牛-哈特贝格 推荐:双进(是) 友谊赛 00:00 队伍:赫罗纳-阿森纳 推荐:全场大(2.5/3) 葡超杯 07:30 队伍:波尔图-图伦斯 推荐:图伦斯(+2)

1 Aug 2026, 13:34 UTC59 viewsread 7 August 2026

瑞典甲 23:00 北雪平 VS 赫尔辛堡 推荐:全场大3球 球会友谊 02:00 赫罗纳 VS 阿森纳 推荐:全场小 2.75 球 厄瓜甲03:00 曼塔VS穆苏鲁纳 推荐:全场小2.25球 阿甲05:00 贝尔格拉诺VS小阿根廷人 推荐:全场小1.75球 美职业07:30 纽约红牛VS奥兰多城 推荐:全场大3.75球

1 Aug 2026, 07:08 UTC55 viewsread 7 August 2026

2026-08-01 19:00 中国超级联赛 天津津门虎 v 云南玉昆 足球 让球 云南玉昆 +0 / 0.5 2026-08-01 19:35 中国超级联赛 北京国安 v 浙江 足球 角球数 - 大 / 小 大 10 2026-08-01 19:35 中国超级联赛 上海海港 v 山东泰山 足球 让球 上海海港 -0.5 2026-08-01 20:00 中国超级联赛 成都蓉城 v 武汉三镇 足球 让球 武汉三镇 +1.5

31 Jul 2026, 12:50 UTC63 viewsread 7 August 2026

2026-07-31 23:00 球会友谊赛 摩纳哥 v 色格拉布鲁日 足球 让球 摩纳哥 -1 ------------------------ 2026-08-01 01:00 捷克甲组联赛 布拉格斯巴达 v 辛宁 足球 让球 布拉格斯巴达 -1.5 / 2 ------------------------ 2026-08-01 01:30 波兰甲组联赛 LKS罗兹 v 比托姆 足球 让球 LKS罗兹 -0.5 / 1 ------------------------ 2026-08-01 02:30 波兰超级联赛 莫托路宾 v 乔治罗尼亚 足球 让球 莫托路宾 +0 / 0.5 ------------------------ 2026-08-01 03:00 苏格兰超级联赛 邓迪联 v 格拉斯哥流浪 足球 大 / 小 大 3 ------------------------

30 Jul 2026, 15:11 UTC67 viewsread 7 August 2026

Piang✨篮球赛事推荐7/30 WNBA【08:00】 队伍:天空VS太阳 推荐:小176.5 WNBA【08:00】 队伍:节奏VS山猫 推荐:节奏+11.5 重❤️ WNBA【10:00】 队伍:王牌VS自由人 推荐:大182.5

29 Jul 2026, 15:24 UTC81 viewsread 7 August 2026

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 欧冠 00:00 队伍:考诺萨基列斯-克拉克斯维克 推荐:全场小(2/2.5) 欧冠 01:00 队伍:波兹南莱赫-奥胡斯 推荐:波兹南莱赫(-0.5/1) 欧冠 01:30 队伍:克拉约瓦大学-索菲亚列夫斯基 推荐:索菲亚列夫斯基(+0.5) 欧冠 01:30 队伍:贝尔谢巴工人-维京古 推荐:贝尔谢巴工人(-0.5/1) 欧冠 02:00 队伍:扎布热矿工-费内巴切 推荐:费内巴切(-1) 欧冠 02:00 队伍:贝尔格莱德红星-拉恩 推荐:拉恩(+3) 欧冠 02:00 队伍:布拉迪斯拉发-伊比利亚1999 推荐:总进球 (2/3球)

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

Citation-graph rank

Citation-graph rank — 228,892 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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

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

“银河体育推单” (@yhtytd), 762 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/yhtytd.

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.