📱QQ徒弟反馈 群➕号 全部起飞👍 提升/业务 @fenfh0
👍5

Channel
@fennb666
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
13,626subscribers
+12,312 since we began measuring on 24 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003724375273 |
|---|---|
| Type | Channel |
| Username | @fennb666 |
| Description | 万般机遇 无限可能 |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/fennb666 |
Education — 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 October 2026 and assigned it the closest of 31 fixed categories, at 51% 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 |
|---|---|---|
| 11 Nov 2026, 08:46 | 13,626 | +37 |
| 9 Nov 2026, 12:56 | 13,589 | +20 |
| 8 Nov 2026, 02:20 | 13,569 | +45 |
| 6 Nov 2026, 22:54 | 13,524 | +16 |
| 5 Nov 2026, 20:28 | 13,508 | +23 |
| 4 Nov 2026, 18:16 | 13,485 | +17 |
| 3 Nov 2026, 18:10 | 13,468 | +26 |
| 2 Nov 2026, 19:49 | 13,442 | +11 |
| 1 Nov 2026, 17:58 | 13,431 | +10 |
| 31 Oct 2026, 19:11 | 13,421 | +21 |
| 30 Oct 2026, 15:55 | 13,400 | +18 |
| 29 Oct 2026, 16:17 | 13,382 | +26 |
| 28 Oct 2026, 15:49 | 13,356 | +32 |
| 27 Oct 2026, 17:54 | 13,324 | +36 |
| 26 Oct 2026, 18:18 | 13,288 | +20 |
| 25 Oct 2026, 15:15 | 13,268 | +26 |
| 24 Oct 2026, 17:16 | 13,242 | +25 |
| 23 Oct 2026, 20:40 | 13,217 | +17 |
| 22 Oct 2026, 21:37 | 13,200 | +12 |
| 21 Oct 2026, 19:35 | 13,188 | first reading |
57 posts held, back to 18 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 26 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 13 November 2026 |
|---|---|
| Posts held | 57 (18 September 2026 – 13 November 2026) |
| Views total | 30,126 |
| Reactions total | 436 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 11:24 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 13 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.
513 reactions across 56 posts, in 11 distinct kinds. The most used accounts for 71.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 366 | 71.3% | |
| ❤ | 65 | 12.7% | |
| custom 5136700394033907160 | 34 | 6.63% | |
| custom 6334451835268506146 | 12 | 2.34% | |
| 🥰 | 11 | 2.14% | |
| 🤣 | 7 | 1.36% | |
| 🍌 | 6 | 1.17% | |
| 😱 | 5 | 0.975% | |
| custom 6057627401901315910 | 4 | 0.78% | |
| 😇 | 2 | 0.39% | |
| 🤡 | 1 | 0.195% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 56 of the 57 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 513 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 57 most recent posts we hold, published 18 September 2026 to 13 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: 3 of 41 posts held from the last 30 days (7.32%) 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).
📱QQ徒弟反馈 群➕号 全部起飞👍 提升/业务 @fenfh0
👍5
想买的扣一
👍3
Sticker, posted without a caption
👍3custom 63344518352685061462
免费大头假地址机器人 ‼️新用户免费查询开户 @leomuubot @leomuubot @leomuubot 免费户籍猎手下载 https://t.me/gyyyny/48
👍6custom 51367003940339071603custom 63344518352685061462
📱QQ徒弟反馈稳定 提升/学习 @fenfh0
👍8custom 51367003940339071605custom 63344518352685061464❤1
👍👍👍👍 😀😀😀 各大平台源头账号出售 本店已交500元保证金✅ 如果您正在寻找各大平台账号交易的靠谱的号商源头 不妨来看看我们的店铺 里面有各大国内外社交平台账号资源 涵盖大部分人的需求 且持续更新更多账号资源❤️ 📱快手账号 📱微信账号 📱QQ账号 📱TG账号 🎮和平精英数据号 📱抖音账号 📱小红书账号 💵支付宝账号 📱TG僵尸粉 📱TG会员开通 卡网内所有类型账号一次性买3个联系客服送一个‼️ ⭐怕有人封禁你生活账号?怕有人出你个人信息?购买我的国外挡刀账号注册换绑让他出国外号挡刀码✅ ‼️社交平台所有账号都是发手机号验证码的注册或换绑方式❗️注册的话注册上去都是小白号❗️ 使用方法:注册界面把+86改为购买相对应国家的前缀 把手机号前面的+xxx删除 发送验证码后浏览器搜索链接获取验证码❗️ 各大平台账号购买链接📥 http://i8c.cn/1eQhI 有订单问题 联系TG客服 在卡网内投诉无任…
👍1
📱QQ徒反馈 提升 @fenfh0
👍9custom 63344518352685061463❤1
急急急 哭哭哭
❤4👍1
某些人你就别安排人套你爸爸收款码了 今天晚上一共四个人找过我 三个是问我要支付宝的😅 你爹手里有全套代收系统 想套出我个人信息 下辈子都不可能😂😂
custom 51367003940339071606custom 60576274019013159103👍1
📱QQ稳定 思路稳定无瑕疵 业务/提升 @fenfh0
custom 513670039403390716010👍8❤2
📱快手徒弟反馈 反馈一直都有 今年特别多 提升/拜师 @fenfh0
custom 51367003940339071604👍2
你赤哥 每天晚上熬夜到四五点钟 然后下午甚至快晚上才睡醒😂你徒弟想问你点问题都找不到你人😂 猪头焖子 蠢货赤 @chifh0
👍7❤4
Showing the 12 most recent of 57 posts we hold for @fennb666. 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 5 posts on @fennb666 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
@fennb666 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“枫 封号频道” (@fennb666), 13,626 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/fennb666.
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.