Telegram RegisterThe public register of Telegram
Telegram profile photo for 体育丨电竞丨赛事推单丨 78.com独家冠名 (接广告合作)

Channel

体育丨电竞丨赛事推单丨 78.com独家冠名 (接广告合作)

@jnty135

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

16,696subscribers

+8,785 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001873833089
TypeChannel
Username@jnty135
Description本群内容:🏆体育推单🏆 广告投放 请联系: @zy9845 吃瓜搞笑:https://t.me/zg5518 华人第一资讯:https://t.me/Dzx199 78.com 独家冠名
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 November 2026
Measurements held41
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/jnty135

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 95% 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 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@jnty135/21332 · this entry6 Aug 2026, 15:42 UTC@ybgf9/140786 Aug 2026, 15:49 UTC1.007 minutes
@ybgf9/140807 Aug 2026, 08:30 UTC@jnty135/21339 · this entry7 Aug 2026, 08:34 UTC1.004 minutes
@ybgf9/140827 Aug 2026, 10:21 UTC@jnty135/21344 · this entry7 Aug 2026, 10:45 UTC1.0024 minutes
@jnty135/21354 · this entry7 Aug 2026, 15:46 UTC@ybgf9/140847 Aug 2026, 16:27 UTC1.0041 minutes
@jnty135/21357 · this entry7 Aug 2026, 15:50 UTC@ybgf9/140857 Aug 2026, 16:27 UTC1.0037 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ybgf95 (5/5 hand-verifiable sample passed)1.0016 minutesthis entry (3–2)

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 2 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 12 comparable posts for this entry, running 6 August 2026 to 7 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_mutual, 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

5,84216,82611,3347 August 2026 — 7,911 subscribers7 August 2026 — 7,911 subscribers8 August 2026 — 7,908 subscribers11 August 2026 — 7,742 subscribers14 August 2026 — 7,421 subscribers17 August 2026 — 7,106 subscribers20 August 2026 — 6,972 subscribers24 August 2026 — 6,848 subscribers27 August 2026 — 6,688 subscribers30 August 2026 — 6,539 subscribers1 September 2026 — 6,421 subscribers5 September 2026 — 6,363 subscribers10 September 2026 — 6,278 subscribers14 September 2026 — 6,130 subscribers18 September 2026 — 6,001 subscribers27 September 2026 — 5,939 subscribers5 October 2026 — 5,842 subscribers12 October 2026 — 16,826 subscribers14 October 2026 — 16,815 subscribers15 October 2026 — 16,795 subscribers16 October 2026 — 16,780 subscribers17 October 2026 — 16,770 subscribers18 October 2026 — 16,769 subscribers19 October 2026 — 16,765 subscribers20 October 2026 — 16,764 subscribers21 October 2026 — 16,759 subscribers22 October 2026 — 16,752 subscribers23 October 2026 — 16,743 subscribers24 October 2026 — 16,742 subscribers25 October 2026 — 16,735 subscribers26 October 2026 — 16,732 subscribers27 October 2026 — 16,730 subscribers28 October 2026 — 16,728 subscribers29 October 2026 — 16,724 subscribers30 October 2026 — 16,719 subscribers31 October 2026 — 16,716 subscribers1 November 2026 — 16,713 subscribers2 November 2026 — 16,711 subscribers3 November 2026 — 16,709 subscribers4 November 2026 — 16,703 subscribers5 November 2026 — 16,696 subscribers16,6967 August 20265 November 2026
41 measurements spanning 90 days, net +8,785. 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 4,194–18,474 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 41
Measured (UTC)SubscribersChange
5 Nov 2026, 12:0116,696-7
4 Nov 2026, 09:1916,703-6
3 Nov 2026, 08:2116,709-2
2 Nov 2026, 08:0816,711-2
1 Nov 2026, 06:3916,713-3
31 Oct 2026, 08:2816,716-3
30 Oct 2026, 09:1516,719-5
29 Oct 2026, 08:0816,724-4
28 Oct 2026, 04:0116,728-2
27 Oct 2026, 06:5916,730-2
26 Oct 2026, 08:5916,732-3
25 Oct 2026, 05:4916,735-7
24 Oct 2026, 07:0116,742-1
23 Oct 2026, 08:0616,743-9
22 Oct 2026, 09:4616,752-7
21 Oct 2026, 02:2716,759-5
20 Oct 2026, 00:5616,764-1
19 Oct 2026, 04:0016,765-4
18 Oct 2026, 07:3016,769-1
17 Oct 2026, 07:2916,770first reading

