Telegram RegisterThe public register of Telegram

Channel

云南牛马客栈 ·红牌楼

@NMHp01

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

11,682subscribers

+248 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-1003552762849
TypeChannel
Username@NMHp01
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/NMHp01

Growth

11,43411,68211,5587 August 2026 — 11,434 subscribers7 August 2026 — 11,434 subscribers8 August 2026 — 11,463 subscribers9 August 2026 — 11,483 subscribers10 August 2026 — 11,529 subscribers11 August 2026 — 11,578 subscribers12 August 2026 — 11,615 subscribers14 August 2026 — 11,682 subscribers7 August 202614 August 2026
8 measurements spanning 7 days, net +248. 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 11,397–11,719 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:3311,682+67
12 Aug 2026, 22:4411,615+37
11 Aug 2026, 19:3711,578+49
10 Aug 2026, 16:0511,529+46
9 Aug 2026, 14:1111,483+20
8 Aug 2026, 13:4111,463+29
7 Aug 2026, 19:0111,434no change
7 Aug 2026, 18:5111,434first reading

Engagement

11 posts held, back to 27 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 14 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
34.8%
avg views ÷ 11,682 subscribers
Avg views / post
4,060
11 posts measured
Reaction rate
0.121%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 10 of 11 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 11 August 2026
Posts held11 (27 July 202611 August 2026)
Views total44,690
Reactions total51
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 03:58 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
38s
Average length
19s

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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4894.1%
🔥23.92%
😁11.96%

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

Measured over the 11 most recent posts we hold, published 27 July 2026 to 11 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

11 Aug 2026, 13:51 UTC≈1,710 views3 reactionsread 13 August 2026
Photo

编号: #牛马·红牌楼0156号 花名: #瑶瑶 价位: #7p #13pp 服务: 见课表 特色:见课表 位置: #西山区 认证: 已视频认证 TG: @Fanqie866 工兵车评:报告1 报告2 精英车评:报告1 报告2 报告3 锐评报告: 推荐:报告1 报告2 报告3 报告4 报告5 报告6 不推荐: 出击群:https://t.me/nmyizhan

3

11 Aug 2026, 13:49 UTC≈1,770 views3 reactionsread 13 August 2026
Photo

编号: #牛马·红牌楼0155号 花名: #若曦 价位: #6p #11pp 服务: 见课表 特色:见课表 位置: #西山区 认证: 已视频认证 约课联系新账号👇 TG: @ruoximn 工兵车评: 精英车评:报告1 锐评报告: 推荐:报告1 报告2 报告3 报告4 报告5 报告6 报告7 报告8 报告9 报告10 报告11 报告12 报告13 报告14 报告15 报告16 报告17 报告18 报告19 报告20 报告21 报告22 报告23 报告24 报告25 报告26 报告27 报告28 不推荐:报告1 出击群:https://t.me/nmyizhan

3

11 Aug 2026, 13:48 UTC≈1,800 views2 reactionsread 13 August 2026
Photo

编号: #牛马·红牌楼0154号 花名: #紫霞 价位: #6p #11pp 服务: 见课表 特色:见课表 位置: #官渡区 TG: @kmzixia 工兵车评: 精英车评: 锐评报告: 推荐:报告1 报告2 报告3 报告4 报告5 报告6 报告7 报告8 报告9 报告10 不推荐: 出击群:https://t.me/nmyizhan

2

9 Aug 2026, 06:31 UTC≈2,920 views5 reactionsread 13 August 2026
Photo

编号: #牛马·红牌楼0153号 花名: #白鸽 价位: #7p #12pp 服务: 见课表 特色:见课表 位置: #盘龙区 认证: 已视频认证 TG: @baige520 工兵车评:报告1 报告2 精英车评: 锐评报告: 推荐:报告1 报告2 报告3 报告4 报告5 报告6 报告7 报告8 不推荐: 出击群:https://t.me/nmyizhan

5

4 Aug 2026, 07:51 UTC≈5,380 views10 reactionsread 13 August 2026
Photo

编号: #牛马·红牌楼0152号 花名: #岁岁 价位: #7p #13pp 服务: 见课表 特色:见课表 位置: #西山区 TG: @suisuizuikeai 精英车评:报告1 报告2 报告3 报告4 报告5 报告6 报告7 锐评报告: 推荐:报告1 报告2 报告3 报告4 报告5 报告6 报告7 报告8 报告9 不推荐: 出击群:https://t.me/nmyizhan

