芬乙比赛上的协议球+0.5赢球😓

Channel
绿茵足球协议球蛇货🥇
@nbm6790
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,023subscribers
-257 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002595249822 |
|---|---|
| Type | Channel |
| Username | @nbm6790 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/nbm6790 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:47 | 6,023 | -105 |
| 9 Aug 2026, 18:21 | 6,128 | -147 |
| 6 Aug 2026, 23:12 | 6,275 | -5 |
| 6 Aug 2026, 19:51 | 6,280 | first reading |
Engagement
36 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 9 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.79%
- avg views ÷ 6,023 subscribers
- Avg views / post
- 108
- 36 posts measured
- Reaction rate
- 1.18%
- reactions ÷ views · ER floor
- Posts in window
- 36
- of 36 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 9 of 36 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 36 (1 August 2026 – 11 August 2026) |
| Views total | 3,876 |
| Reactions total | 12 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03: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.
Reaction mix
12 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 16.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤷 | 2 | 16.7% | |
| ❤🔥 | 1 | 8.33% | |
| 🏆 | 1 | 8.33% | |
| 👏 | 1 | 8.33% | |
| 💊 | 1 | 8.33% | |
| 🔥 | 1 | 8.33% | |
| 😢 | 1 | 8.33% | |
| 😱 | 1 | 8.33% | |
| 🤯 | 1 | 8.33% | |
| 🤷♂ | 1 | 8.33% | |
| 🥰 | 1 | 8.33% |
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 36 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 12reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 1 August 2026 to 11 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
芬乙▶️足球比赛上的协议球,TPV谭柏利 v 莎埃帕,需要的私聊提早准备上🤗
这黄了❌❌,下场补单或退押的私信
— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。
今晚✨瑞典超足球上大蛇货,天狼星 v 布洛马波卡纳,🫣最好提早私聊准备好再上
昨晚协议球,土甲小球收💯
晚场👑土甲足球打的协议球,凡斯珀尔 v 开塞利体育,有兴趣提前私信准备上😓
🤔下场赛事带货准备中,分成 协议 蛇货 要合作点击 双向联系:@xindai0013_bot 合作联系:@huq257 #协议球 #假球 #足球
晚上中超山东泰山 -0.5胜利收货🤭
晚上⚡️中超足球打的大蛇货,山东泰山 v 天津津门虎,在线的可以私信上🤫
昨晚上土甲足球上协议球让球顺利收货🥇
晚上🔴土甲足球上的协议球,安塔利亚 v 凯瑟兰高古,在线的可以提早私聊准备上☹️
Showing the 12 most recent of 36 posts we hold for @nbm6790. 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 — 300,076 of 1,169,250entries 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 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“绿茵足球协议球蛇货🥇” (@nbm6790), 6,023 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/nbm6790.
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.