Telegram RegisterThe public register of Telegram

Channel

TG规则脚本信息分享器

@MRHXPJGG

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

10,053subscribers

-18 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001105395908
TypeChannel
Username@MRHXPJGG
Created21 October 2017measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/MRHXPJGG

Growth

10,05310,07310,0636 August 2026 — 10,071 subscribers6 August 2026 — 10,071 subscribers6 August 2026 — 10,073 subscribers7 August 2026 — 10,067 subscribers8 August 2026 — 10,066 subscribers9 August 2026 — 10,062 subscribers10 August 2026 — 10,056 subscribers12 August 2026 — 10,055 subscribers14 August 2026 — 10,053 subscribers6 August 202614 August 2026
9 measurements spanning 8 days, net -18. 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 10,050–10,076 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 08:1710,053-2
12 Aug 2026, 20:5310,055-1
10 Aug 2026, 22:3510,056-6
9 Aug 2026, 23:3510,062-4
8 Aug 2026, 23:3710,066-1
7 Aug 2026, 21:2510,067-6
6 Aug 2026, 23:5710,073+2
6 Aug 2026, 02:4810,071no change
6 Aug 2026, 02:0710,071first reading

Engagement

18 posts held, back to 31 March 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
16.7%
avg views ÷ 10,053 subscribers
Avg views / post
1,680
1 post measured
Reaction rate
0.238%
reactions ÷ views · ER floor
Posts in window
1
of 18 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 23 July 2026
Posts held18 (31 March 202523 July 2026)
Views total1,680
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 05:26 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.

What this channel posts

Video runtime
11m 29s
Average length
1m 26s

Measured directly from 8 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

135 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 26.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3626.7%
🤣3425.2%
👍2216.3%
🥰1611.9%
😁107.41%
💩64.44%
🤡53.70%
🌚32.22%
👎21.48%
👏10.741%

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 18 of the 18 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 135reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 31 March 2025 to 23 July 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

23 Jul 2026, 23:36 UTC≈1,680 views4 reactionsread 13 August 2026
Forwarded from @iOS_TrollStorePhoto

❌ 乌龙工作室展示了 iOS 17.3.1 越狱录屏回复质疑 基于原版 Dopamine 越狱, 这可能是第一个完全由 AI 构建的越狱工具——0 行源代码是由人类编写的。使用 Sol 和 K3 制作。 👻 opa334 道歉并感叹 AI 如此强大 看来只要有漏洞,用 AI 完成越狱不是难事😇

4

26 Feb 2026, 18:41 UTC≈8,940 views1 reactionsread 13 August 2026

https://youtu.be/HrUNXofYAfY?si=ndIWoWeqf4MY9ZwV

1

17 Feb 2026, 07:55 UTC≈7,480 views4 reactionsread 13 August 2026
Video

艺术已成 papi酱《我想象中的春晚导演》

2👏1💩1

16 Feb 2026, 14:38 UTC≈5,530 views1 reactionsread 13 August 2026

除夕平安,祝您新年快乐!骐骥驰骋!

1

22 Dec 2025, 11:46 UTC≈7,340 views11 reactionsread 13 August 2026

2026年1月1日起,新修订的《中华人民共和国治安管理处罚法》(以下简称《治安管理处罚法》)将正式施行,其中第八十条对传播淫秽信息的处罚规定作出明确细化,对传播淫秽信息加大了处罚力度。 记者梳理了广东地区审理的多起涉网络淫秽信息传播案件,深入解读新法司法实践导向,网络涉黄无论牟利与否、场景公私,均无法律真空,新规落地将进一步填补规制空白,筑牢清朗网络环境法治防线。 微信转发淫秽信息给好友也违法,QQ群主放任成员传播“色情”也获刑 从广东地区查处的涉网络淫秽信息案件来看,传播行为的表现形式日趋多样,从传统的群内分享、私聊发送,到专业化的众筹合购、网站传播、直播牟利,覆盖了行政违法、刑事犯罪,清晰呈现了不同行为模式对应的法律后果。 以往公众存在的“私下传播淫秽信息仅属道德问题”的认知误区,新规修订明确纠正这一认知。 新《治安管理处罚法》第八十条明确将“利用信息网络、电话以及其他通讯工具传播淫秽信息”纳入治安处罚范畴,无论传播

💩5😁51

8 Jun 2025, 12:47 UTC≈19,400 views9 reactionsread 13 August 2026
Video

Video, posted without a caption

9

Showing the 12 most recent of 18 posts we hold for @MRHXPJGG. 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 — 1,241,287 of 1,345,403entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

“TG规则脚本信息分享器” (@MRHXPJGG), 10,053 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/MRHXPJGG.

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.