🟢@shendi 神帝 8000 🟢@shenqu 神曲 8000 🟢@chuqin 楚秦 1800 🟢@chaojin 朝觐 1200 🟢@lingzu 灵族 800 🟢@taishou 太守 3000 🟢@junshou 郡守 3000
Channel
taishou(太守)
@taishou
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
6subscribers
-2 since we began measuring on 15 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001739940298 |
|---|---|
| Type | Channel |
| Usernames | @puzong @taishou |
| Created | 20 August 2022 — measured — dated from the channel’s first post |
| First recorded | 15 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/taishou |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 63% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 19:39 | 6 | -1 |
| 2 Oct 2026, 15:39 | 7 | no change |
| 30 Sept 2026, 23:41 | 7 | -1 |
| 15 Sept 2026, 08:47 | 8 | no change |
| 15 Sept 2026, 08:22 | 8 | no change |
| 15 Sept 2026, 07:47 | 8 | first reading |
Engagement
9 posts held, back to 20 August 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of 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 9 September 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
✨【城市地区】 🟢@enshi 恩施 🟢@xican 西餐 🟢@aierlan 爱尔兰 ------------------------------ 🟢@hualv 华旅 🟢@haixiao 海啸 🟢@xianfeng 咸丰 ------------------------------ 🟢@pubei 浦北 🟢@fangte 方特 🟢@shibiao 市标 ------------------------------ 🟢@hangjian 航舰 🟢@jiangjing 江景 🟢@meihang 美航 🟢@nanhang 南航 🟢@chengshi 城市 🟢@chenggui 城轨 🟢@chengzhu 城主
🍀高净值用户名商店 | Username Store 📌@nftbao 宝藏 @lizuo 中文列表 :1 +888选号频道:待推出 🕴🏻业主 |可可豆: Owner :@kekedou
➡️@qianji 千机 2000 ➡️@enshi 恩施 12000 ➡️@minzu 民族 11000 ➡️@manzu 满足/满租 13000 ➡️@xintuo 信托 28888 ➡️@zhongtou 中投 5000 ➡️@xinpin 新品 12888 ➡️@dazhan 大战 8888 ➡️@renlun 人伦 8888 ➡️@duihua 对话 2800 ➡️@wushen 武神 12000 ➡️@diandan 点单 5000 ➡️@guanxuan 官宣 8000
@taishou 太守 @piaoqu 嫖趣 @pingdingshanshi 平顶山市 @pingshu 评书 @pinru 品如 @pubei 浦北 @puzong 浦总 @qianji 千机 千姬 @qianweichang 钱伟长 @qianzhuan 前传
🍀高净值用户名商店 | Username Store 📌@nftyouming 宝藏 @lizuo 🎆购买用户名 | Buy Username 中文列表 :1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 -20 -21 -22 -23 -24 -25 -26 -27 -28 -29 -30 -31 -32 -33 TRX | VIP English : 1 -2 -3 -4 -5 -6 -7 -8 -9 +888选号频道:待推出 🕴🏻业主 |可可豆: Owner :@kekedou
1
1
Channel created
Showing the 9 most recent of 9 posts we hold for @taishou. 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 3 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.
@nftbao · 63 posts12
@dongre · 462 posts永恒藏品 NFT宝
@lizuo · 6342 poststaishou(太守)
@pubei · 62 poststaishou(太守)
@qianji · 62 posts1
@aierlan · 111 post7
@chengshi · 71 post8
@chuqin · 71 post11
@dasuo · 2021 post辛德勒
@diandan · 81 post15
@gouxiang · 51 post18
@huiyinghong · 81 postjunshou(郡守)
@junshou · 61 postlingtouren(领头人)
@lingtouren · 51 post2016
@lingtouren · 501 posthrggg
@lingzu · 91 posttaishou(太守)
@pingdingshanshi · 71 posttaishou(太守)
@qianweichang · 71 posttaishou(太守)
@qianzhuan · 71 postmaibige(买/卖币哥)
@shenqu · 91 postpitiaoge(皮条哥)
@shibiao · 91 postbchao(B超)
@taqukefu · 61 postyunniang(酝酿 芸娘)
@xianfeng · 61 posttoudan(投单)
@xican · 51 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“taishou(太守)” (@taishou), 6 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/taishou.
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.