Channel
@boshuaibot
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 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002362458688 |
|---|---|
| Type | Channel |
| Usernames | @boshuai @boshuaibot |
| Description | @tg8tg |
| Created | 16 October 2024 — 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/boshuaibot |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 04:32 | 2 | no change |
| 13 Aug 2026, 01:46 | 2 | first reading |
7 posts held, back to 16 October 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 7 posts for this entry, the most recent from 28 May 2026. An engagement rate over an empty window would be a number about nothing.
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.
😢NFT @guashuai 挂帅 😢NFT @anshuai 安帅 😢NFT @bashuai 8帅 霸帅 😢NFT @guishuai 鬼帅 😢NFT @boshuai 波帅 博帅 😢NFT @guoshuai 郭帅 😢NFT @kaishuai 凯帅 开帅 😢NFT @jiaoshuai 焦帅 😢NFT @chuanshuai 川帅 😢NFT @gushuai 谷帅 顾帅 古帅 😢NFT @shishuai 十帅 😢NFT @shuaiwai 帅歪 😢NFT @waishuai 歪帅 😢NFT @shuaizeng 帅曾 😢NFT @shuaiwa 帅娃 😢NFT @shuaimiao 帅猫 😢NFT @shuaigou 帅狗
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
Channel photo updated
https://fragment.com/username/@boshuai 😢 @boshuai 博帅 波帅
😢NFT @boshuai 博帅 波帅
用户名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 @k…
Channel created
Showing the 7 most recent of 7 posts we hold for @boshuaibot. 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 — 478,589 of 1,478,351entries 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 69 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.
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.
@boshuaibot 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“NFT @boshuai 博帅 波帅” (@boshuaibot), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/boshuaibot.
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.