导航分类,点击直接跳转 客服 - 老板 点击直接跳转
Channel
老板/客服
@kshuan
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
8subscribers
+1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003806732190 |
|---|---|
| Type | Channel |
| Username | @kshuan |
| Created | 21 April 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 2 October 2026 |
| On Telegram | t.me/kshuan |
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 93% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 01:29 | 8 | +1 |
| 12 Aug 2026, 19:17 | 7 | no change |
| 10 Aug 2026, 03:46 | 7 | first reading |
Engagement
5 posts held, back to 21 April 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 page 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 5 posts for this entry, the most recent from 19 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
3 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 2 of the 5 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 21 April 2026 to 19 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
1
老板 @anglaoban 108 昂老板 @aolaoban 198 澳老板 @banglaoban 108 棒老板 @benglaoban 108 蚌老板 @biaolaoban 138 彪老板 @binglaoban 198 冰老板 @canlaoban 168 灿老板 @celaoban 138 策老板 @choulaoban 108 臭老板 @chuanglaoban 108 创老板 @chuanlaoban 168 川老板 @chuilaoban 108 捶老板 @chuolaoban 108 绰老板 @cilaoban 108 此老板 @dielaoban 138 蝶老板 @diulaoban 108 丢老板 @dunlaoban 108 蹲老板 @enlaoban 138 恩老板 @fenlaoban 138 芬老板 @ganglaoban 138 刚老板 @geilaoban 108 给老板 @…
❤2
客服 @kf0003 198 @kf0222 198 @kf0333 198 @kf0999 198 @kf1116 198 @kf2111 198 @kf2220 198 @kf2224 198 @kf2225 198 @kf2227 198 @kf2228 198 @kf2229 198 @kf2888 198 @kf3000 198 @kf3330 198 @kf3331 198 @kf3336 198 @kf3337 198 @kf3338 198 @kf4111 198 @kf4222 198 @kf4333 198 @kf4442 198 @kf4443 198 @kf4666 198 @kf4777 198 @kf4999 198 @kf5111 198 @kf5222 198 @kf5333 198 @kf5551 198 @kf5552 198 @kf5553 198 @kf6111 198 @kf6222 …
❤1
Channel created
Showing the 5 most recent of 5 posts we hold for @kshuan. 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 2 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.
@bb2y2 · 11 postbbb77x
@bbb77x · 31 postcc8p8
@cc8p8 · 11 postccc77p
@ccc77p · 21 postgg5p5
@gg5p5 · 11 postgg8p8
@gg8p8 · 11 postkkk22y
@kkk22y · 41 postpppdd6
@pppdd6 · 31 postqq6g6
@qq6g6 · 11 postsss33h
@sss33h · 31 postuu2z2
@uu2z2 · 11 postuuu33w
@uuu33w · 11 postuuu44k
@uuu44k · 11 postvv2o2
@vv2o2 · 31 postvv3b3
@vv3b3 · 31 postwoguangguang
@woguangguang · 11 postww4s4
@ww4s4 · 11 postwwj6w
@wwj6w · 11 postwwu8w
@wwu8w · 11 postwwwiix
@wwwiix · 11 postyy6m6
@yy6m6 · 31 postzhengshanshan
@zhengshanshan · 11 postzhunainai
@zhunainai · 31 postzz5n5
@zz5n5 · 41 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
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@kshuan 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 13 August 2026 – 13 August 2026 · confirmed gone 13 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“老板/客服” (@kshuan), 8 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/kshuan.
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.