Telegram RegisterThe public register of Telegram
Telegram profile photo for (检索)魔都 探花/验证/自聊/选妃/榜单/评价/报告

Channel

(检索)魔都 探花/验证/自聊/选妃/榜单/评价/报告

@thxhyl

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

7,988subscribers

+94 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002015490707
TypeChannel
Username@thxhyl
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/thxhyl

Growth

7,8907,9887,9396 August 2026 — 7,894 subscribers7 August 2026 — 7,895 subscribers10 August 2026 — 7,890 subscribers13 August 2026 — 7,901 subscribers17 August 2026 — 7,936 subscribers20 August 2026 — 7,956 subscribers24 August 2026 — 7,960 subscribers27 August 2026 — 7,958 subscribers30 August 2026 — 7,964 subscribers3 September 2026 — 7,986 subscribers8 September 2026 — 7,988 subscribers6 August 20268 September 2026
11 measurements spanning 32 days, net +94. 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 7,875–8,003 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 02:387,988+2
3 Sept 2026, 00:457,986+22
30 Aug 2026, 19:287,964+6
27 Aug 2026, 23:047,958-2
24 Aug 2026, 17:387,960+4
20 Aug 2026, 17:147,956+20
17 Aug 2026, 10:557,936+35
13 Aug 2026, 15:467,901+11
10 Aug 2026, 09:457,890-5
7 Aug 2026, 05:187,895+1
6 Aug 2026, 22:027,894first reading

Engagement

21 posts held, back to 12 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 20 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.04%
avg views ÷ 7,988 subscribers
Avg views / post
323
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 21 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 27 August 2026
Posts held21 (12 November 202527 August 2026)
Views total323
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 20:44 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.

Reaction mix

190 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 86.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
16486.3%
👍2010.5%
👎21.05%
😁21.05%
👏10.526%
😇10.526%

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

Measured over the 21 most recent posts we hold, published 12 November 2025 to 27 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

27 Aug 2026, 00:23 UTC323 viewsread 28 August 2026
Photo

— 创作者中心 · 发视频赚USDT — 将超级引擎 @CJYQ 设置成管理员可收录您的频道/群组/让您的视频内容展现在小程序曝光获得流量 👇点击按钮体验视频号MiniApp吧👇

9 May 2026, 06:58 UTC≈11,000 views5 reactionsread 28 August 2026
Photo

浦东甜酥 浦东麦麦 浦东晓晓

👍32

30 Apr 2026, 12:23 UTCviews —

(检索)魔都 探花/验证/自聊/选妃/榜单/评价/报告 pinned Deleted message

15 Apr 2026, 15:25 UTCviews —

(检索)魔都 探花/验证/自聊/选妃/榜单/评价/报告 pinned Deleted message

1 Mar 2026, 05:15 UTC≈16,600 views21 reactionsread 28 August 2026
Photo

2026-08-20 普陀芊羽 普陀可馨 静安夏清禾 2026-08-21 长宁Amanda 长宁婉茵 2026-08-22 闵行杏子 普陀雅思 2026-08-23 普陀米苏 普陀球球 2026-08-24 普陀玉米 徐汇梦娜 黄浦粉菊花 普陀百合 2026-08-25 闵行泡泡 浦东小九 浦东喵喵 2026-08-26

21

1 Mar 2026, 02:52 UTC≈14,800 views26 reactionsread 28 August 2026
Photo

🌈170cm 普陀小白 普陀大白兔 普陀娜娜 普陀北方有佳人 普陀阳阳 普陀汤圆 浦东冉冉 长宁悠米 闵行欣欣 闵行彤彤 闵行泡泡 普陀岚歆 黄埔米苏 🌈171cm 普陀樂樂 普陀苏米雪 静安小黛 杨浦徐如蓝 🌈172cm 普陀甜心 普陀百合 浦东小栗子 徐汇鹿少女 松江梦兮 🌈173cm 静安璐娜 普陀小软 徐汇雪茹 徐汇尼娜娜 🌈174cm 闵行奈倩 普陀Lucky(8P) 🌈175cm 浦东贝贝 静安小思 普陀图一 🌈 176cm 🌈 177cm 浦东露娜 🌈178cm 静安夏清禾 🌈180cm

25👍1

28 Feb 2026, 11:33 UTC≈13,500 views13 reactionsread 28 August 2026
Photo

🌈159cm 嘉定研研 浦东雯雯 🌈158cm 浦东念念 浦东麦麦 普陀久久 普陀狗头萝莉 静安朵儿 黄浦妍妍 闵行婉儿 闵行糖豆豆 🌈155cm 静安Coco 虹口范范 黄浦翠芬 🌈151cm 浦东时一 🌈150cm 浦东媛媛 浦东小不点 浦东七七

10👎2😇1

17 Feb 2026, 00:40 UTC≈13,900 views13 reactionsread 28 August 2026
Photo

普陀小白 普陀图一 普陀阳阳 普陀白若璃 普陀乐乐 普陀徐小雨 普陀小懒猫 普陀甜心 普陀玉米 黄埔翠芬 静安晚晴 静安小思 浦东小怪兽 浦东夹妃 浦东元宝 松江梦羽 闵行王锦鲤 长宁婉茵

9👍2👏1😁1

3 Feb 2026, 04:21 UTC≈24,700 views9 reactionsread 28 August 2026
Photo

棉花糖(7P) 范范(12P)

5👍4

17 Jan 2026, 06:27 UTC≈16,500 views27 reactionsread 28 August 2026
Photo

🌈 D 普陀乖乖兔 普陀雯雯 普陀噗噗 普陀茹茹 普陀奶兔 普陀陆佳瑶 普陀夏夏 普陀米苏 普陀静静 普陀大白兔 普陀甜心 普陀狗头萝莉 普陀杨悠悠 浦东钥钥 浦东小海豚 普陀Selina 浦东暮暮 浦东菲菲 浦东南宫宠妃 浦东露娜 浦东小艺 浦东萌萌 浦东小怪兽 浦东小鱼鱼 嘉定芊芊 嘉定九月 宝山米娜 宝山优乐美 宝山柠檬 闵行兰香 闵行漫漫 长宁网红花店老板娘 长宁冰冰 徐汇骚气小狂魔 徐汇美美子 徐汇雪茹 徐汇小初 徐汇钥钥 静安莎莎 虹口棉花糖 杨浦徐如蓝 奉贤晓苒 黄浦粉菊花 🌈E 普陀樂樂 普陀语萱 普陀球球 普陀小白 普陀阿紧 普陀岚歆 闵行焦糖 徐汇妮妮

26😁1

17 Jan 2026, 06:13 UTC≈15,200 views7 reactionsread 28 August 2026
Photo

静安朵儿 静安小雪 普陀岚歆 徐汇小曼 静安静静 闵行安琪 闵行漫漫 黄浦翠芬 黄浦团团 浦东小怪兽 浦东妙妙 普陀徐小雨 普陀奶兔

7

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

@thxhyl edited 6 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
8 August 2026
Most recent edit
25 August 2026

Mentions

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

“(检索)魔都 探花/验证/自聊/选妃/榜单/评价/报告” (@thxhyl), 7,988 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/thxhyl.

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.