😢NFT @luansha 乱杀 😢NFT @luancha 乱叉
Channel
NFT @luancha 乱叉
@luancha1
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
2subscribers
+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 | -1003112500447 |
|---|---|
| Type | Channel |
| Usernames | @luancha @luancha1 |
| Description | 41# |
| Created | 11 October 2025 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/luancha1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 23:34 | 2 | no change |
| 12 Aug 2026, 04:17 | 2 | first reading |
Engagement
7 posts held, back to 11 October 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 11 November 2025. 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
https://fragment.com/username/@luancha 😢NFT @luancha 乱叉
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 干将
用户名nft出售列表(2) 😢NFT @jingbiao 竞标 😢NFT @duobiao 夺标 😢NFT @duibiao 对飙 😢NFT @danbiao 单飙(担保) 😢NFT @biaonan 飙男 标男 😢NFT @xiongnan 凶男 😢NFT @zhuandou 赚豆 @zengdou 赠豆 😢NFT @tongchao 通钞 😢NFT @tongshua 通刷 😢NFT @zhishua 直刷 😢NFT @seshua 色刷(色刷料) 😢NFT @shuadian 刷点 😢NFT @tiaodian 跳点 😢NFT @shuatie 刷贴 😢NFT @shuadui 刷兑(闪兑) 😢NFT @kuandui 款对 款兑( 承兑) 😢NF…
用户名nft出售列表(8) 😢NFT @guanlan 观澜(深圳) 😢NFT @yuangao 原稿 原告 😢NFT @digao 底稿 迪高 😢NFT @qiage 恰哥 七阿哥 😢NFT @zangge 藏哥 😢NFT @zangxing 藏星 脏性 😢NFT @linjiao 麟角 林娇 😢NFT @bingliao 冰疗 😢NFT @xiangquan 项圈 香圈 😢NFT @rouduo 柔朵 肉多 😢NFT @roushe 肉社 肉射 😢NFT @rouwo 肉我 😢NFT @woqie 我切 😢NFT @huanwo 环沃 幻我 😢NFT @senlan 森蓝 @senyuan 森源 😢NFT @wanchou 万筹 😢NF…
jin
Channel created
Showing the 7 most recent of 7 posts we hold for @luancha1. 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 — 505,047 of 1,350,102entries 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 77 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.
@luandao · 33 posts刷贴带贴 飞机微信用户名
@shuatiebot · 62 postsNFT @beiri 被日
@beiribot · 21 postNFT @caodang 曹荡
@caodang · 21 post@channian 禅念
@channianbot · 21 post@chashuang 查双 插爽
@chashuang1 · 21 postNFT @duisao 兑扫 对骚
@duisaobot · 31 postNFT @duixiao 对销
@duixiaobot · 21 postNFT @houwo 吼我 猴窝 厚沃
@houwobot · 21 postNFT @huanwo 环沃 幻我
@huanwo1 · 21 postNFT @kuojiu 阔九
@kuojiubot · 21 postNFT @lianneng 联能
@lianneng_bot · 21 post@luansha 乱杀
@luanshabot · 21 postNFT @paodui 炮队
@paoduibot · 21 postNFT @qiaojiu 翘久 荞酒
@qiaojiubot · 31 postnaiqiu奶球saonai骚奶
@qiaosao · 121 postNFT @qiongpei 琼佩
@qiongpeibot · 21 postNFT @rangtian 让天 让舔
@rangtianbot · 21 post@roushe 肉社 肉射
@roushe1 · 21 post奢婷 社厅
@shetingbot · 21 postNFT @suitie 随贴
@suitiebot · 21 post索达id全拼@suoda出售。老频道 带贴+用户名+微信ws+飞机号 代开会员
@suoda · 41 post永妙
@yongmiaobot · 21 post@yongshua 永刷
@yongshuabot · 21 post
Names
Channels on the register whose handles appear in this channel's posts.
@luanshabot · 22 postsNFT @chahei 查黑
@chahei8 · 21 postNFT @chasao 查扫 查骚
@chasao1 · 21 post@chashuang 查双 插爽
@chashuang1 · 21 postNFT @danbiao 单飙(担保)
@danbiao_bot · 21 postNFT 底稿 迪高
@digao1 · 21 postNFT @duisao 兑扫 对骚
@duisaobot · 31 postNFT @duobiao 夺标
@duobiao1 · 21 postNFT @fakuang 发狂
@fakuang1 · 21 postNFT @huanwo 环沃 幻我
@huanwo1 · 21 postNFT @jingbiao 竞标
@jingbiao_bot · 51 postNFT @panpiao 盘票
@panpiao · 31 postNFT @biping 币评
@piping8 · 21 post恰哥 七阿哥
@qiage1 · 21 postNFT 强权主义
@qiangquanzhuyi · 81 post@senlan 森蓝,森岚,森澜
@senlan8 · 31 post@shanpiao 闪票
@shanpiao8 · 21 post@shuadian 刷店 刷电
@shuadian1 · 21 postNFT @shuhao 书豪
@shuhao8 · 21 postNFT @tiaodian 跳点
@tiaodiang · 21 post@tongchao 通钞
@tongchao · 21 post@xiangquan 项圈 香圈
@xiangquan · 31 postNFT @xiongnan 凶男
@xiongnanren · 21 post@zhishua 直刷
@zhishuabot · 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
- 3
- 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
- 3
- vacant every time we have ever looked
@luancha1 named 3 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, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“NFT @luancha 乱叉” (@luancha1), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/luancha1.
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.