Channel
@pisaobot
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
6subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002293174590 |
|---|---|
| Type | Channel |
| Usernames | @pisao @pisaobot |
| Description | @zhuailong 拽龙 @xiaozhuailong 小拽龙 |
| Created | 5 December 2024 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/pisaobot |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:16 | 6 | no change |
| 12 Aug 2026, 04:17 | 6 | first reading |
9 posts held, back to 5 December 2024 — 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 9 posts for this entry, the most recent from 17 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
😢NFT @piqin 屁琴 皮琴 😢NFT @pisao 皮嫂 屁骚 😢NFT @duisao 兑扫 对骚 😢NFT @luesao 略骚 😢NFT @wensao 文嫂 文骚 😢NFT @miaosao 苗嫂 秒扫 秒骚 😢NFT @leisao 雷嫂 😢NFT @kuosao 阔嫂 😢NFT @kuangsao 狂骚 狂扫 😢NFT @qingsao 清扫 情骚 庆嫂 😢NFT @qiaosao 俏嫂 巧嫂 翘骚 😢NFT @niangsao 娘骚 😢NFT @chasao 查扫 叉骚
😢NFT @pisao 皮嫂 屁骚 😢NFT @piqin 屁琴 皮琴
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
小l
https://fragment.com/username/@pisao 😢NFT @pisao 皮嫂 屁骚
😢NFT @pisao 皮嫂 屁骚
用户名nft出售列表(9) 😢NFT @shaosao 烧骚 😢NFT @saonai 骚奶 😢NFT @pisao 皮嫂 屁骚 😢NFT @piqin 屁琴 皮琴 😢NFT @duisao 兑扫 对骚 😢NFT @luesao 略骚 😢NFT @wensao 文嫂 文骚 😢NFT @kuangsao 狂骚 狂扫 😢NFT @qingsao 清扫 情骚 庆嫂 😢NFT @qiaosao 俏嫂 巧嫂 翘骚 😢NFT @niangsao 娘骚 😢NFT @chasao 查扫 查骚 😢NFT @saoming 骚名 😢NFT @saogong 骚公 😢NFT @saoguai 骚怪 骚乖 😢NFT @saokang 骚康 😢NFT @saozhuai 骚拽 😢NFT @saogua 骚瓜 😢NFT @saohen 骚痕 …
用户名nft出售列表(15) 😢NFT @dongwa 冬娃 😢NFT @xuanyue 玄月 😢NFT @qionglou 琼楼 😢NFT @jianglan 姜岚 江蓝 😢NFT @piaolan 飘兰 😢NFT @miaolan 妙兰 😢NFT @heqiao 何巧🦩 😢NFT @liqiao 李乔 李巧 😢NFT @renqiao 任巧 人桥 😢NFT @bingmeng 冰梦 😢NFT @miaoli 妙丽 苗栗（台湾市) 😢NFT @mengya 萌芽 梦雅 😢NFT @mengzuan 萌钻 猛赚 😢NFT @mengrun 梦润 😢NFT @qingguai 晴乖 😢NFT @chunqin 春琴 纯琴 😢NFT @chunduo 春朵 😢NFT @chunxue …
Channel created
Showing the 9 most recent of 9 posts we hold for @pisaobot. 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 — 759,047 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.
Named by 8 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@pisaobot 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.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“NFT @pisao 皮嫂 屁骚” (@pisaobot), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/pisaobot.
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.