😢NFT @longchuan 龙川 😢NFT @luelong 掠龙 😢NFT @lielong 烈龙🐉 😢NFT @kualong 夸龙 @longchao 龙巢

Channel
NFT @kualong 夸龙
@kualong1
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002414658782 |
|---|---|
| Type | Channel |
| Usernames | @kualong @kualong1 |
| Description | 干将11 @vip6955 |
| Created | 3 May 2025 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/kualong1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 07:33 | 2 | no change |
| 13 Aug 2026, 09:33 | 2 | first reading |
Engagement
6 posts held, back to 3 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 6 posts for this entry, the most recent from 19 May 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 14 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
Channel photo updated
😢NFT @kualong 夸龙
https://fragment.com/username/@kualong 夸龙
用户名nft出售列表(14) 😢NFT @botian 博天 😢NFT @bochao 博超 😢NFT @boshuai 博帅 波帅 😢NFT @bashuai 8帅 霸帅 😢NFT @baguai 八怪 😢NFT @baniang 8娘 八娘 😢NFT @jinniang 金娘 😢NFT @tunniang 囤娘 😢NFT @beiding 北鼎 😢NFT @dingmi 鼎秘 😢NFT @dingzhuo 鼎卓 订桌 😢NFT @dinghang 鼎航 顶航(导航) 😢NFT @hangxuan 航选(海选) 😢NFT @guanchuan 官船 贯穿 😢NFT @longchuan 龙船 龙川 😢NFT @luelong 掠龙 😢NFT @lielong 猎龙 烈龙🐉 😢NFT @c…
Channel created
Showing the 6 most recent of 6 posts we hold for @kualong1. 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 43 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.
@cailong8 · 32 postsNFT @luelong 掠龙
@luelong1 · 22 postsNFT @baguai 八怪
@baguaibot · 21 post@baniang 八娘
@baniang1 · 21 postNFT @bashui 八水
@bashui_bot · 21 postNFT @bieao 别熬
@bieaobot · 21 postNFT @biehun 别混
@biehunbot · 21 postNFT @bieliu 别溜
@bieliubot · 21 postNFT @boshuai 博帅 波帅
@boshuaibot · 21 postNFT@guanchuan 官船 贯穿
@guanchuan1 · 21 postNFT @jinniang 金娘
@jinniang_bot · 21 post@kezhui 可追
@kezhui1 · 21 postNFT @longchao 龙潮 龙钞 龙巢
@longchaobot · 31 postNFT @neiyue 内约
@neiyuebot · 21 post彭爽 捧双 碰爽
@pengshuang · 21 postNFT @queqing 雀青
@queqing · 21 post冉刚 染缸
@rangangbot · 21 postNFT @shengxie 胜邪
@shengxie1 · 21 post@shouniang 兽娘
@shouniangbot · 41 post@shuangluan 双滦
@shuangluan_bot · 21 post@tunniang 囤娘
@tunniangbot · 21 postNFT @yinrou 音柔
@yinrou1 · 21 post@zhaai 渣爱
@zhaai1 · 21 postNFT 纵雅 总压
@zongya_bot · 21 post
Names
Channels on the register whose handles appear in this channel's posts.
@lielongbot · 42 postsNFT @longchao 龙潮 龙钞 龙巢
@longchaobot · 32 postsNFT @longchuan 龙船 龙川
@longchuan8 · 22 postsNFT @luelong 掠龙
@luelong1 · 22 posts@baniang 八娘
@baniang1 · 21 post@bashuai 8帅 霸帅
@bashuai · 31 postNFT @beiding 北鼎
@beidingbot · 21 post@biesong 别怂
@biesong1 · 21 post@botian 博天
@botianpai · 41 postNFT @dingmi 鼎秘
@dingmiBOT · 31 postNFT @dingzhuo 鼎卓 订桌
@dingzhuo1 · 21 postNFT@guanchuan 官船 贯穿
@guanchuan1 · 21 post@hangxuan 航选 航轩
@hangxuanbot · 21 postNFT @jinniang 金娘
@jinniang_bot · 21 post@kezhui 可追
@kezhui1 · 21 post@longluan 龙鸾
@longluan1 · 21 post@longpang 龙胖
@longpangge · 21 post@longzhuai 龙拽
@longzhuai · 21 postNFT @neiyue 内约
@neiyuebot · 21 postNFT @shengxie 胜邪
@shengxie1 · 21 post@tunniang 囤娘
@tunniangbot · 21 postNFT @xingling 星灵
@xingling6 · 21 postNFT @yingruo 盈若
@yingruobot · 21 post@zhaai 渣爱
@zhaai1 · 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“NFT @kualong 夸龙” (@kualong1), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/kualong1.
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.