Telegram RegisterThe public register of Telegram

Channel

@zhaofen 找粉

@zhaofen1

2 usernames

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

4subscribers

+0 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002352218093
TypeChannel
Usernames@zhaofen @zhaofen1
Description干将5 @vip7602
Created13 May 2025 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/zhaofen1

Growth

412 Aug 2026, 11:07 — 4 subscribers13 Aug 2026, 10:02 — 4 subscribers12 Aug 2026, 11:0713 Aug 2026, 10:02
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 10:024no change
12 Aug 2026, 11:074first reading

Engagement

12 posts held, back to 13 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 14 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Links
2

Lifetime counters from Telegram’s own channel header, read 13 August 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.

Recent posts

14 Apr 2026, 01:00 UTC14 viewsread 13 August 2026
Photo

NFT 官网一口价，喜欢的直接拍。🧧 更多nft用户名 @tg8tg 🇸🇰 NFT列表: 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- 16- 17- 18- 19- 20- usdt 购买联系 @ganjiang 干将 @NFT899 已上链用户名1000个。 😢NFT @zouyan 走烟(走私烟) @tg8tg @tgtg8 @tgtgQ @o66666 @j66666 @p66666

14 May 2025, 17:56 UTC131 views0 reactionsread 13 August 2026

用户名nft出售列表(4) 😢NFT @zhaodie 找爹 赵蝶 😢NFT @duichang 对唱 😢NFT @zhaofen 找粉 😢NFT @zanfen 赞粉 😢NFT @shangliao 上料 😢NFT @kuojun 扩军 😢NFT @yingzhan 影展 迎战 😢NFT @lazhan 蜡展 拉战 😢NFT @guochuang 国创 😢NFT @guozuan 国钻 😢NFT @xianguan 县官 现管 😢NFT @xunguan 迅冠 勋官 😢NFT @paoguan 炮管 跑官 😢NFT @paobang 炮榜 炮棒 😢NFT @weiluo 微裸 微络 😢NFT @panshe 盘蛇 盘社 😢NFT @panzheng 盘整 潘正 😢NFT…

14 May 2025, 17:56 UTC107 viewsread 13 August 2026

官方一口价，喜欢的直接拍 1 😢NFT @miaokuan 秒款 😢NFT @shunkuan 顺款 😢NFT @chongkuan 充款 😢NFT @luansha 乱杀 😢NFT @shangliao 上料 😢NFT @zhucang 逐仓 😢NFT @daichang 代偿 😢NFT @shoushui 收税 😢NFT @chuangqun 创群 2 😢NFT @souguan 搜官 😢NFT @xiangui 显贵 😢NFT @jiezhu 借助 😢NFT @xishou 吸收 😢NFT @youxing 有型 😢NFT @yuangao 原告 😢NFT @saohen 骚痕 😢NFT @biaonan 标男 😢NFT @huashou 画首 😢NF…

14 May 2025, 17:53 UTC48 viewsread 13 August 2026

@ganjiang 干将 @ganjiangmoye 干将莫邪 @jingbiao 竞标 @duobiao 夺标 @xuanyue 玄月 @suoda 索达 @suoen 索恩 @hwtd689 @hwff078 @tuoling 驼铃 @rouduo 肉多 @rouwo 肉我 @youxing 游行 有型 @yuangao 原告 @shaquan 杀拳 @xishou 喜售 吸收 @tongkuai 痛快 @waima 外码 @hongpo 红婆 @renxuan 任选 @guishou 鬼首 @huashou 华首 @mianshen 免审 @luansha 乱杀 @chuangqun 创群 @shangliao 上料 @zhaofen 找粉 @zhaoku 找酷 @bindao 滨岛 @bingdun 冰墩 墩 @qikuan （七)期款 @wukuang 五矿 …

Showing the 12 most recent of 12 posts we hold for @zhaofen1. 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.

Citation-graph rank

Citation-graph rank — 685,386 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 29 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 24 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.

@chongshi 充实
@ganjiang88888 · 42 postso签+o风(有钱又顺丰)o钱
@oqian · 32 posts挑美 频道
@qiankou1 · 102 posts刷贴带贴 飞机微信用户名
@shuatiebot · 62 posts索达id全拼@suoda出售。老频道 带贴+用户名+微信ws+飞机号 代开会员
@suoda · 42 postsNFT @bindao 滨岛 宾道
@bindao8 · 21 post@caokong 操控
@caokong6 · 31 postNFT @chengtai 𫍯泰
@chengtai · 31 postNFT @dangyong 当勇
@dangyong1 · 31 postNFT @diaoyang 屌样
@diaoyang1 · 21 post@fj4444
@FJ4444 · 21 post@goudang 勾当
@goudang8 · 21 post@guochuang 国创
@guochuang1 · 31 postNFT @hongkuo 宏阔
@hongkuobot · 21 post@kangjuan 康娟
@kangjuan · 31 postNFT @kangxun 康讯
@kangxunbot · 31 post@kouban 扣板
@koubanbot · 31 post@panshe 盘蛇🐍 盘社
@panshebot · 31 postNFT 强权主义
@qiangquanzhuyi · 81 post@qiongshang 琼商
@qiongshang · 21 post屈晴 趣情
@quqing_bot · 21 post@tuoling 驼铃
@tuoling1 · 21 post@xinleng 心冷 新冷
@xinleng8 · 21 postNFT @zhuangdi 庄帝
@zhuangdi1 · 31 post

Names

Channels on the register whose handles appear in this channel's posts.

NFT @bindao 滨岛 宾道
@bindao8 · 22 posts@caokong 操控
@caokong6 · 32 posts@chongshao 冲少
@chongshao1 · 32 posts@chuangqun 创群
@chuangqun1 · 22 posts@congzheng 从政
@congzheng1 · 22 postsNFT @diaoyang 屌样
@diaoyang1 · 22 posts@goudang 勾当
@goudang8 · 22 posts@guochuang 国创
@guochuang1 · 32 posts骚名用户名NFT任选🆔
@tg8tg · 2952 posts@tuoling 驼铃
@tuoling1 · 22 postsNFT @bokou 博口
@bokou1 · 21 post@couhe 凑合
@couheBOT · 21 postNFT @cuifei 崔飞
@cuifeibot · 31 post@cujiu 粗九 醋酒
@cujiubot · 21 postNFT 底稿 迪高
@digao1 · 21 postNFT @duobiao 夺标
@duobiao1 · 21 postNFT @feique 飞雀 肥缺
@feique1 · 21 postNFT @gousan 狗三
@gousan8 · 31 postNFT @hongkuo 宏阔
@hongkuobot · 21 post@kuangxiao 狂笑
@kuangxiao1 · 101 post@tunbao 屯宝
@tunbao1 · 21 postNFT @xianguan 县官 现管
@xianguan1 · 21 post@zhuailongbot
@zhuailongbot · 41 postNFT @zhuangdi 庄帝
@zhuangdi1 · 31 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“@zhaofen 找粉” (@zhaofen1), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/zhaofen1.

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.