🟢@fudie 富爹 1800 🟢@futing 副厅/付婷 2500 🟢@fuxiao 副校/拂晓 3000 🟢@kangye 康爷 800 🟢@huner 魂儿 500 🟢@huaner 欢儿 800 🟢@benmei 笨妹 200 🟢@sheishei 谁谁 2800 🟢@hanhuo 憨货 1800 🟢@hanshao 韩少 1200

Channel
孔一凡
@kongyifan
On this record: Growth · Engagement · Posts · Citations · Cite this entry
167subscribers
+166 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002190881583 |
|---|---|
| Type | Channel |
| Usernames | @diaopei @fengqian @fulizongbu @guiban @kongyifan |
| Created | 31 July 2024 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/kongyifan |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 10:59 | 167 | +9 |
| 16 Sept 2026, 21:39 | 158 | +3 |
| 16 Sept 2026, 15:40 | 155 | +3 |
| 15 Sept 2026, 04:47 | 152 | no change |
| 15 Sept 2026, 04:22 | 152 | no change |
| 15 Sept 2026, 03:47 | 152 | +21 |
| 11 Sept 2026, 10:01 | 131 | no change |
| 11 Sept 2026, 01:57 | 131 | +125 |
| 10 Sept 2026, 14:21 | 6 | -74 |
| 1 Sept 2026, 21:45 | 80 | +5 |
| 1 Sept 2026, 13:46 | 75 | +70 |
| 26 Aug 2026, 18:56 | 5 | -15 |
| 25 Aug 2026, 04:34 | 20 | no change |
| 25 Aug 2026, 04:07 | 20 | -6,698 |
| 22 Aug 2026, 04:27 | 6,718 | -6,684 |
| 20 Aug 2026, 20:55 | 13,402 | -237 |
| 19 Aug 2026, 23:54 | 13,639 | +13,633 |
| 19 Aug 2026, 09:24 | 6 | +3 |
| 13 Aug 2026, 17:04 | 3 | no change |
| 12 Aug 2026, 20:19 | 3 | first reading |
Engagement
11 posts held, back to 31 July 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 7.66%
- avg views ÷ 167 subscribers
- Avg views / post
- 12.8
- 5 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 5
- of 11 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.
| Window | Rolling 30 days · latest post in window 9 September 2026 |
|---|---|
| Posts held | 11 (31 July 2024 – 9 September 2026) |
| Views total | 64 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Sept 2026, 05:22 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.
Recent posts
🟢@kefei 课费/可飞 12000 🟢@xiaoqie 小妾 30000 🟢@yingyue 应约 3000 🟢@yuelou 约楼 3000 🟢@renlun 人伦 8888 🟢@shenqu 身躯 神曲 8000 🟢@chapian 查片 5000 🟢@fengrun 丰润 3200 🟢@diandan 点单 5000 ------------------------------ 🟢@bchao b超 8000 🟢@nenyi 嫩姨 2000 🟢@sheyun 射晕 800 🟢@zhenjie 贞洁 1500 🟢@koupao 口炮 1500 🟢@hanzhu 韩助 2000 🟢@gangniu …
🍀高净值用户名商店 | Username Store 📌@nftbao 宝藏 @lizuo 中文列表 :1 +888选号频道:待推出 🕴🏻业主 |可可豆: Owner :@kekedou
@paidan 派单 排单 @diandan 点单 垫单 @toudan 头单 投单 @chuqin 出勤 @touyuan 投缘 @diaopei 调配
@diaopei 调配 @dibaohu 低保户 @feijibi 飞机逼(币) @fengqian 冯倩 封签 @fulizongbu 福利总部 @gangniu 港妞 @gongluan 供暖 供卵 @guiban 贵办 硅板 @hanhuo 韩货 憨货 @hanshao 韩少 晗少
1
https://fragment.com/username/kongyifan -附赠🤖
购买联系 @kekedou
孔一凡:著名饺子馆名。 适用于在境外做餐饮的老板
Channel photo updated
Channel created
Showing the 11 most recent of 11 posts we hold for @kongyifan. 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.
Mentions
Named by 12 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.
@shuangpinwaiwei · 23 posts古今中外人名
@gujinzhongwai01 · 32 posts8
@cizong · 71 post双拼个人IP
@gerenIP · 21 post汉语NFT
@HanYuNft · 61 post@jiecan
@jiecan · 61 post21
@junshuai · 61 postppppa
@ppppa · 81 post三拼外围类
@sanpinwaiwei · 21 postbchao(B超)
@taqukefu · 71 postTG中文用户名出售
@TGlianghao · 5201 post@zhipi
@zhipi · 91 post
Names
Channels on the register whose handles appear in this channel's posts.
@diandan · 82 posts孔一凡
@gangniu · 1342 posts孔一凡
@tingzong · 1592 posts孔一凡
@yunhutui · 1662 postsbchao(B超)
@bchao · 71 post3
@benmei · 51 post8
@chuqin · 71 post孔一凡
@dibaohu · 1701 post孔一凡
@feijibi · 1671 post13
@fengrun · 61 postaa(qu999)
@fenhang · 91 post孔一凡
@gongluan · 1661 posthuaner(欢儿)
@huaner · 61 post18
@huner · 81 post21
@kangye · 61 postg322
@kefei · 81 postg322
@liaoqizhi · 81 postmiaonan(秒男)
@miaonan · 61 post永恒藏品 NFT宝
@nftbao · 5721 postmaibige(买/卖币哥)
@shenqiang · 81 postmaibige(买/卖币哥)
@shenqu · 81 postpitiaoge(皮条哥)
@sheyun · 91 postyuelou(月楼)
@yuelou · 81 postkoupao(口炮)
@zhenjie · 61 post
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“孔一凡” (@kongyifan), 167 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/diaopei.
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.