Telegram RegisterThe public register of Telegram
Telegram profile photo for 然后业务频道

Channel

然后业务频道

@ranhoupingdao

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

12,718subscribers

-2,294 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003744564700
TypeChannel
Username@ranhoupingdao
CreatedBetween 1 February 2026 and 1 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live19 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/ranhoupingdao

Topic

Hacking & security — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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

12,71815,01313,865.514 August 2026 — 15,012 subscribers15 August 2026 — 15,013 subscribers16 August 2026 — 15,010 subscribers17 August 2026 — 15,009 subscribers18 August 2026 — 15,011 subscribers19 August 2026 — 14,986 subscribers20 August 2026 — 14,922 subscribers21 August 2026 — 14,893 subscribers23 August 2026 — 14,823 subscribers24 August 2026 — 14,745 subscribers25 August 2026 — 14,706 subscribers26 August 2026 — 14,563 subscribers27 August 2026 — 14,539 subscribers28 August 2026 — 14,455 subscribers29 August 2026 — 14,316 subscribers30 August 2026 — 14,247 subscribers31 August 2026 — 14,194 subscribers1 September 2026 — 14,109 subscribers2 September 2026 — 14,036 subscribers3 September 2026 — 13,945 subscribers5 September 2026 — 13,734 subscribers9 September 2026 — 13,515 subscribers11 September 2026 — 13,313 subscribers13 September 2026 — 13,166 subscribers15 September 2026 — 13,054 subscribers17 September 2026 — 12,934 subscribers19 September 2026 — 12,718 subscribers14 August 202619 September 2026
27 measurements spanning 36 days, net -2,294. 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 12,374–15,357 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
19 Sept 2026, 16:2112,718-216
17 Sept 2026, 06:5912,934-120
15 Sept 2026, 08:5713,054-112
13 Sept 2026, 17:2113,166-147
11 Sept 2026, 20:3813,313-202
9 Sept 2026, 07:3813,515-219
5 Sept 2026, 20:3913,734-211
3 Sept 2026, 17:5513,945-91
2 Sept 2026, 11:3614,036-73
1 Sept 2026, 14:4714,109-85
31 Aug 2026, 17:1314,194-53
30 Aug 2026, 17:4414,247-69
29 Aug 2026, 19:0614,316-139
28 Aug 2026, 16:3314,455-84
27 Aug 2026, 17:4914,539-24
26 Aug 2026, 19:2314,563-143
25 Aug 2026, 20:0714,706-39
24 Aug 2026, 23:0614,745-78
23 Aug 2026, 06:1314,823-70
21 Aug 2026, 20:0714,893first reading

Engagement

19 posts held, back to 1 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 35 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 19 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, 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 2 of the 19 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 19 most recent posts we hold, published 1 July 2026 to 8 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.

Recent posts

8 Aug 2026, 20:04 UTC537 viewsread 2 September 2026

文全,补齐,猎魔 已跟随市场调价 已编辑

20 Jul 2026, 12:56 UTC≈1,300 views1 reactionsread 2 September 2026

寻找 需要文全/公网补齐/猎魔 量大代理客户 公网补齐 😀😃😀 排队秒 公网猎魔 😀😃😀 排队秒 可以排除 无视脱裤菜 保真不保漏 确认好再报 百分百的公网 全国文全 😀😃😀 排队秒 保真不保漏 集体户默认空会通知 要的话再出 报过的客户都说准 文全地址 😃😀 全天秒 非社工库出单 文全库出单 不是公网实时 报了不扯皮谢谢 然后永久用户名: @ran_hou

1

20 Jul 2026, 12:44 UTC993 viewsread 2 September 2026

@rennn 不再使用这个用户名 已被朋友高价收走 后面会重新购买新的用户名 现在用户名: @ran_hou 不要被骗了

12 Jul 2026, 17:55 UTC≈1,320 viewsread 2 September 2026

假地址机器人: @diguazhbot 代理量大老板可以来拿优势价格 😀😀一单 早七点半到晚七点半随时秒 需要的可以联系充值客服: @ran_hou 机器人频道: @ranhouyewu

8 Jul 2026, 15:18 UTC≈1,920 views1 reactionsread 2 September 2026

全网最全地区头: 12天津2️⃣🔤 13河北1️⃣🔤 32江苏1️⃣🔤 33浙江 4️⃣🔤 34安徽 4️⃣🔤 36江西4️⃣🔤 37山东3️⃣🔤 41河南4️⃣🔤 42湖北2️⃣🔤 43湖南1️⃣🔤 44广东4️⃣🔤 45广西1️⃣🔤 46海南1️⃣🔤 50重庆3️⃣🔤 52贵州3️⃣🔤 62甘肃4️⃣🔤 63青海1️⃣🔤 64宁夏1️⃣🔤 65新疆2️⃣🔤 地区户籍地: 11北京2️⃣🔤 34安徽 2️⃣🔤 50/51重庆2️⃣🔤 44广东2️⃣🔤 43湖南 2️⃣🔤 62甘肃 2️⃣🔤 31上海 2️⃣🔤 35 福建2️⃣🔤 33浙江2️⃣🔤 地区头机器人: @ranhoudqt_bot 客服: @ran_hou 双向机器人: @ranhousxbot

1

5 Jul 2026, 23:55 UTC≈1,110 viewsread 2 September 2026

假地址 😀😀 早七点半到晚七点半 量大老板可以来拿优势价格 一直在秒 @ran_hou

1 Jul 2026, 08:41 UTC≈1,100 viewsread 2 September 2026

微支流水正常收单 微信流水不带ID /支付宝流水带ID 一月 🤩🤩🤩🤩 三月 🤩🤩🤩🤩 半年 🤩🤩🤩🤩 一年 🤩🤩🤩🤩 二年 🤩🤩🤩🤩 三年 🤩🤩🤩🤩🤩 回单:1~3个工作日 温馨提示:保真不保漏 ‼️ 不管出来多少条都按报单时间收费‼️

1 Jul 2026, 08:37 UTC659 viewsread 2 September 2026
File

强登12306 出行记录 🤩🤩🤩 报单提供 大头 @ran_hou

1 Jul 2026, 08:33 UTC551 viewsread 2 September 2026

交管12123名下车 🤩🤩🤩 报单;名字 身份证 不需大头

1 Jul 2026, 08:29 UTC538 viewsread 2 September 2026
Photo

公网水电地址反查 🤩🤩🤩 (出系统内登记 户主的信息/系统内登记的联系方式信息) 有什么出什么 保真

1 Jul 2026, 08:27 UTC573 viewsread 2 September 2026
Photo

🪱🐛🦋 邮政快递 邮政单地址;🤩🤩 邮政多地址;🤩🤩🤩 规则; 邮政多地址最多出两条 一条按单地址收

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

Posts edited after publishing

@ranhoupingdao edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
19 August 2026
Most recent edit
19 August 2026

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.

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

“然后业务频道” (@ranhoupingdao), 12,718 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ranhoupingdao.

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.