Telegram RegisterThe public register of Telegram

Channel

匿名中国

@Tor_ph

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

1,858subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1001390596323
TypeChannel
Username@Tor_ph
Created14 February 2023measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/Tor_ph

Growth

1,85814 Aug 2026, 03:50 — 1,858 subscribers14 Aug 2026, 13:34 — 1,858 subscribers14 Aug 2026, 03:5014 Aug 2026, 13:34
2 measurements taken within a single day. 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,856–1,860 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 13:341,858no change
14 Aug 2026, 03:501,858first reading

Engagement

5 posts held, back to 14 February 2023the 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.

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 3 March 2023. An engagement rate over an empty window would be a number about nothing.

Reaction mix

157 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 50.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7950.3%
5535.0%
😁127.64%
👎63.82%
👏31.91%
🥰21.27%

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 3 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 157reactions 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 14 February 2023 to 3 March 2023, 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

3 Mar 2023, 14:02 UTC≈63,400 views30 reactionsread 14 August 2026

[匿名中国] 已转让至 HatPay 官方 “现更改用户名”为 @HatPayGroup 请牢记。

14👍8😁8

15 Feb 2023, 14:25 UTC≈65,000 views32 reactionsread 14 August 2026

本频道已作废,请用户关注上述频道👆

👍188👎3👏3

15 Feb 2023, 14:24 UTCviews —

匿名中国 pinned «Hatpay官方认证👇(🌐) 1. @HatGx 供需广告 2. @HatGq 押金公群 3. @HatPayGroup 官方群组 4. @HatpayNews 官方公告 5. @HatPayBot ⚙️自助服务 [正在开发中] 👩‍💻 HatPay官方客服: @HatPayAdminBot ————————————————————— 📮 HatPay帽子官方担保 [自助导航菜单] * HatPay 帽子官方担保规则 * HatPay 帽子官方内部老板群 * HatPay 担保如何收费及公群须知…»

15 Feb 2023, 14:24 UTC≈63,500 views95 reactionsread 14 August 2026
Forwarded from @HatPayNews

Hatpay官方认证👇(🌐) 1. @HatGx 供需广告 2. @HatGq 押金公群 3. @HatPayGroup 官方群组 4. @HatpayNews 官方公告 5. @HatPayBot ⚙️自助服务 [正在开发中] 👩‍💻 HatPay官方客服: @HatPayAdminBot ————————————————————— 📮 HatPay帽子官方担保 [自助导航菜单] * HatPay 帽子官方担保规则 * HatPay 帽子官方内部老板群 * HatPay 担保如何收费及公群须知 * 机器人可消费商户公群及详细介绍 * 使用 @HatPayBot 自助发布广告教程 * 使用 @HatPayBot 进行简单担保服务 [无手续费] 目前部分功能正在开发中,开群上押/供需发布/业务咨询/投诉建议请联系官方客服。 [更新于2023.2.15]

👍5333😁4👎3🥰2

Showing the 5 most recent of 5 posts we hold for @Tor_ph. 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,442,942 of 1,480,688entries 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.

“匿名中国” (@Tor_ph), 1,858 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Tor_ph.

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.