Telegram RegisterThe public register of Telegram
Telegram profile photo for 爱在西元前

Channel

爱在西元前

@Rnxb517

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

2,766subscribers

-118 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002256094962
TypeChannel
Username@Rnxb517
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/Rnxb517

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

2,7662,8842,8258 August 2026 — 2,884 subscribers8 August 2026 — 2,880 subscribers11 August 2026 — 2,864 subscribers14 August 2026 — 2,854 subscribers17 August 2026 — 2,845 subscribers20 August 2026 — 2,833 subscribers24 August 2026 — 2,830 subscribers27 August 2026 — 2,827 subscribers30 August 2026 — 2,812 subscribers2 September 2026 — 2,796 subscribers6 September 2026 — 2,788 subscribers11 September 2026 — 2,775 subscribers14 September 2026 — 2,768 subscribers18 September 2026 — 2,766 subscribers8 August 202618 September 2026
14 measurements spanning 41 days, net -118. 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 2,748–2,902 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 03:002,766-2
14 Sept 2026, 06:212,768-7
11 Sept 2026, 00:192,775-13
6 Sept 2026, 09:582,788-8
2 Sept 2026, 10:112,796-16
30 Aug 2026, 13:562,812-15
27 Aug 2026, 16:282,827-3
24 Aug 2026, 09:532,830-3
20 Aug 2026, 19:242,833-12
17 Aug 2026, 12:352,845-9
14 Aug 2026, 11:182,854-10
11 Aug 2026, 01:532,864-16
8 Aug 2026, 06:532,880-4
8 Aug 2026, 01:312,884first reading

Engagement

13 posts held, back to 28 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 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 13 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 13 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 28 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, 00:25 UTC7 viewsread 8 August 2026
Photo

破解支百脱库/大众名字通杀 @yixinlu

Signed 一心路 @yixinlu

7 Aug 2026, 02:57 UTC69 viewsread 8 August 2026

破解卡反 😀😀 😀😀 剩菜卡反 😃😀 😃😀 无视大众名/地区 @yixinlu

Signed 一心路 @yixinlu

6 Aug 2026, 04:04 UTC145 viewsread 8 August 2026

支百 😀😃😀 老线回归概率带户籍地 支付宝上传证件照概率出户籍地 下午四点前报当天回 联系:@yixinlu 专吃剩菜 公网补齐空 破解支空等等都来‼️

Signed 一心路 春江5418

5 Aug 2026, 04:42 UTC144 viewsread 8 August 2026
Photo

民政婚姻 带婚史 稳定不翻车 @yixinlu

Signed 一心路 春江5418

2 Aug 2026, 06:52 UTC236 views1 reactionsread 8 August 2026
Photo

文字全户😀😃😀‼️‼️ 文字全户😀😃😀‼️‼️ 排队秒 @yixinlu😀

1

Signed 一心路 春江5418

1 Aug 2026, 07:25 UTC154 views0 reactionsread 8 August 2026
Photo

Photo, posted without a caption

Signed 一心路 春江5418

31 Jul 2026, 01:09 UTC188 viewsread 8 August 2026
Photo

民政婚姻 😃😀‼️ 民政婚姻 😃😀‼️ 节假日不停机 主打稳定😀 @yixinlu

Signed 一心路 春江5418

29 Jul 2026, 07:46 UTC208 viewsread 8 August 2026
Photo

破解支百/破解电百/剩菜机主 一直在秒 @yixinlu

Signed 一心路 春江5418

29 Jul 2026, 04:52 UTC297 viewsread 8 August 2026

支机/机主终点站 破解电百😃😀 剩菜机主😃😀 破解支百😀😃😀 真支百/公网机主前的最后一道防线 @yixinlu

Signed 一心路 春江5418

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“爱在西元前” (@Rnxb517), 2,766 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Rnxb517.

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.