Cgpay渠道开启通知 Cgpay钱包官方维护已完成,目前平台存款及取款渠道已恢复正常使用,现可正常通过钱包进行存取款操作! 感谢您在维护期间的耐心等待与理解,如有任何疑问,请联系在线客服协助处理!~ 非凡娱乐客服:@feifan6978 非凡娱乐网址: 6868.pw
🖕5

Channel
@feifan777555
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Cite this entry
11,616subscribers
+1,676 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002097873435 |
|---|---|
| Type | Channel |
| Username | @feifan777555 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 30 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/feifan777555 |
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 14 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 20:55 | 11,616 | -164 |
| 8 Nov 2026, 11:06 | 11,780 | -221 |
| 7 Nov 2026, 03:37 | 12,001 | -144 |
| 6 Nov 2026, 04:08 | 12,145 | -146 |
| 5 Nov 2026, 01:31 | 12,291 | -64 |
| 3 Nov 2026, 23:19 | 12,355 | +9,838 |
| 31 Oct 2026, 21:51 | 2,517 | -381 |
| 28 Oct 2026, 16:28 | 2,898 | -242 |
| 25 Oct 2026, 06:27 | 3,140 | -38 |
| 22 Oct 2026, 03:08 | 3,178 | -27 |
| 18 Oct 2026, 12:58 | 3,205 | -23 |
| 15 Oct 2026, 13:16 | 3,228 | -40 |
| 12 Oct 2026, 21:28 | 3,268 | -125 |
| 6 Oct 2026, 01:21 | 3,393 | -46 |
| 28 Sept 2026, 12:00 | 3,439 | -40 |
| 19 Sept 2026, 05:19 | 3,479 | -20 |
| 14 Sept 2026, 20:39 | 3,499 | -101 |
| 11 Sept 2026, 08:57 | 3,600 | -648 |
| 6 Sept 2026, 18:40 | 4,248 | -4,987 |
| 2 Sept 2026, 04:23 | 9,235 | first reading |
10 posts held, back to 23 July 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 48 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 4 November 2026 |
|---|---|
| Posts held | 10 (23 July 2026 – 4 November 2026) |
| Views total | 2,185 |
| Reactions total | 10 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 12:54 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 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.
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.
40 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 82.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🖕 | 33 | 82.5% | |
| ❤ | 7 | 17.5% |
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 7 of the 10 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 40 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 23 July 2026 to 4 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.
Telegram’s own ‘edited’ marker: 0 of 2 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).
Cgpay渠道开启通知 Cgpay钱包官方维护已完成,目前平台存款及取款渠道已恢复正常使用,现可正常通过钱包进行存取款操作! 感谢您在维护期间的耐心等待与理解,如有任何疑问,请联系在线客服协助处理!~ 非凡娱乐客服:@feifan6978 非凡娱乐网址: 6868.pw
🖕5
新鲜感容易得到,非凡体验才值得留下。 真正的非凡,从来经得起时间。 最后一舞,放下犹豫,放下顾虑。 不留后手,不留遗憾,拼尽全力,向着非凡而去。
🖕5
恭喜非凡娱乐玩家6****9 喜爆大奖48965元!!! 别人开始搞,你说不好搞 别人坚持搞,你说利润少 别人搞大了,你说搞迟了 别人挣钱了,你说人家搞得早 非凡娱乐网址: 6868.pw 非凡客服:@feifan6978 首存500送188 首存1000送288 同时首次注册3天内达标活跃流水(10000)加赠100 活动 不定期发放8888扶持 扶持领取流程:注册-绑定提现信息-发账号登记-充值记录/到账记录截图-派送扶持到账
🖕5
恭喜非凡娱乐代理1****2 喜爆大奖2️⃣8️⃣1️⃣3️⃣7️⃣元!!! 别人开始搞,你说不好搞 别人坚持搞,你说利润少 别人搞大了,你说搞迟了 别人挣钱了,你说人家搞得早 非凡娱乐网址: 6868.pw 非凡客服:@feifan6978 首存500送188 首存1000送288 同时首次注册3天内达标活跃流水(10000)加赠100 活动 不定期发放8888扶持 扶持领取流程:注册-绑定提现信息-发账号登记-充值记录/到账记录截图-派送扶持到账
🖕5
非凡娱乐 pinned Deleted message
非凡娱乐 pinned a video
恭喜非凡娱乐玩家G****9 喜爆大奖700000元!!! 加入非凡,遇见更好的自己。 每一步成长,都在创造不一样的未来。 一起突破自我,共创无限可能。 加入非凡,挑战无限,赢得未来! 非凡娱乐网址: 6868.pw 非凡客服:@feifan6978 500扶持188 1000扶持288 或注册后5天内累计存款500 扶持288 同时3天内达标活跃流水(10000)加赠100 活动 不定期发放8888扶持 扶持领取流程:注册-绑定提现信息-发账号登记-充值记录/到账记录截图-派送扶持到账
❤7🖕5
恭喜非凡娱乐代理T****3 喜爆大奖1️⃣4️⃣0️⃣0️⃣0️⃣0️⃣元!!! 加入非凡,遇见更好的自己。 每一步成长,都在创造不一样的未来。 一起突破自我,共创无限可能。 加入非凡,挑战无限,赢得未来! 非凡娱乐网址: 6868.pw 非凡客服:@feifan6978
🖕4
恭喜非凡娱乐代理c*****6 喜提5⃣0️⃣0️⃣0️⃣0️⃣元!!! 别人开始搞,你说不好搞 别人坚持搞,你说利润少 别人搞大了,你说搞迟了 别人挣钱了,你说人家搞得早 网址:6868.pw
🖕4
转折点从来不是偶然,而是一次又一次坚持累积出来的结果。 机会一直都在,改变从行动开始,突破从坚持开始。 每一个不放弃的今天,都可能成为明天逆风翻盘的起点。
Showing the 10 most recent of 10 posts we hold for @feifan777555. 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.
We recorded 1 post on @feifan777555 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.
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.
“非凡娱乐” (@feifan777555), 11,616 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/feifan777555.
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.