Telegram RegisterThe public register of Telegram
Telegram profile photo for 薄荷·供需频道 @xiupai

Channel

薄荷·供需频道 @xiupai

@xiupai

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

2,410subscribers

+1,577 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003994010330
TypeChannel
Username@xiupai
CreatedBetween 1 April 2026 and 24 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/xiupai

Topic

Personal blog — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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

8336,2783,555.57 August 2026 — 833 subscribers8 August 2026 — 833 subscribers8 August 2026 — 834 subscribers16 August 2026 — 966 subscribers23 August 2026 — 1,005 subscribers26 August 2026 — 1,008 subscribers29 August 2026 — 1,017 subscribers31 August 2026 — 6,278 subscribers4 September 2026 — 1,683 subscribers10 September 2026 — 1,771 subscribers13 September 2026 — 2,140 subscribers17 September 2026 — 2,410 subscribers2,4107 August 202617 September 2026
12 measurements spanning 41 days, net +1,577. 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 16–7,095 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 22:372,410+270
13 Sept 2026, 16:002,140+369
10 Sept 2026, 02:581,771+88
4 Sept 2026, 15:411,683-4,595
31 Aug 2026, 21:046,278+5,261
29 Aug 2026, 06:251,017+9
26 Aug 2026, 12:111,008+3
23 Aug 2026, 19:561,005+39
16 Aug 2026, 05:39966+132
8 Aug 2026, 09:37834+1
8 Aug 2026, 01:21833no change
7 Aug 2026, 11:16833first reading

Engagement

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

Reaction mix

181 reactions across 18 posts, in 20 distinct kinds. The most used accounts for 32.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5832.0%
😭5027.6%
👍189.94%
🌚116.08%
🤪116.08%
🔥73.87%
🤝42.21%
🤡42.21%
🥰31.66%
🍾21.10%
💔21.10%
💘21.10%
🤨21.10%
🎉10.552%
👎10.552%
👏10.552%
💩10.552%
🤔10.552%
🤣10.552%
🤮10.552%

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 20 of the 20 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 181 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 24 June 2026 to 6 August 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.

Telegram Stars

Stars received
18
across the posts below
Posts paid on
6
of 20 we hold a reading for · 30%
Most on one post
9
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @xiupai. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 24 June 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Aug 2026, 11:17 UTC108 views11 reactionsread 8 August 2026
Photo

Photo, posted without a caption

😭4👍21🔥1🤔1🤣1🤮1

Signed 薄荷

5 Aug 2026, 03:21 UTC250 views10 reactions1 Starread 8 August 2026

或許有一天你會後悔 或許依舊覺得自己做的對

🔥3🍾2🤨2😭2👍1

Signed

2 Aug 2026, 15:14 UTC291 views6 reactionsread 8 August 2026

我曾以為時光無限 但轉眼沧海尽迁

3😭2💩1

Signed 薄荷

30 Jul 2026, 18:22 UTC486 views16 reactionsread 8 August 2026

物是人非事事休,欲語淚先流

5😭4🤡3🌚2👍2

Signed 薄荷 @hanhuai

29 Jul 2026, 16:13 UTC513 views11 reactionsread 8 August 2026

我愛的是斷橋殘雪 為何你的雙眸波瀾不驚 卻融化了熱梅氤氳 只留餘溫用來潮濕我的千篇一律 .

😭52👍2👏1🔥1

Signed 薄荷 @hanhuai

27 Jul 2026, 15:24 UTC651 views15 reactionsread 8 August 2026

或許你早就變了 是我記憶中的你太好了.

😭6💘2🔥21🎉1👍1🤡1🥰1

Signed 薄荷 @hanhuai

21 Jul 2026, 05:01 UTC972 views18 reactionsread 8 August 2026

也許思念 是潮濕的木質香

11🌚5👍2

Signed 薄荷 @xiupai

14 Jul 2026, 12:14 UTC≈1,320 views18 reactions1 Starread 8 August 2026

待到今年下雪時 我們會見面.

😭123💔2👍1

Signed

13 Jul 2026, 10:53 UTC≈1,260 views14 reactions1 Starread 8 August 2026

倘若我未能望穿秋水 請先讓雙眼歸於荒蕪.

😭74👍3

Signed 落雨 @biandui

12 Jul 2026, 08:51 UTC946 views13 reactions1 Starread 8 August 2026

人們天真的以為犯錯只需要懺悔.

😭82🥰2👎1

Signed 落雨 @biandui

12 Jul 2026, 03:12 UTC929 views13 reactions9 Starsread 8 August 2026

你我相識第二年.

7🌚4👍2

Signed 落雨 @biandui

7 Jul 2026, 10:42 UTC≈1,180 views13 reactions5 Starsread 8 August 2026

https://t.me/+RQ9qA_coExM4ZjUx

8🤪3👍2

Signed 落雨 @xiupai

Showing the 12 most recent of 20 posts we hold for @xiupai. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

Named by 1 registered channel — 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.

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

“薄荷·供需频道 @xiupai” (@xiupai), 2,410 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/xiupai.

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.