Telegram RegisterThe public register of Telegram

Channel

中高

@PMXKT

2 usernames

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

13,905subscribers

+102 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002113396053
TypeChannel
Usernames@PMXKT @vipt00
Description➡️ 1.5以下: @vipt001 ➡️ 1.5以上: @vipt00 ➡️ 莳花馆(大圈): @sisishihuaguan ➡️ 万事屋(S M): @BJwanshiwu ➡️ 检察院: @vipt003 ➡️ 导航群: @VIPPM888 一键关注品茗:https://t.me/addlist/ZsUMbKuQDqljZmFl
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held13
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/PMXKT

Growth

13,80313,90613,854.57 August 2026 — 13,803 subscribers7 August 2026 — 13,807 subscribers7 August 2026 — 13,808 subscribers8 August 2026 — 13,823 subscribers8 August 2026 — 13,826 subscribers9 August 2026 — 13,833 subscribers9 August 2026 — 13,857 subscribers10 August 2026 — 13,885 subscribers10 August 2026 — 13,885 subscribers11 August 2026 — 13,900 subscribers11 August 2026 — 13,906 subscribers12 August 2026 — 13,904 subscribers12 August 2026 — 13,905 subscribers13,9057 August 202612 August 2026
13 measurements spanning 5 days, net +102. 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 13,788–13,921 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 16:4313,905+1
12 Aug 2026, 11:5513,904-2
11 Aug 2026, 16:0813,906+6
11 Aug 2026, 11:2513,900+15
10 Aug 2026, 16:3613,885no change
10 Aug 2026, 10:0113,885+28
9 Aug 2026, 18:1113,857+24
9 Aug 2026, 08:5113,833+7
8 Aug 2026, 18:5613,826+3
8 Aug 2026, 10:1513,823+15
7 Aug 2026, 21:2113,808+1
7 Aug 2026, 18:4513,807+4
7 Aug 2026, 17:0213,803first reading

Engagement

31 posts held, back to 7 August 2026the 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
2.03%
avg views ÷ 13,905 subscribers
Avg views / post
282
31 posts measured
Reaction rate
0.28%
reactions ÷ views · ER floor
Posts in window
31
of 31 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. It is computed over the 16 of 31 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held31 (7 August 202612 August 2026)
Views total8,733
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 02:15 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

Photos
10,800
Videos
1,910
Links
1,690

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
3m 37s
Average length
9s

Measured directly from 24 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

13 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 46.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍646.2%
538.5%
👎215.4%

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

Measured over the 31 most recent posts we hold, published 7 August 2026 to 12 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

12 Aug 2026, 12:10 UTC426 views2 reactionsread 13 August 2026
Photo

#韩锦夕 #北京 #亚运村 #已验证 3000p ☎️ @hanjinxi 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

👍2

12 Aug 2026, 12:07 UTC434 views1 reactionsread 13 August 2026
Photo

#竹子 #北京 #百子湾 #已验证 2000p ☎️ @zhuye0006 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

👍1

12 Aug 2026, 09:44 UTC495 views0 reactionsread 13 August 2026
Photo

#白虎小乖 #北京 #东二环 #已视频验证 #白虎 #sm #嫩妹 1500p ☎️ @xg598 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

12 Aug 2026, 08:47 UTC194 viewsread 12 August 2026
Photo

#豆豆 #北京 #丰台 #已视频验证 1300p 品茗优惠➖2/联系妹子即可 ☎️ @doud688 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

12 Aug 2026, 06:12 UTC106 views1 reactionsread 12 August 2026
Photo

#万岁兔 #北京 #百子湾 #已视频验证 1800p 品茗优惠➖4/联系妹子即可 ☎️ @wantusui1800 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

1

11 Aug 2026, 07:57 UTC568 viewsread 11 August 2026
Photo

#紫琳 #北京 #大望路 #已视频验证 #一致好评 3000p ☎️ @zl1525 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

11 Aug 2026, 07:35 UTC509 viewsread 11 August 2026
Photo

#乐乐 #北京 #亚运村 #已视频验证 1500p 品茗优惠➖2/联系妹子即可 ☎️ @bjmzyy 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

11 Aug 2026, 07:28 UTC481 viewsread 11 August 2026
Photo

#小鹿鹿 #北京 #国贸 #已视频验证 2000p ☎️ @Lulu24231 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

10 Aug 2026, 14:39 UTC133 views1 reactionsread 10 August 2026
Photo

#兮兮 #北京 #三元桥 #已视频验证 1500p ☎️ @xixibao0606 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

👍1

10 Aug 2026, 06:52 UTC443 views1 reactionsread 10 August 2026
Photo

#诗诗 #北京 #望京 #已视频验证 700p起 ☎️ @shiheyuanfang11 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

👍1

10 Aug 2026, 06:49 UTC412 views1 reactionsread 10 August 2026
Photo

#羊羊 #北京 #金茂府 #已视频验证 1500p 品茗优惠➖2/联系妹子即可 ☎️ @paofuyang 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

👍1

10 Aug 2026, 05:24 UTC156 viewsread 10 August 2026
Photo

#点点 #北京 #大郊亭 #已视频验证 1300p ☎️ @Jiangxi222 联系备注:品茗 客服招财猫:@BJzhaocaimao 无法私信,看主页机器人🤖 一键导入品茗 https://t.me/addlist/ZsUMbKuQDqljZmFl

Showing the 12 most recent of 31 posts we hold for @PMXKT. 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 — 83,919 of 1,160,990entries 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 8 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

“中高” (@PMXKT), 13,905 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/PMXKT.

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.