Telegram RegisterThe public register of Telegram
Telegram profile photo for 182体育 体育赛事 推单频道

Channel

182体育 体育赛事 推单频道

@td182TY

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry

4,002subscribers

+1,467 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003733165142
TypeChannel
Username@td182TY
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held33
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/td182TY

Topic

Sports — 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 15 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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 6 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
@TYtuijian8/566328 Aug 2026, 11:51 UTC@td182TY/650 · this entry28 Aug 2026, 11:51 UTC1.00under a minute
@TYtuijian8/567729 Aug 2026, 07:07 UTC@td182TY/654 · this entry29 Aug 2026, 07:07 UTC1.00under a minute
@TYtuijian8/567929 Aug 2026, 07:07 UTC@td182TY/656 · this entry29 Aug 2026, 07:07 UTC1.00under a minute
@TYtuijian8/568229 Aug 2026, 07:55 UTC@td182TY/659 · this entry29 Aug 2026, 07:55 UTC1.00under a minute
@TYtuijian8/569630 Aug 2026, 07:13 UTC@td182TY/661 · this entry30 Aug 2026, 07:13 UTC1.00under a minute
@TYtuijian8/570430 Aug 2026, 09:58 UTC@td182TY/668 · this entry30 Aug 2026, 09:58 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
@TYtuijian822 (8/8 hand-verifiable sample passed)1.00under a minute@TYtuijian8 (22–0)
@GF8KGJ18 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (18–0)
@tytd1613 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (13–0)

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. 22 of the 22 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 50 comparable posts for this entry, running 1 August 2026 to 2 September 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 6 channels, the one whose matching posts we hold earliest is @QSTY988. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, 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 6 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

36711,4295,8987 August 2026 — 2,535 subscribers7 August 2026 — 2,535 subscribers10 August 2026 — 2,526 subscribers13 August 2026 — 1,756 subscribers16 August 2026 — 1,551 subscribers19 August 2026 — 1,220 subscribers23 August 2026 — 367 subscribers29 August 2026 — 11,429 subscribers30 August 2026 — 11,386 subscribers31 August 2026 — 11,328 subscribers1 September 2026 — 11,187 subscribers2 September 2026 — 11,143 subscribers3 September 2026 — 11,103 subscribers5 September 2026 — 11,060 subscribers8 September 2026 — 10,870 subscribers11 September 2026 — 10,698 subscribers13 September 2026 — 10,629 subscribers14 September 2026 — 10,598 subscribers16 September 2026 — 10,521 subscribers18 September 2026 — 10,347 subscribers24 September 2026 — 10,026 subscribers3 October 2026 — 8,172 subscribers10 October 2026 — 7,656 subscribers14 October 2026 — 7,313 subscribers17 October 2026 — 6,785 subscribers20 October 2026 — 6,292 subscribers23 October 2026 — 6,175 subscribers25 October 2026 — 6,041 subscribers28 October 2026 — 5,982 subscribers31 October 2026 — 4,956 subscribers4 November 2026 — 4,242 subscribers7 November 2026 — 4,114 subscribers10 November 2026 — 4,002 subscribers4,0027 August 202610 November 2026
33 measurements spanning 96 days, net +1,467. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
10 Nov 2026, 20:284,002-112
7 Nov 2026, 04:284,114-128
4 Nov 2026, 00:114,242-714
31 Oct 2026, 19:114,956-1,026
28 Oct 2026, 17:355,982-59
25 Oct 2026, 21:286,041-134
23 Oct 2026, 02:276,175-117
20 Oct 2026, 09:396,292-493
17 Oct 2026, 06:046,785-528
14 Oct 2026, 06:087,313-343
10 Oct 2026, 03:177,656-516
3 Oct 2026, 14:378,172-1,854
24 Sept 2026, 20:1810,026-321
18 Sept 2026, 20:0010,347-174
16 Sept 2026, 10:2110,521-77
14 Sept 2026, 17:5810,598-31
13 Sept 2026, 04:5810,629-69
11 Sept 2026, 10:2110,698-172
8 Sept 2026, 19:1510,870-190
5 Sept 2026, 09:5611,060first reading

Engagement

69 posts held, back to 1 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 7 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 69 posts for this entry, the most recent from 2 September 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Sept 2026, 15:19 UTC≈2,420 viewsread 3 September 2026