Engagement

194 posts held, back to 6 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 19 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
12.8%
avg views ÷ 16,696 subscribers
Avg views / post
2,140
55 posts measured
Reaction rate
0.047%
reactions ÷ views · ER floor
Posts in window
55
of 194 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 55 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 5 November 2026
Posts held194 (6 August 2026 – 5 November 2026)
Views total117,435
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 04:30 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

Photos
≈6,180
Videos
≈1,090
Links
≈2,470

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

Video runtime
4m 09s
Average length
19s

Measured directly from 13 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

9 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 55.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤555.6%
💩222.2%
👍111.1%
👎111.1%

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

Measured over the 194 most recent posts we hold, published 6 August 2026 to 5 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: 0 of 55 posts held from the last 30 days (0%) 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).

5 Nov 2026, 14:03 UTC≈1,500 viewsread 6 November 2026

2026-11-06 01:45 欧洲协会联赛 特拉布宗 v 弗赖堡 足球 让球 弗赖堡 0 2026-11-06 04:00 欧洲联赛 格拉茨风暴 v 采列 足球 让球 格拉茨风暴 -1 2026-11-06 04:00 欧洲联赛 勒沃库森 v 马赛 足球 让球 马赛 +1.5 / 2 2026-11-06 04:00 欧洲联赛 维戈塞尔塔 v 圣吉罗斯 足球 让球 圣吉罗斯 +0 / 0.5 2026-11-06 04:00 欧洲协会联赛 赫塔费 v 布莱顿 足球 让球 布莱顿 -1 2026-11-06 04:00 欧洲协会联赛 摩纳哥 v 洛斯查兰特 足球 让球 - 上半场 摩纳哥 -0.5 6*1 6*5

5 Nov 2026, 12:38 UTC996 viewsread 6 November 2026

亚足联冠军二级联赛 狮城水手 v 阿德莱德联 足球 (滚球) 大 / 小 (3 - 0) 大 4.5 / 5

5 Nov 2026, 10:12 UTC≈1,880 viewsread 6 November 2026

亚足联冠军二级联赛 町田泽维亚 v 上海申花 足球 (滚球) 双方球队进球 是

5 Nov 2026, 09:24 UTC≈2,160 viewsread 6 November 2026

足球 (滚球) 大 / 小 (0 - 1) 澳大利亚锦标赛 悉尼奥林匹克 v 欧克莱卡诺 大 2.5 / 3

5 Nov 2026, 09:06 UTC≈2,150 views1 reactionsread 6 November 2026

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 亚冠 18:00 队伍:盯田泽维亚-上海申花 推荐:盯田泽维亚 (-1.5) 亚冠 18:00 队伍:志杰-金边皇冠 推荐: 金边皇冠(+0/0.5) 亚冠 18:00 队伍:狮城水手-阿德莱德联 推荐: 全场大(3/3.5) 亚冠 18:00 队伍:柴桢-淡滨尼流浪者 推荐: 柴桢(-1) 亚冠 18:00 队伍:古晋城-江源FC 推荐: 古晋城(+0.5/1) 亚冠 18:00 队伍:巴吞联-大浦 推荐:巴吞联(-2) 六串一 平推捡钱 串子回国!😡😡😡

👍1

5 Nov 2026, 07:13 UTC≈3,310 viewsread 6 November 2026
Forwarded from @zg5518Photo

😄😄😄😄😄😄 🫥🫥🫥🫥🫥🫥🫥🫥 🟢🟢🟢🟢🟢🟢🟢🟢🟢 😄 U01.COM|全球华人娱乐优选 😄 PG电子|热门游戏一站体验 😄 麻将胡了2|连消叠加倍率 😄 虎虎生财|特色重转玩法 😄 赏金大对决|免费旋转与倍率 ✨ 信誉立足 · 规则透明 · 用心服务 👉 点击直达热门PG电子专区! 🎁 关注U01官方频道领取18USDT 🟢🟢🟢🟢🟢🟢🟢🟢 🫥🫥🫥🫥🫥🫥🫥🫥🫥🫥🫥🫥 🟢🟢🟢🟢🟢🟢🟢🟢🟢 🫥🫥🫥🫥 @U01KF 🫥🫥🫥🫥 @U01COM 🫥🫥🫥🫥 @U01ZS 🫥🫥🫥🫥 U01.com 🫥🫥🫥🫥 @U01COMBOT

5 Nov 2026, 07:13 UTC≈3,080 viewsread 6 November 2026
Forwarded from @zg5518Video