8🔥2

2 Aug 2026, 12:08 UTC≈4,330 views4 reactionsread 10 August 2026
Photo

编号: #牛马·红牌楼0151号 金颜坊<养身spa丝足 . 92> 官渡区,养生spa.丝足诱惑,前列腺保养,脱敏延时,龟责,丝足诱惑,spa,G点高潮,芳香疗愈!头部按摩放松!超级舒服的手法!呵护你的私密! 高质量,颜值高,服务贴心,笑容温馨,这里是家里的港湾!如果你累了,压力大了,那方面不够,感到力不心!来金颜坊! 🔥🔥🔥限时活动特惠🔥 799套餐增送小项目2前列腺高潮或者男士潮吹,选喜欢的项目降落🔥 地址:官渡区 营业时间:下午1点到晚上2点,提前预约,不排队!一客一换,一消毒,决对私密! 😊套餐带理疗,都带出水,有喜欢小项目可以加小项目!体验!如果中途出水时间没到,也会把剩下的服务做完了!大家放心约客! 小项目不单独做,需要搭配套餐用👍👍👍 预约:@jyf1618 双向群:https://t.me/jyf1618199 频道:https://t.me/jyf161819 推荐: 不推荐:

4

27 Jul 2026, 07:06 UTC≈6,530 views8 reactionsread 10 August 2026
Video

编号: #牛马·红牌楼0150号 甜甜半套木桶浴 ❤️‍🔥【莞式半全套💞海选会所】❤️‍🔥 🟣海选 🟡油压 🟠莞式 🔴全套 ❤️会所介绍 :海选模式 莞式服务, 环境豪华私密安全, 给您至尊享受的高端体验 🔥服务内容 :🅾️莞式36式 , 🛁皇帝共浴,💆菲式按摩,💪莞式抓龙, 👙制服诱惑, 👯‍♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 等三十多种项目。1. 木桶浴、泡澡、洗澡、美女全身搓背单间搓背!全身打沐浴露! 2. SPA技师服务:鼻吸、耳捂、深喉、毒龙裸顶、过水、胸推、漫游、臀推、裸推、丝足、69式,高山流水,肛门旋转,丝袜制服诱惑,足交,无套口交,最后一口咬定射妹妹嘴巴里面,所有💋的服务都是裸吹!丝袜🉑带走! 无需定金 🈚️套路(靠谱预约👉到店消费) ⏰ 服务时长: 90-120分钟 🙋‍♀️ 营业时间: 13:00-05:0

8

27 Jul 2026, 05:05 UTC≈6,480 views10 reactionsread 10 August 2026
Photo

编号: #牛马·红牌楼0150号 花名: #芷若 价位: #7p #12pp 服务: 见课表 特色: 见课表 位置: #官渡区 认证: 已视频认证 TG: @xizh6188 工兵车评: 精英车评: 锐评报告: 推荐:报告1 报告2 报告3 报告4 报告5 报告6 报告7 报告8 报告9 报告10 报告11 报告12 不推荐: 出击群:https://t.me/nmyizhan

10

27 Jul 2026, 05:02 UTC≈5,540 views4 reactionsread 10 August 2026
Photo

编号: #牛马·红牌楼0149号 花名: #苏婉婉 价位: #6p #11pp 服务: 见课表 特色:见课表 位置: #西山区 认证: 已视频认证 TG: @wdhexh 工兵车评: 精英车评:报告1 报告2 锐评报告: 推荐:报告1 报告2 报告3 报告4 报告5 报告6 报告7 报告8 报告9 不推荐: 出击群:https://t.me/nmyizhan

4

27 Jul 2026, 05:00 UTC≈5,670 views2 reactionsread 9 August 2026
Photo

编号: #牛马·红牌楼0148号 花名: #欣怡 价位: #5p #9pp 服务: 见课表 特色:见课表 位置: #西山区 认证: 已视频认证 TG: @aiuy9087 工兵车评:报告1 精英车评:报告1 锐评报告: 推荐:报告1 报告2 报告3 报告4 报告5 报告6 报告7 报告8 报告9 报告10 报告11 报告12 不推荐: 出击群:https://t.me/nmyizhan

1😁1

Showing the 11 most recent of 11 posts we hold for @NMHp01. 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 — 178,983 of 1,189,255entries 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.

Mentions

Named by 2 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.

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.

“云南牛马客栈 ·红牌楼” (@NMHp01), 11,682 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/NMHp01.

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.