Telegram RegisterThe public register of Telegram
Telegram profile photo for 经理皮肤号

Channel

经理皮肤号

@KXYYHP

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

3,309subscribers

-49 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002295210890
TypeChannel
Username@KXYYHP
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/KXYYHP

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 37% 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

3,3093,3583,333.57 August 2026 — 3,358 subscribers8 August 2026 — 3,357 subscribers11 August 2026 — 3,352 subscribers14 August 2026 — 3,350 subscribers17 August 2026 — 3,358 subscribers24 August 2026 — 3,351 subscribers27 August 2026 — 3,354 subscribers30 August 2026 — 3,345 subscribers3 September 2026 — 3,340 subscribers8 September 2026 — 3,333 subscribers12 September 2026 — 3,321 subscribers16 September 2026 — 3,320 subscribers25 September 2026 — 3,309 subscribers7 August 202625 September 2026
13 measurements spanning 49 days, net -49. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,302–3,365 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 18:013,309-11
16 Sept 2026, 19:363,320-1
12 Sept 2026, 16:563,321-12
8 Sept 2026, 20:213,333-7
3 Sept 2026, 09:343,340-5
30 Aug 2026, 18:273,345-9
27 Aug 2026, 10:063,354+3
24 Aug 2026, 09:583,351-7
17 Aug 2026, 19:533,358+8
14 Aug 2026, 16:153,350-2
11 Aug 2026, 05:243,352-5
8 Aug 2026, 07:033,357-1
7 Aug 2026, 14:033,358first reading

Engagement

6 posts held, back to 7 August 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 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 6 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 20:03 UTC8 viewsread 7 August 2026

37.236.132.27 三位数联系我 @Bomplayer886

Signed 海关吖

7 Aug 2026, 16:40 UTC16 viewsread 7 August 2026
Photo

谷歌邮箱一体 立即解绑 23 @Bomplayer886

Signed 海关吖

7 Aug 2026, 16:01 UTC19 viewsread 7 August 2026
Photo

邮箱手机号我的 减去其他 6颗宝石任意兑换 38 @Bomplayer886

Signed 海关吖

7 Aug 2026, 12:08 UTC5 viewsread 7 August 2026
Photo

手机号加谷歌加邮箱 全部我的数据 安全 给价格 @Bomplayer886

Signed 海关吖

7 Aug 2026, 06:47 UTC18 viewsread 7 August 2026
Photo

单邮箱 战神号 有一把冰霜1级 g三妹控都有皮肤 65 @Bomplayer886

Signed 海关吖

Showing the 6 most recent of 6 posts we hold for @KXYYHP. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“经理皮肤号” (@KXYYHP), 3,309 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/KXYYHP.

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.