😀 月满中秋,情暖相伴 😀 祝大家: 🥮 中秋快乐,阖家团圆 🌕 月圆人圆,事事圆满 ✨ 工作顺利,生活美满 ❤️ 平安喜乐,幸福常伴! 感谢一路同行,愿我们继续携手共进,共赴美好! 各位老板中秋节快乐!
❤17🔥11👍10
Signed Channel Help

Channel
@FAHAN10
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
30,420subscribers
+14,362 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001530520515 |
|---|---|
| Type | Channel |
| Username | @FAHAN10 |
| Description | 🅾️【官方认证】🅾️🅥官方商务频道🅥 ✅SKG包网-B端-API接口 ✅线下团队-seo团队✅天下支付-财务整包-渠道合作 🖥招商部 VIP服务专线⬇️⬇️⬇️ 🖥招商飞机➕: @crc888 🖥招商飞机➕: @x66666e #开云 #华体会 #爱游戏 #乐鱼 #星空 #OD #九游 #米兰 #MK #开云体育 #体育 #IM体育 #FB体育 #欧冠 #英超 #意甲 #德甲 #法甲 #中超 #足球 #篮球 #VR体育 #电竞 #网球 #世界杯 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/FAHAN10 |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 15:18 | 30,420 | +113 |
| 17 Sept 2026, 08:00 | 30,307 | -44 |
| 15 Sept 2026, 05:18 | 30,351 | -33 |
| 13 Sept 2026, 11:41 | 30,384 | -75 |
| 11 Sept 2026, 19:17 | 30,459 | -154 |
| 9 Sept 2026, 09:41 | 30,613 | -364 |
| 5 Sept 2026, 23:58 | 30,977 | -180 |
| 3 Sept 2026, 22:19 | 31,157 | -22 |
| 2 Sept 2026, 11:22 | 31,179 | -28 |
| 1 Sept 2026, 13:33 | 31,207 | -58 |
| 31 Aug 2026, 14:11 | 31,265 | -50 |
| 30 Aug 2026, 16:39 | 31,315 | -68 |
| 29 Aug 2026, 17:23 | 31,383 | -40 |
| 28 Aug 2026, 16:24 | 31,423 | -19 |
| 27 Aug 2026, 18:14 | 31,442 | +19,982 |
| 26 Aug 2026, 20:14 | 11,460 | -51 |
| 25 Aug 2026, 22:33 | 11,511 | -172 |
| 24 Aug 2026, 19:25 | 11,683 | -152 |
| 23 Aug 2026, 06:44 | 11,835 | -176 |
| 21 Aug 2026, 16:27 | 12,011 | first reading |
21 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 78 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 24 September 2026 |
|---|---|
| Posts held | 21 (1 August 2026 – 24 September 2026) |
| Views total | 5,582 |
| Reactions total | 556 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Sept 2026, 06:53 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.
Lifetime counters from Telegram’s own channel header, read 30 September 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.
Measured directly from 2 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.
1,354 reactions across 21 posts, in 7 distinct kinds. The most used accounts for 28.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 384 | 28.4% | |
| 👍 | 321 | 23.7% | |
| 🔥 | 299 | 22.1% | |
| 🤩 | 109 | 8.05% | |
| 🥰 | 102 | 7.53% | |
| 😍 | 76 | 5.61% | |
| 💯 | 63 | 4.65% |
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 21 of the 21 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 1,354 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 1 August 2026 to 24 September 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @FAHAN10. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 21 most recent posts we hold for this entry, published 1 August 2026 to 24 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
😀 月满中秋,情暖相伴 😀 祝大家: 🥮 中秋快乐,阖家团圆 🌕 月圆人圆,事事圆满 ✨ 工作顺利,生活美满 ❤️ 平安喜乐,幸福常伴! 感谢一路同行,愿我们继续携手共进,共赴美好! 各位老板中秋节快乐!
❤17🔥11👍10
Signed Channel Help
🇵🇳🇵🇭🇷🇼🇵🇭代理新增冲刺激励 😔活动时间:2026年9月24日——2026年10月7日 1、活动时间内,根据代理所做的有效新增数量满足要求给予😀😀😀——😀😀😀😀元激励; 2、后台转盘抽奖活动,活动期间内根据代理每天的新增和有效活跃、总输赢给予抽奖机会,给予:8️⃣♥1️⃣8️⃣8️⃣8️⃣元红包激励。
❤18👍14🔥10
Signed Channel Help
🏮 欢迎加入远程招商🏮 😍线上兼职 推荐代理 提成拿到手软 不压护照不提供真实信息|有代理资源转化即可拿提成 匿名兼职.达标即可拿底薪(阶梯式)
🔥23👍21❤17😍6💯4
Signed Channel Help
☺️ #开云 #早安祝福 #每日问候 2026年09月16日 星期三 开云官方招商特姆 佣金准时|出款稳定|大额无忧 最顶级的平台 | 最好的福利 最快的出入款 | 最靠谱的招商
🔥19❤15👍15
Signed Channel Help
☺️ 大平台有保障|不黑款不卡|玩家代理都放心 开云|乐鱼|爱游戏|OD| 星空|米兰|华体会|九游| ♥支持各种出入款:👛💰🎛💰💵💰💰💰 注册代理账号 品牌展示说明 谷歌验证器 😵官方招商负责人朵莉亚: @x66666e 😵官方招商负责人特姆:@crc888 😵双向小助手咨询:@x66666e_bot 😵官方招商推单频道:@ybgf9 😵ZS集团最新招聘岗位咨询 : @crc888 #电子 #爆奖 #彩金 #博彩 #棋牌 #赚钱 #项目 #兼职 #开云 #乐鱼 #爱游戏 #华体会 #综合盘 #世界杯 #百万收入 #加盟代理
❤18🔥17👍7
Signed 开云官方负责人 -朵莉亚
😃月代理佣金已陆续发放,请各位老板注意查收 目前佣金审核结果刚出来,本月派发佣金时间会在15号之前派发完毕的哦 需要在代理后台验证佣金 验证步骤 1. 登陆代理后台 点击 佣金报表 2. 佣金报表里 点击右上方 发佣验证 3. 按照页面提示输入信息 4. 显示 已验证 注册代理账号 品牌展示说明 谷歌验证器 ❤️❤️❤️❤️❤️❤️❤️❤️ 😵官方招商负责人特姆:@crc888 😵官方招商负责人朵莉亚: @x66666e 😵双向小助手咨询:@x66666e_bot 😵官方招商推单频道:@ybgf9 😵ZS集团最新招聘岗位咨询 : @crc888
👍17❤15🔥13
Signed 开云官方负责人 -朵莉亚
😍😍😍😍😍😍😍😍😍😍😍😍😍😍 免费加盟😃😃😀代理|认准官网特姆 💥会员输10万你拿5.5万 💥会员输100万你拿55万 💥新增冲刺奖励+月日均活越奖励+新增投注豪礼奖励 ⚽️👩🦱 🤩🤩🤩 🤩🤩🤩 🤩🤩🤩🤩 🤩🤩⚽ 📍全网最低成本,服务最全 📍行头龙头信誉保障,稳定可靠 📍全程保驾护航,创造你的博彩宏图大业 #开云 #华体会 #爱游戏 #乐鱼 #星空 #OD #九游 #米兰 #MK #开云体育 #体育 #IM体育 #FB体育 #欧冠 #英超 #意甲 #德甲 #法甲 #中超 #足球 #篮球 #VR体育 #电竞 #网球 #世界杯
❤19👍14🔥13
Signed Channel Help
😀代理后台场馆手续费 ♥免费加盟55%代理返佣 客损10万,你拿5.5万 客损50万,你拿25万 客损100万,你拿55万 佣金准时|出款稳定|大额无忧 最顶级的平台 | 最好的福利 最快的出入款 | 最靠谱的招商 😵官方招商负责人特姆:@crc888 😵双向小助手咨询:@x66666e_bot 😵官方招商推单频道:@ybgf9 😵ZS集团最新招聘岗位咨询 : @crc888
❤18🔥16👍13
Signed 开云官方负责人 -朵莉亚
✅✅✅✅✅⚡⚡⚡ 九台存取手续费费率 佣金准时|出款稳定|大额无忧 最顶级的平台 | 最好的福利 最快的出入款 | 最靠谱的招商 ♥支持各种出入款:👛💰🎛💰💵💰💰💰 注册代理账号 品牌展示说明 谷歌验证器 #电子 #爆奖 #彩金 #博彩 #棋牌 #赚钱 #项目 #兼职 #开云 #乐鱼 #爱游戏 #华体会 #综合盘 #世界杯 #百万收入 #加盟代理
👍16❤14🔥12
Signed 开云官方负责人 -朵莉亚
1️⃣1️⃣1️⃣1️⃣🔤🔤 九游【😀月代理活动】 🥰1. 代理佣金直达12月55% 🥰2. 新增冲刺人头最高可获得30万 🥰3.9月月均日活最高奖励38888元 🥰4. 新增投注豪礼最高奖励100万元 🥰5. 优质代理长期😀😀佣金比例特权 🥰6.9月指定联赛冠军盘投注返利最高188888 🥰7. 首存彩金+复存彩金+首100送100元体验金 佣金准时|出款稳定|大额无忧 😵官方招商负责人特姆:@crc888 😵双向小助手咨询:@x66666e_bot 😵官方招商推单频道:@ybgf9 😵ZS集团最新招聘岗位咨询 : @crc888
❤19👍15🔥13
Signed 开云官方负责人 -朵莉亚
1️⃣1️⃣1️⃣1️⃣🔤🔤米兰【😀月代理活动】 🦀【代理活动:55%佣金】🦀 🥰1. 代理佣金直达12月55% 🥰2. 新增冲刺人头最高可获得30万 🥰3.9月月均日活最高奖励38888元 🥰4. 新增投注豪礼最高奖励100万元 🥰5. 优质代理长期😀😀佣金比例特权 🥰6.9月指定联赛冠军盘投注返利最高188888 🥰7. 首存彩金+复存彩金+首100送100元体验金 佣金准时|出款稳定|大额无忧 😵官方招商负责人特姆:@crc888 😵双向小助手咨询:@x66666e_bot 😵官方招商推单频道:@ybgf9 😵ZS集团最新招聘岗位咨询 : @crc888
👍17❤14🔥13
Signed 开云官方负责人 -朵莉亚
1️⃣1️⃣1️⃣1️⃣🔤🔤 【😀月代理活动】 🦀【代理活动:55%佣金】🦀 🥰1. 代理佣金直达12月55% 🥰2. 新增冲刺人头最高可获得30万 🥰3.9月月均日活最高奖励38888元 🥰4. 新增投注豪礼最高奖励100万元 🥰5. 优质代理长期😀😀佣金比例特权 🥰6.9月指定联赛冠军盘投注返利最高188888 🥰7. 首存彩金+复存彩金+首100送100元体验金 佣金准时|出款稳定|大额无忧 😵官方招商负责人特姆:@crc888 😵双向小助手咨询:@x66666e_bot 😵官方招商推单频道:@ybgf9 😵ZS集团最新招聘岗位咨询 : @crc888
❤17👍13🔥13
Signed 开云官方负责人 -朵莉亚
Showing the 12 most recent of 21 posts we hold for @FAHAN10. 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.
@FAHAN10 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 4 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.
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.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“开云 爱游戏 华体会 乐鱼 星空 OD 九游 MK 米兰 代理招商佣金55%” (@FAHAN10), 30,420 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/FAHAN10.
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.