Supergroup
输入关键字就能看到你想看的！
@zhainanfulil
On this record: Growth · Engagement · Citations · Cite this entry
6,879members
+145 since we began measuring on 6 August 2026
307 online right now
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002406372257 |
|---|---|
| Type | Supergroup |
| Username | @zhainanfulil |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/zhainanfulil |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 28 Aug 2026, 15:38 | 6,879 | +4 |
| 27 Aug 2026, 20:46 | 6,875 | no change |
| 26 Aug 2026, 01:18 | 6,875 | +11 |
| 22 Aug 2026, 19:54 | 6,864 | -12 |
| 19 Aug 2026, 14:43 | 6,876 | +21 |
| 16 Aug 2026, 08:46 | 6,855 | +31 |
| 13 Aug 2026, 02:46 | 6,824 | +69 |
| 9 Aug 2026, 19:02 | 6,755 | +20 |
| 6 Aug 2026, 20:24 | 6,735 | +1 |
| 6 Aug 2026, 19:45 | 6,734 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Mentions
Named by 71 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@iiit001 · 6,9858 posts光年-抖音粉丝小红书快手视频号涨粉丝
@wjgn002 · 5,2856 posts热点新闻 刑事犯罪🌎
@xinwen663 · 3,1185 postsTelegram数字生活指南
@Youzhigongxu00 · 5,8035 postsTelegram优质资源导航
@Boling666666 · 3,1433 posts国产热门擦边短剧
@cabian08 · 3,5293 posts艺术三级片春光
@dianying8880 · 4,6763 posts欧美AV|AV女优|色情片|极品洋妞福利站
@omei08 · 4,1093 posts国际新闻|吃瓜新闻|突发事件
@qqhots · 2,9773 posts今日黑平台曝光|黑榜日报
@baoguang066 · 2,9742 posts每日内涵段子🔥吃瓜搞笑视频
@bx666bp · 1,4832 posts擦边短剧㊙️擦边剧
@chygj775 · 1,7312 posts斯里兰卡大事件 东南亚动态 东南亚早报 东南亚新鲜事
@dny99o · 1,9742 posts极品身材
@jhvjjj56885 · 7142 posts一对一视频裸聊馆精品妹妹
@jwjaknwnw · 3692 posts欧美系列 媚黑无码
@omei05 · 1,9152 posts欧美精选无码Av
@omei06 · 1,9152 posts热点曝光台
@SEA999NEWS · 1,5962 posts海外素材库/人设 套图
@sucai098 · 2,5212 posts神仙文案集 一句入心
@wenan018 · 2,4052 posts小红书快手抖音粉丝业务
@wjgn005 · 5332 posts💦 终极快感体验 🔥
@xft345 · 1,9902 posts济南海选上门服务
@oaishsjhfd · 1,0941 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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“输入关键字就能看到你想看的！” (@zhainanfulil), 6,879 members as measured 28 August 2026. Telegram Register, tgregister.com/channel/zhainanfulil.
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.