巴西杯 —————————————-- 维多利亚 vs 瓦斯科达伽马 巴西杯 09/03 08:30 让球[欧洲盘] 维多利亚 [email protected] —————————————-- 桑托斯SP vs 帕尔梅拉斯 巴西杯 09/03 08:30 让球[欧洲盘] 桑托斯SP [email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

2 Sept 2026, 07:52 UTC≈2,650 viewsread 3 September 2026

德国足协杯 —————————————-- 奥斯纳布吕克 1899 vs 拜仁慕尼黑 德国足协杯 09/03 02:45 让球[欧洲盘] 拜仁慕尼黑 [email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

2 Sept 2026, 07:37 UTC≈3,430 viewsread 3 September 2026

意大利杯 —————————————-- 萨索洛 vs 弗罗西诺内 意大利杯 09/02 21:00 让球[欧洲盘] 萨索洛 [email protected] —————————————-- 乌迪内斯 vs 威尼斯 意大利杯 09/03 00:00 让球[欧洲盘] 威尼斯 [email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

2 Sept 2026, 07:36 UTC≈3,010 viewsread 3 September 2026

中国足协杯 —————————————-- 云南玉昆 vs 重庆铜梁龙 中国足协杯 09/02 20:00 让球[欧洲盘] 云南玉昆 -0.5/[email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

2 Sept 2026, 07:34 UTC≈11,500 viewsread 3 September 2026

日本甲级联赛 —————————————-- 水户蜀葵 vs 鹿岛鹿角 日本甲级联赛 09/02 18:00 让球[欧洲盘] 鹿岛鹿角 -0.5/[email protected] —————————————-- 千叶市原 vs 冈山绿雉 日本甲级联赛 09/02 18:00 让球[欧洲盘] 冈山绿雉 [email protected] —————————————-- 东京绿茵 vs 神户胜利船 日本甲级联赛 09/02 18:00 让球[欧洲盘] 东京绿茵 [email protected] —————————————-- 町田泽维亚 vs 川崎前锋 日本甲级联赛 09/02 18:00 让球[欧洲盘] 町田泽维亚 [email protected] —————————————-- 横滨水手 vs 京都不死鸟 日本甲级联赛 09/02 18:00 让球[欧洲盘] 横滨水手 [email protected] —————————————-- 清水心跳 vs 东京 日本甲级联赛 09/02 18:00 让球[欧洲盘…

1 Sept 2026, 13:35 UTC≈2,040 viewsread 3 September 2026

巴西杯 —————————————-- 米内罗竞技 vs 克鲁塞罗MG 巴西杯 09/02 08:00 让球[欧洲盘] 米内罗竞技 [email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

1 Sept 2026, 13:34 UTC≈2,600 viewsread 3 September 2026

意大利杯 —————————————-- 帕尔马 vs 克雷莫纳 意大利杯 09/02 00:00 让球[欧洲盘] 帕尔马 -0/[email protected] —————————————-- 都灵 vs 蒙扎 意大利杯 09/02 03:00 让球[欧洲盘] 都灵 -0.5/[email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

31 Aug 2026, 09:56 UTC≈2,790 viewsread 3 September 2026

西班牙甲级联赛 —————————————-- 奥萨苏纳 vs 赫塔菲 西班牙甲级联赛 09/01 01:30 让球[欧洲盘] 赫塔菲 +0/[email protected] —————————————-- 巴塞罗那 vs 巴列卡诺 西班牙甲级联赛 09/01 03:30 让球[欧洲盘] 巴塞罗那 -2.5/[email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

31 Aug 2026, 09:56 UTC≈2,630 viewsread 3 September 2026

意大利甲级联赛 —————————————-- 莱切 vs 罗马 意大利甲级联赛 09/01 00:30 大/小[欧洲盘] 大 [email protected] —————————————-- 亚特兰大 vs 博洛尼亚 意大利甲级联赛 09/01 02:45 让球[欧洲盘] 亚特兰大 [email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

31 Aug 2026, 09:55 UTC≈2,370 viewsread 3 September 2026

英格兰超级联赛 —————————————-- 阿斯顿维拉 vs 阿森纳 英格兰超级联赛 09/01 03:00 让球[欧洲盘] 阿森纳 [email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

30 Aug 2026, 09:58 UTC≈2,510 viewsread 3 September 2026

西班牙甲级联赛 —————————————-- 皇家马德里 vs 马拉加 西班牙甲级联赛 08/30 23:00 让球[欧洲盘] 皇家马德里 -2.5/[email protected] —————————————-- 拉科鲁尼亚 vs 瓦伦西亚 西班牙甲级联赛 08/31 01:30 让球[欧洲盘] 拉科鲁尼亚 [email protected] —————————————-- 维戈塞尔塔 vs 毕尔巴鄂竞技 西班牙甲级联赛 08/31 03:30 大/小[欧洲盘] 大 2/[email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

30 Aug 2026, 09:57 UTC≈2,070 viewsread 3 September 2026

法国甲级联赛 —————————————-- 巴黎FC vs 尼斯 法国甲级联赛 08/30 21:00 让球[欧洲盘] 巴黎FC [email protected] —————————————-- 雷恩 vs 勒芒 法国甲级联赛 08/30 23:15 让球[欧洲盘] 勒芒 +1/[email protected] —————————————-- 摩纳哥 vs 马赛 法国甲级联赛 08/31 02:45 让球[欧洲盘] 摩纳哥 -0/[email protected] —————————————-- 赛事无神、红黑莫怪、仅供参考

Showing the 12 most recent of 69 posts we hold for @td182TY. 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 62 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“182体育 体育赛事 推单频道” (@td182TY), 4,002 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/td182TY.

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.