Telegram RegisterThe public register of Telegram

Channel

用户名 租售 @yhmZS

@yhmzs

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

383subscribers

+1 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001808695528
TypeChannel
Username@yhmzs
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/yhmzs

Growth

382383382.511 Aug 2026, 08:48 — 382 subscribers11 Aug 2026, 19:24 — 383 subscribers11 Aug 2026, 08:4811 Aug 2026, 19:24
2 measurements taken within a single day, net +1. 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 382–383 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 19:24383+1
11 Aug 2026, 08:48382first reading

Engagement

20 posts held, back to 4 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 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 20 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

8 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 62.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
562.5%
👎225.0%
💔112.5%

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

Measured over the 20 most recent posts we hold, published 4 November 2025 to 3 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

3 Jul 2026, 09:49 UTC940 viewsread 11 August 2026

🎁🎁入手 @miaopan 秒盘 @niaonv 鸟女 @cunjiao 村娇 @zanhou 赞侯 @kuaihai 快嗨 @zhuanbo 转播 搜用户名 导航点这里 #多用户名 #nft用户名 #id

22 Jun 2026, 13:20 UTC≈1,350 viewsread 11 August 2026

🎁🎁入手 @nenshu 嫩叔 @qq008 @naichong 奶虫 @zhenhuo 真货 @svip756 @kf516 @kf868 客服 @zx321 最新、在线、资讯、咨询 #用户名 #买用户名 #双用户名

13 Mar 2026, 14:02 UTC≈3,470 views1 reactionsread 11 August 2026

截至今日 上链🆔破1000个 感恩回馈老用户 推出特价⚜️⚜️ 💎💎 特价区 消费🈵100u以上 +🎁🎁送波场靓号 +多签教程 #同时 #用户名 #nft 👍导航🔥🚩🚩🚩🚩🚩🚩🚩🚩

1

31 Dec 2025, 12:34 UTC≈4,260 viewsread 11 August 2026

juege 绝哥 dacang 大仓 已出 @ninbei 您北 闽 @nvjun 女君 君王 @zhouxiu 周秀 @guanhe 关何 @niugui 牛贵 @gaofumei 高富美 @niucun 牛村 @tianqun 天群 @tuhaogege 富豪哥哥 #双拼 #nft #nft用户名

28 Nov 2025, 14:08 UTC≈4,660 views1 reactionsread 11 August 2026

🎁🎁入手 @leihun 雷魂 @luruo 陆若 @jingpan 京盘 @tebiao 特彪 #同时 #用户名 #又名 🎁

💔1

19 Nov 2025, 10:30 UTC≈4,050 views0 reactionsread 11 August 2026

👍导航🔥🚩🚩🚩🚩🚩🚩🚩🚩

19 Nov 2025, 10:29 UTC≈3,560 viewsread 11 August 2026

🎁上链 需谈价 @leizha 雷炸 @zhufuwo 祝福我 @baoyouta 保佑他 @fantiantiao 犯天条 @wubainian 五百年 @hundredold 百岁 @xinxiaomei 新小妹 @zaishaonian 再少年 @xinpen 新盆 @moupu 某朴 @rutian 如天 @kuangzai 狂仔 @zheman 遮瞒 @nvlin 女林 @erdiao 二屌 @cuopo 厝婆 @zhacang 炸仓 @miesu 灭俗 @zhangwa 张娃 @ww_000 @ee_555 @eefzr 负责人 @svipquan svip圈 @uuvip4 @uuvipp #同时 #用户名 #又名 🎁

19 Nov 2025, 10:26 UTC≈2,620 viewsread 11 August 2026

市面新出一种不能上链的用户名 买频道/群的用户名🉐注意了

18 Nov 2025, 02:42 UTC≈2,560 views3 reactionsread 11 August 2026

@tekui 特亏 @shuanpu 栓普 @niugui 牛鬼 牛贵 @penshou 喷手 @xunpu 寻朴 @jiaojue 叫绝 @meibumei 美不美 @erhang 二行🥩 🎁上链 需谈价 #同时 #用户名 #又名 🎁

👎21

16 Nov 2025, 12:42 UTC≈2,370 viewsread 11 August 2026

@u4pay @rundong 润东 @shuaihai 帅孩 @vv200 @dhaha D哈哈 🎁上链 需谈价 #同时 #用户名 #又名 🎁

11 Nov 2025, 09:41 UTC≈2,150 viewsread 11 August 2026

@iiggtt @jjkkvv 🎁上链 期间19t/个 #同时 #用户名 #又名 🎁

8 Nov 2025, 03:06 UTC≈2,080 viewsread 11 August 2026

@luanlao 銮老 @tianqun 天群 @xianniu 仙牛 🎁上链 需谈价 #同时 #用户名 #又名 🎁

Showing the 12 most recent of 20 posts we hold for @yhmzs. 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 — 8,856 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.

Mentions

Named by 42 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“用户名 租售 @yhmZS” (@yhmzs), 383 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/yhmzs.

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.