Telegram RegisterThe public register of Telegram
Telegram profile photo for 红薯批发部通知群

Channel

红薯批发部通知群

@hongshu987

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

54subscribers

+6 since we began measuring on 27 August 2026

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

Register entry

Telegram ID-1002524275054
TypeChannel
Username@hongshu987
CreatedBetween 1 March 2025 and 6 May 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live7 October 2026
Measurements held5
Confirmed unchanged2 times, most recently 7 October 2026
On Telegramt.me/hongshu987

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

48545127 August 2026 — 48 subscribers28 August 2026 — 50 subscribers5 September 2026 — 51 subscribers14 September 2026 — 53 subscribers27 September 2026 — 54 subscribers27 August 202627 September 2026
5 measurements spanning 31 days, net +6. 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 47–55 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 18:1654+1
14 Sept 2026, 01:0253+2
5 Sept 2026, 06:5951+1
28 Aug 2026, 01:1650+2
27 Aug 2026, 09:1548first reading

Engagement

5 posts held, back to 6 May 2025 — 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 12 June 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.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 1 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 2 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 6 May 2025 to 12 June 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

12 Jun 2025, 21:02 UTC462 viewsread 27 August 2026

1.港新和港老补货 ➖➖➖➖➖➖➖➖ 2.针对部分客户反馈备用网站付款不跳卡密问题,目前对网站进行了调整,解决了不跳卡密问题,新的网站已经上线可以收藏保存使用。 ➖➖➖➖➖➖➖➖ 3.卡网上新了矩阵区,里面有自动化批量发布矩阵软件测试版本,一键导入ck登录比特,一键批量发布作品,同时带适配软件的ck老,有需要的客户自己去拍了测试(可以找我拿视频教程) ➖➖➖➖➖➖➖➖ 4.卡网今天消费满10元,可以找我领取10个无需vpn 美新⬇️ 自助卡网: 点击购买 客户福利: 点击查看(每人限领一次) 客户必看: 点击查看

2 Jun 2025, 08:46 UTC444 viewsread 27 August 2026

📱红薯机器人调整完毕:有转帐需求同时想省手续费的客户可以复制地址长期使用。 ➖➖➖➖➖➖➖➖➖➖ 📱将3 TRX 转账至以下指定地址后一小时内转U不需要手续费(点击复制): TMotxXQJ1LweQouc2r7xTFkGYoQcSq9Hkh ➖➖➖➖➖➖➖➖➖➖ 💹 当前价格: ├── 对方有U: 3 TRX └── 对方无U: 6 TRX ➖➖➖➖➖➖➖➖➖➖ 🎁前期推广的都是老客户,有问题随时问我,第一次使用后给我反馈还可以领取个小福利。 ➖➖➖➖➖➖➖➖➖➖ 📱关注机器人: @trxfreexhs_bot

28 May 2025, 19:06 UTC359 viewsread 27 August 2026

目前红薯机器人新增自助会员代开功能板块,可以自己开通也可以给他人代开,目前的定价是给到了代开的利润空间,给关注频道的客户提供多一条挣钱的渠道,首次自助开通前请和我沟通下细节。 📱关注机器人: @trxfreexhs_bot

7 May 2025, 02:35 UTCviews —

红薯批发部通知群 pinned «常见问题整理: 各类号售后(必看) 新号注册流程方法 发码失败解决方案 登录扫码解决方案 不出评论解决方案 拦截卡密通知频道 付款后未跳转卡密 联系:@hongshu789 打粉业务整理: 代自热业务 代截流业务 其他各类号: 千粉号 批发卡密拦截 mcn,sm千粉号,企业蓝v 三网白号带sm»

6 May 2025, 17:50 UTC436 views2 reactionsread 27 August 2026

常见问题整理: 各类号售后(必看) 新号注册流程方法 发码失败解决方案 登录扫码解决方案 不出评论解决方案 拦截卡密通知频道 付款后未跳转卡密 联系:@hongshu789 打粉业务整理: 代自热业务 代截流业务 其他各类号: 千粉号 批发卡密拦截 mcn,sm千粉号,企业蓝v 三网白号带sm

❤2

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

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

“红薯批发部通知群” (@hongshu987), 54 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/hongshu987.

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.