Telegram RegisterThe public register of Telegram
Telegram profile photo for ZUMO - 头皮发麻

Channel

ZUMO - 头皮发麻

@bestzumo

On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

498subscribers

+5 since we began measuring on 22 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002016779821
TypeChannel
Username@bestzumo
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 August 2026
Last confirmed live14 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/bestzumo

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

493500496.522 August 2026 — 493 subscribers22 August 2026 — 493 subscribers23 August 2026 — 494 subscribers30 August 2026 — 496 subscribers7 September 2026 — 500 subscribers14 September 2026 — 498 subscribers49822 August 202614 September 2026
6 measurements spanning 23 days, net +5. 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 492–501 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 23:40498-2
7 Sept 2026, 02:57500+4
30 Aug 2026, 02:59496+2
23 Aug 2026, 21:35494+1
22 Aug 2026, 19:45493no change
22 Aug 2026, 19:30493first reading

Engagement

20 posts held, back to 25 June 2025the 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 19 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

34 reactions across 15 posts, in 14 distinct kinds. The most used accounts for 14.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩514.7%
🤮514.7%
👎411.8%
👏38.82%
😭38.82%
🤡38.82%
👍25.88%
😁25.88%
🤯25.88%
12.94%
🌚12.94%
🎉12.94%
😢12.94%
🤔12.94%

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 15 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 34 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 25 June 2025 to 19 December 2025, 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

19 Dec 2025, 13:49 UTC733 views2 reactionsread 22 August 2026

突然注意到,我们的电信IEPL线路是一直可用的,并且有客户在用(我说怎么很长时间都没客户要求退款。 目前来看,整体用的人不多并且没通报,如果您愿意继续使用,可以不申请退款。(后续如果故障的话,我们考虑不再更换IP,但是您依然可以申请退款。 如果您已经完全不再使用我们的平台,请提交退款。 我们会在 下周开始慢慢处理信息。

🌚1🤔1

Signed Kevin 币圈大傻

18 Dec 2025, 13:57 UTC769 viewsread 22 August 2026

为了避免重复退款或者遗忘,您的信息将会处于未读状态。 如果当您的信息被已读,但是没有收到退款再发消息确认。(请不要反复发送消息

Signed Kevin 币圈大傻

18 Dec 2025, 12:47 UTC771 views5 reactionsread 22 August 2026

我们计划开始退款,请提供您的用户名信息,私聊 @kkkevin123 。将于 本周末继续到下个月初,完全所有的退款。 后续也没有提供服务的计划了。

😭3💩1😢1

Signed Kevin 币圈大傻

3 Nov 2025, 12:30 UTC≈1,070 views5 reactionsread 22 August 2026

原ip被恶意举报封了,不得不下架所有套餐,最后去官网获取新的ip。 再挂了,只能退款关门。最多考虑转成合组模式或摆烂(摆烂概率比较大 另外,入口+对端服务长期保持稳定服务。

🤮5

Signed Kevin 币圈大傻

18 Aug 2025, 18:12 UTC≈1,580 viewsread 22 August 2026

补充: 主要维护 Premium 与 Standard 用户以及个人用户。 Entry 还是尽快申请退款

Signed Kevin 币圈大傻

18 Aug 2025, 17:57 UTC≈1,510 views1 reactionsread 22 August 2026

还有客户需要申请退款的请尽快联系, 下周之后将关闭退款通道。 同时我们就会慢慢认真维护剩余的客户。(如果一些情况相对可控的情况下。

1

Signed Kevin 币圈大傻

12 Aug 2025, 04:00 UTC≈1,540 views2 reactionsread 22 August 2026

请注意,如果您的冷钱包地址属于未激活或没有U,退款需扣除 1.5u或者 5trx。 还剩下部分未来退款的用户如果不做说明都将会按照以上操作退款,因为客户退款就25cny ,避免争议。 (月底还会恢复联通以及专线~~

👎1💩1

Signed Kevin 币圈大傻

10 Aug 2025, 15:10 UTC≈1,220 views1 reactionsread 22 August 2026

由于个人用户总是提供交易所钱包地址,导致能量完全不够用。 目前我们优先完成了 64k能量消耗的客户退款,其他的下周工作日会慢慢退款。(一般个人用户退款不超过10u,放心,真的不会跑 目前恢复了电信,也不是不能用

💩1

Signed Kevin 币圈大傻

5 Aug 2025, 07:06 UTC≈1,200 views2 reactionsread 22 August 2026

前两天出差, zumo 退款有延迟,或者消息被覆盖,或者咕咕咕没处理的。 注: 由于个人用于也出现业务整顿整顿,导致无法使用,我们暂时不考虑维护,如果需要退款,个人用户也可以申请。 现在仅 IPv6 可以正常运行。 麻烦重新发一下,本周会慢慢处理。

💩2

Signed Kevin 币圈大傻

19 Jul 2025, 21:46 UTC≈1,380 views3 reactionsread 22 August 2026

电信IP已更新,暂时恢复,后续看命

👍2🤡1

Signed Kevin 币圈大傻

12 Jul 2025, 04:56 UTC≈1,590 views2 reactionsread 22 August 2026

增加有效期,晚一些处理,近期线下工作繁忙

😁2

Signed Kevin 币圈大傻

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

翻翻墙 | 机场评测
@ffqchannel · 62,201
Telegram ranks this channel #44 of 45 here — alongside 44 others — read 22 August 2026
NodeSeek官方频道
@nodeseekc · 36,546
Telegram ranks this channel #50 of 52 here — alongside 51 others — read 2 September 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“ZUMO - 头皮发麻” (@bestzumo), 498 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/bestzumo.

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.