🤩🤩🤩🤩 🤩🤩🤩🤩🤩 0审核|包出款🤩🤩🤩 东南亚大事件联合担保🤩🤩🤩🤩🤩(电子) 🤩亿级域名|78.COM 🤩官方飞投|充提自由 🔝实力派: 78.COM 数字够短 品牌够大 🔥香港六合彩 · 独家盈利无上限! 🤩所有的特码🤩🤩倍 🤩连码三中三🤩🤩🤩倍 🤩百家乐全网最高起步返水🤩% 🤩电子|棋牌|捕鱼起步返水🤩.🤩% 🤩十三水|德州自主组队,无抽佣; 🏆电子单注🤩🤩🤩🤩U一拉; ⭐️百家乐真人视讯台红🤩🤩万U; 🚩诚招代理合作 1.打码返佣,限指定平台; 2.可叠加占成,自选占成比例及游戏平台; 🤩🤩🤩🤩:@DL78 💥高额战绩,巅峰记录持续刷新: 🥇PP电子|极速糖果1000 玩家游戏中购买30000u超级免费旋转,高倍爆奖,最终拿下378万U,已出款 ; 🥈PG电子|麻将胡了 又又又欧气爆棚,5000U一拉,连番触发,单局斩获233万U ; 🥉香港六合彩|特码49倍 爱拼才会赢,大佬单码下注18万U , 一注直接…

5 Nov 2026, 07:12 UTC≈2,620 viewsread 6 November 2026

亚冠联2 :18.00 狮城水手-阿德莱德 狮城水手-1 亚冠联2 :18.00 町田-申花 町田-1.5 亚冠联2 :20.15 古晋-江原 江原-0.5/1 亚冠联2 :20.15 巴吞联-和富大浦 大3 4*1

5 Nov 2026, 03:46 UTC≈3,240 viewsread 6 November 2026

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 欧冠 01:45 队伍:费内巴切-利物浦 推荐:费内巴切 (+1/1.5) ✅✅✅ 欧冠 01:45 队伍:AEK雅典-皇家马德里 ✅✅✅ 推荐:AEK雅典 (+2) 欧冠 04:00 队伍:多特蒙德-皇家贝蒂斯 ✅✅✅ 推荐:多特蒙德(-0.5/1) 欧冠 04:00 队伍:莱比锡红牛-曼城 ✅✅✅ 推荐:全场大(3.5/4) 欧冠 04:00 队伍:布拉格斯拉维亚-阿森纳 推荐:阿森纳半场(-0.5/1) ✅✅✅ 欧冠 04:00 队伍:朗斯-科莫 ✅✅✅ 推荐:科莫(-0.5) 欧冠 04:00 队伍:波尔图-那不勒斯 推荐:总进球(2/3球) 欧冠 04:00 队伍:PSV埃因霍温-布鲁日 推荐:全场大(3.5) 欧冠 04:00 …

4 Nov 2026, 15:50 UTC≈2,930 viewsread 6 November 2026

欧洲联赛 雷恩 v 奥林匹亚科斯 足球 (滚球) 让球 (0 - 0) 奥林匹亚科斯 +0 / 0.5

4 Nov 2026, 13:36 UTC≈2,150 viewsread 6 November 2026

---同路上车 跟反自由--- ---赛事无神 红黑勿怪--- 欧冠 01:45 队伍:费内巴切-利物浦 推荐:费内巴切 (+1/1.5) 欧冠 01:45 队伍:AEK雅典-皇家马德里 推荐:AEK雅典 (+2) 欧冠 04:00 队伍:多特蒙德-皇家贝蒂斯 推荐:多特蒙德(-0.5/1) 欧冠 04:00 队伍:莱比锡红牛-曼城 推荐:全场大(3.5/4) 欧冠 04:00 队伍:布拉格斯拉维亚-阿森纳 推荐:阿森纳半场(-0.5/1) 欧冠 04:00 队伍:朗斯-科莫 推荐:科莫(-0.5) 欧冠 04:00 队伍:波尔图-那不勒斯 推荐:总进球(2/3球) 欧冠 04:00 队伍:PSV埃因霍温-布鲁日 推荐:全场大(3.5) 欧冠 04:00 队伍:维京-沙巴巴库 推荐:维京(-1.5) 九串一 平推捡钱 串子回国!😡😡😡

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

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“体育丨电竞丨赛事推单丨 78.com独家冠名 (接广告合作)” (@jnty135), 16,696 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/jnty135.

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.