😢NFT @zuiru 嘴入
Channel
NFT @zuiru 嘴入
@zuiru
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1subscribers
+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 | -1002920911157 |
|---|---|
| Type | Channel |
| Username | @zuiru |
| Created | 23 September 2025 — measured — dated from the channel’s first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/zuiru |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 10:15 | 1 | no change |
| 12 Aug 2026, 16:31 | 1 | first reading |
Engagement
7 posts held, back to 23 September 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 7 posts for this entry, the most recent from 22 January 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 2
Lifetime counters from Telegram’s own channel header, read 15 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
https://fragment.com/username/@zuiru 😢NFT @zuiru 嘴入
用户名nft出售列表(8) 😢NFT @guanlan 观澜(深圳) 😢NFT @yuangao 原稿 原告 😢NFT @digao 底稿 迪高 😢NFT @qiage 恰哥 七阿哥 😢NFT @zangge 藏哥 😢NFT @zangxing 藏星 脏性 😢NFT @linjiao 麟角 林娇 😢NFT @bingliao 冰疗 😢NFT @bingsun 冰笋 😢NFT @bingmeng 冰梦 😢NFT @xiangquan 项圈 香圈 😢NFT @rouduo 柔朵 肉多 😢NFT @roushe 肉社 肉射 😢NFT @rouwo 肉我 😢NFT @beiri 被日 😢NFT @zuiru 嘴入 😢NFT @woqie 我切 😢NFT …
@feida
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个
@zuiru 嘴入
Channel created
Showing the 7 most recent of 7 posts we hold for @zuiru. 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 30 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.
@bbmei · 31 postNFT @beiri 被日
@beiribot · 21 postNFT @caodang 曹荡
@caodang · 21 post@channian 禅念
@channianbot · 21 postNFT 底稿 迪高
@digao1 · 21 post@haizhang 还涨
@haizhang · 21 postNFT @huanwo 环沃 幻我
@huanwo1 · 21 postNFT 孔冷 空冷
@konglengbot · 21 postNFT @kuojiu 阔九
@kuojiubot · 21 post@liati 俩提
@liati · 31 postNFT @luandao 鸾刀 乱刀
@luandao · 31 post@luansha 乱杀
@luanshabot · 21 post@luesha 掠杀
@luesha_bot · 21 postNFT @paodui 炮队
@paoduibot · 21 postNFT @qiangduan 抢断 强端
@qiangduan1 · 21 postNFT @rangtian 让天 让舔
@rangtianbot · 21 post@roushe 肉社 肉射
@roushe1 · 21 post奢婷 社厅
@shetingbot · 21 postNFT @shuhao 书豪
@shuhao8 · 21 post@tianbeng 天崩
@tianbeng · 21 postNFT @woqie 我切
@woqie1 · 21 post永妙
@yongmiaobot · 21 post@yongshua 永刷
@yongshuabot · 21 post@Zangmiao 藏苗
@zangmiao · 21 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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@zuiru named 2 handles 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 16 August 2026 – 16 August 2026
named in 1 post, 16 August 2026 – 16 August 2026
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“NFT @zuiru 嘴入” (@zuiru), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/zuiru.
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.