Telegram RegisterThe public register of Telegram

Channel

然后机器人频道

@ranhouyewu

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

1,274subscribers

+1 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1004496426061
TypeChannel
Username@ranhouyewu
CreatedBetween 1 June 2026 and 24 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/ranhouyewu

Growth

1,2731,2741,273.511 Aug 2026, 23:47 — 1,273 subscribers12 Aug 2026, 00:00 — 1,273 subscribers12 Aug 2026, 22:54 — 1,274 subscribers11 Aug 2026, 23:4712 Aug 2026, 22:54
3 measurements taken within a single day, net +1. 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 1,273–1,274 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:541,274+1
12 Aug 2026, 00:001,273no change
11 Aug 2026, 23:471,273first reading

Engagement

20 posts held, back to 24 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
40.7%
avg views ÷ 1,274 subscribers
Avg views / post
518
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held20 (24 July 202611 August 2026)
Views total10,368
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 00:00 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

11 Aug 2026, 16:31 UTC58 viewsread 12 August 2026

📢通知: 广东地区神父恢复 😃😀 回单时间不具体 得看源头什么时候在 可能晚上也可能秒 中途可以撤单 急的话可以来做广东拼接个户 相差了个有效期 都是公网!!!

Signed 然后 春江2017

10 Aug 2026, 09:32 UTC260 viewsread 12 August 2026

大量收广东政务网个人账号 不会注册的 可以找我拿链接注册 秒结账 有账号的直接来变现 有多少要多少

Signed 然后 春江2017

10 Aug 2026, 09:00 UTC269 viewsread 12 August 2026

河南个户: 头加公网实时地址 😀😀 量大客户,同行代理来找我拿代理价 给优势价 一手源头出单 百分百公网 假一赔十 随便埋雷

Signed 然后 春江2017

9 Aug 2026, 15:43 UTC297 viewsread 12 August 2026

📢通知: 新增河南神父😃😀 河南个户😀😀 量大客户,同行代理来找我拿代理价 给优势价 一手源头出单

Signed 然后 春江2017

8 Aug 2026, 19:48 UTC325 viewsread 12 August 2026

📢通知: 新增湖南实时公网户籍地 😃😀 绝对的公网 湖南神父空了的可以拿这个出拼接 跟真地址一样的效果 担心湖南神父上面的不是实时公网的 可以来出这个 同行来拿代理价 量大给最优势价

Signed 然后 春江2017

8 Aug 2026, 06:51 UTC346 viewsread 12 August 2026

📢通知: 全国文全市场上调 以下地区文全一律 😃😀 河北,江苏,浙江,安徽,山东,湖北,湖南,广东,广西,甘肃 非市场上社工库数据出单,都是接口出单,另外跟全国一样,不是无遗漏的,可以指定出人

Signed 然后 春江2017

7 Aug 2026, 15:39 UTC348 viewsread 12 August 2026

📢通知: 广东公网户籍地恢复 😃😀 保实时公网,同行来拿代理价 量大给最优势价

Signed 然后 春江2017

6 Aug 2026, 15:49 UTC394 viewsread 12 August 2026

📢通知: 重庆地区神父恢复 😀😀 和之前重庆板子一样 重庆是名下 想要神父之外的东西 单独来问我 全天都能出 速度更快 绝对公网 量大客户 同行代理可以来拿价了

Signed 然后 春江2017

3 Aug 2026, 14:36 UTC537 viewsread 12 August 2026

📢通知: 新增上海公网户籍地 2️⃣🔤 保公网,同行来拿代理价 量大给最优势价

Signed 然后

2 Aug 2026, 08:20 UTC562 viewsread 12 August 2026

📢通知: 山东神父现在只有早八晚十线 除了这个时间段外的期间 不用来丢了 全天线已经死了 价格不变依然是3u 代理单量大的客户可以来拿价格了

Signed 然后

1 Aug 2026, 05:46 UTC547 viewsread 12 August 2026

因为建频道号掉了 老神父模板频道掉了 地区神父模板新频道→ @diqutoumoban

Signed 然后

29 Jul 2026, 15:31 UTC678 viewsread 12 August 2026

📢通知: 安徽,浙江,甘肃 这三个地区神父的板子已更新到 地区神父展示频道→ @diqutoumoban 自行查看各个地区模板

Signed 然后

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

Citation-graph rank

Citation-graph rank — 284,032 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 3 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“然后机器人频道” (@ranhouyewu), 1,274 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ranhouyewu.

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.