Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
Views per post sit far below this size band
2.4 average views per post against 11,239 subscribers — an engagement rate of 0.021%. Across the 2,085 registered channels in the same cohort — 10,003–31,622 subscribers, posting mainly in Chinese — the middle half sit between 1.76% and 11.0%, with a median of 4.89%.
What this was computed from
Window
30 days (6 October 2026 – 5 November 2026)
Posts measured
28 of 28 published in the window (28 exact, 0 rounded by Telegram)
Views totalled
67
Mature posts only
0.022% over 23 posts read at least 24h after publication
When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_low, last confirmed 5 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.
Growth
29 measurements spanning 44 days, net +4,731. 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 5,169–13,573 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)
Subscribers
Change
9 Nov 2026, 21:37
10,870
-140
8 Nov 2026, 12:44
11,010
-88
7 Nov 2026, 08:49
11,098
-70
6 Nov 2026, 06:49
11,168
-71
5 Nov 2026, 07:16
11,239
-40
4 Nov 2026, 04:51
11,279
-90
3 Nov 2026, 01:44
11,369
-9
2 Nov 2026, 03:36
11,378
-80
1 Nov 2026, 04:58
11,458
-43
31 Oct 2026, 07:40
11,501
-112
30 Oct 2026, 04:28
11,613
-64
29 Oct 2026, 07:58
11,677
-92
28 Oct 2026, 09:27
11,769
-66
27 Oct 2026, 10:01
11,835
-46
26 Oct 2026, 12:57
11,881
-126
25 Oct 2026, 11:18
12,007
-53
24 Oct 2026, 10:15
12,060
-97
23 Oct 2026, 07:20
12,157
-56
22 Oct 2026, 06:30
12,213
-137
20 Oct 2026, 20:59
12,350
first reading
Engagement
76 posts held, back to 17 September 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 22 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.027%
avg views ÷ 10,870 subscribers
Avg views / post
3.0
56 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
56
of 76 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
Window
Rolling 30 days · latest post in window 10 November 2026
Posts held
76 (17 September 2026 – 10 November 2026)
Views total
167
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Nov 2026, 14:07 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
213
Videos
2
Links
130
Lifetime counters from Telegram’s own channel header, read 10 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
20s
Average length
5s
Measured directly from 4 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 56 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).
1⃣1⃣月9️⃣日 😍😀 于谦
❤❤❤❤❤❤❤❤
法甲🔢🔢昂热 vs 尼斯（尼斯-0/0.5 / 大2.5）
法甲🔢🔢布雷斯特 vs 里昂（里昂-0/0.5 / 大2.5/3）⭐️重点
法甲🔢🔢勒阿弗尔 vs 洛里昂（勒阿弗尔-0/0.5 / 小2.5/3）
法甲🔢🔢勒芒 vs 摩纳哥（摩纳哥-0.5/1 / 大2.5/3）⭐️重点
德甲🔢🔢弗赖堡 vs 柏林联合（弗赖堡-0.5 / 大2.5）
英超🔢🔢曼彻斯特联 vs 阿斯顿维拉（曼联-0/0.5 / 大2.5/3）⭐️重点
意甲🔢🔢国际米兰 vs 科莫（国际米兰-0.5/1 / 大2.5/3）⭐️重点
西甲🔢🔢塞尔塔 vs 莱万特（塞尔塔-0.5 / 大2.5）
西甲🔢🔢比利亚雷亚尔 vs 赫塔费（比利亚雷亚尔-0.5 / 大2.5）
德甲🔢🔢霍芬海姆 vs 沙尔克04（霍芬海姆-0.5/1 / 大2.5/3）
意甲🔢🔢佛罗伦萨 vs 尤文图斯（尤文图斯-0/0.5 / …
Showing the 12 most recent of 76 posts we hold for @shibotiy. 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 recorded as deleted after publishing
We recorded 10 posts on @shibotiy as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
3 November 2026
Most recent seen missing
10 November 2026
Median time before seen missing
33 hours
Seen missing in the last 30 days
10
Mentions
Named by 31 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 23 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@shibotiy named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@cszwso named in 4 posts, 8 November 2026 – 9 November 2026
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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“🥇世博国际🅥pg娱乐” (@shibotiy), 10,870 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/shibotiy.
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.
