😢NFT @chuangqun 创群 😢NFT @bangqun 绑群 邦群 😢NFT @douqun 豆群(土豆群) 😢NFT @tddbqun 土豆担保群 😢NFT @daoqun 导群 道群 😢NFT @daoliao 导聊 道聊 😢NFT @jianliao 简聊 😢NFT @qiaqun 恰群 😢NFT @louqun 楼群 😢NFT @yoqun yo群 😢NFT @xuanqun 炫群 选群 😢NFT @qunshi 群狮 😢NFT @qunsong 群松
Channel
NFT @qunsong 群松
@qunsong
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
3subscribers
+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 | -1003782686012 |
|---|---|
| Type | Channel |
| Username | @qunsong |
| Description | 干将65 @vip4905 |
| Created | 13 March 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/qunsong |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 13:17 | 3 | no change |
| 12 Aug 2026, 01:32 | 3 | first reading |
Engagement
8 posts held, back to 13 March 2026 — 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 8 posts for this entry, the most recent from 13 March 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
😢NFT @qunsong 群松
https://fragment.com/username/@qunsong 😢NFT @qunsong 群松
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
用户名nft出售列表(1) 😢NFT @baibo 白波 百博(赌博) 😢NFT @botian 博天 😢NFT @feibo 飞博🥔百博🆚飞达 😢NFT @feida 飞达飞大(飞18把大) 😢NFT @weituo 委托 😢NFT @yangmu 仰慕 养母 😢NFT @jintu 金图 金兔 👍 😢NFT @oqian o签 😿😿 😢NFT @ofeng o丰 😢NFT @danqian 单签 😢NFT @niuqian 牛签(多签 签名) 😢NFT @niuquan 牛圈(牛逼圈) 😢NFT @niumai 牛麦 牛迈 😢NFT @niuqiang 牛强 牛枪 😢NFT @reqiang 热抢 热枪 😢NFT @niuzhou 牛州 😢NFT @niuyong 牛勇 😢NFT @niulin 牛林 😢NFT @ni…
j6
😢NFT @qunsong 群松
Channel created
Showing the 8 most recent of 8 posts we hold for @qunsong. 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 — 283,483 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 33 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.
@qunshi1 · 32 postsNFT @baibo 白波 百博(赌博)
@baiboqun · 291 postNFT @bangqun 绑群 邦群
@bangqunbot · 21 post@botian 博天
@botianpai · 41 postNFT @danqian 单签
@danqian · 21 postNFT @desou 的搜
@desou8 · 21 postNFT @goushou 狗首 勾手
@goushuou1 · 21 postNFT @guishou 鬼首
@guishou1 · 31 postNFT @kuoshen 阔神
@kuoshenbot · 141 postNFT @mianshen 缅神 免审
@mianshen1 · 21 post@niuqiang 牛强 牛枪
@niuqiang8 · 21 postNFT @niuquan 牛圈(牛逼圈)
@niuquan1 · 21 postNFT @niuzhou 牛州
@niuzhou1 · 21 post@niuzhun 牛准
@niuzhunbot · 21 postNFT @piaoshou 嫖首
@piaoshou · 21 postNFT @sansou 三搜
@sansou3 · 21 postNFT @shensong 神松 神颂
@shensong · 21 post@souguan 搜官
@souguanbot · 21 postNFT @soujiu 搜救
@soujiubot · 21 postNFT @souqie 搜切
@souqiebot · 21 postNFT @soutuo 搜拓
@soutuobot · 21 postNFT @weisou 微搜
@weisou_bot · 21 post@xipan 西盘(西港大盘)
@xigangdapan · 31 post@xishou 西首 喜售
@xishou1 · 21 post
Names
Channels on the register whose handles appear in this channel's posts.
@bangqunbot · 22 posts@chuangqun 创群
@chuangqun1 · 22 posts@daoliao 道聊
@daoliaobot · 22 postsNFT @daoqun 导群 道群
@daoqun1 · 842 posts@louqun 楼群
@louqun · 22 posts@qunshi 群狮
@qunshi1 · 32 posts土豆担保公群 @tddbqun
@tddbqun · 102 postsNFT @baibo 白波 百博(赌博)
@baiboqun · 291 postNFT @danqian 单签
@danqian · 21 postNFT @desou 的搜
@desou8 · 21 postNFT @duoniu 多牛 多妞
@duoniu_bot · 21 postNFT @goushou 狗首 勾手
@goushuou1 · 21 postNFT @guishou 鬼首
@guishou1 · 31 postNFT @mianshen 缅神 免审
@mianshen1 · 21 postNFT @niumai 牛卖 牛迈
@niumai1 · 21 postNFT @niuquan 牛圈(牛逼圈)
@niuquan1 · 21 postNFT @niuzhou 牛州
@niuzhou1 · 21 post@niuzhun 牛准
@niuzhunbot · 21 postNFT @sansou 三搜
@sansou3 · 21 postNFT @shensong 神松 神颂
@shensong · 21 post@souguan 搜官
@souguanbot · 21 postNFT @weituo 委托
@weituo8 · 41 post@xishou 西首 喜售
@xishou1 · 21 postNFT @youxing 游行 有型
@youxing6 · 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
- 1
- 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
- 1
- vacant every time we have ever looked
@qunsong named 1 handle 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
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 @qunsong 群松” (@qunsong), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/qunsong.
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.