Telegram RegisterThe public register of Telegram
Telegram profile photo for Luckly☕️幸运九色鹿🍀

Channel

Luckly☕️幸运九色鹿🍀

@xingyunhua

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

122subscribers

+5 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002551205079
TypeChannel
Username@xingyunhua
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live17 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/xingyunhua

Growth

117122119.59 August 2026 — 117 subscribers10 August 2026 — 117 subscribers17 August 2026 — 122 subscribers9 August 202617 August 2026
3 measurements spanning 8 days, net +5. 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 116–123 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 16:28122+5
10 Aug 2026, 04:34117no change
9 Aug 2026, 09:16117first reading

Engagement

20 posts held, back to 6 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
150.0%
avg views ÷ 122 subscribers
Avg views / post
183
13 posts measured
Reaction rate
0.568%
reactions ÷ views · ER floor
Posts in window
13
of 20 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 2 of 13 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 8 August 2026
Posts held20 (6 July 20268 August 2026)
Views total2,379
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 09:16 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.0%

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 2 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 1reactions 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 6 July 2026 to 8 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

8 Aug 2026, 04:23 UTC212 viewsread 9 August 2026
Photo

此版本全头全户 🥰🥰🥰 源头收 有量来 当天下午17:00前报当天回 晚报隔天 非真刑侦 介意勿报

31 Jul 2026, 14:16 UTC63 viewsread 9 August 2026

月底啦 各位同行客户们 合作是缘 体谅一下 我现在一天打三份工 收到地址的 不分大小帐都清一下 谢谢 等我以后考研考公来当内鬼

31 Jul 2026, 04:10 UTC105 views1 reactionsread 9 August 2026

北京房产 首套 🥰🥰🥰第二套往后🥰🥰🥰 【空收🥰🥰🥰】 报单提供:大头+姓名+身份证号 当天回,等不了可以+15u秒单 同行代理可以拿价

1

30 Jul 2026, 19:34 UTC160 viewsread 9 August 2026

寻找能出移动机主(无盲移动)的渠道 预算充足 能出联系我 @RX663 一直有量 直接包养 不要历史机主

30 Jul 2026, 13:46 UTC571 viewsread 9 August 2026

出入境记录 🥰🥰 全天😎 全头全户22u 源头收 非真刑侦 当天下午17:00前报当天回 晚报隔天 有量代理利润给足 批量百单工商法人0.5u起 人在就秒 小批量1.5u 100出99 包0错单

30 Jul 2026, 10:20 UTC174 viewsread 9 August 2026

单头/全头全户🥰🥰🥰/🥰🥰🥰当天15:30报当天回 支百【港澳台/邮箱/大众】 🥰🥰🥰 出入境记录 🥰🥰全天秒 出入境记录 🥰🥰全天秒 出入境记录 🥰🥰全天秒 机主 🥰🥰 支码反 限制码反 百分百码反 非库补 按市场价格吧 我也不知道多少 全国文全🥰🥰公网补齐/猎魔 🥰🥰 全国文全🥰🥰公网补齐/猎魔 🥰🥰 卡反身份证 散🥰🥰 卡反预留手机号散🥰🥰脱🥰🥰批0.xu 公司名下卡 🥰🥰🥰对公账户 非税务局 可排除 不用法人大头报 排除+🥰🥰🥰税务局空了的也可以 税务局空了的也可以 【税务局全业务】同行代理带刀砍价 【税务局全业务】同行代理带刀砍价 公网网逃 🥰🥰🥰不带撤销 公网网逃 🥰🥰🥰带撤销 出全部案件 公网网逃 🥰🥰🥰带简要案情+同案人 12306强登 🥰🥰 国政名下证 🥰🥰 美团后台地址🥰🥰🥰一年半内地址 保时间 不保时间的🥰🥰🥰

29 Jul 2026, 11:03 UTC126 viewsread 9 August 2026

单头/全头全户🥰🥰🥰/🥰🥰🥰【非刑侦】不包实时数据 当天15:30报当天回 支百【港澳台/邮箱/大众都可以】 🥰🥰🥰 破解微反🥰🥰🥰 通杀 包过验证 银行卡反身份证号 🥰🥰 概率给预留 银行卡反预留手机号🥰🥰 脱🥰🥰 公司名下卡 🥰🥰🥰 对公账户 可排除 不用法人大头报单 破解公司名下卡 🥰🥰🥰 对公账户 自带法人大头报 保真不包漏 【税务局全业务】同行带刀砍价 公网网逃🥰🥰🥰不带撤销 公网网逃🥰🥰🥰带撤销 出全部案件 公网网逃🥰🥰🥰带简要案情+同案人 出入境记录 🥰🥰😎 带名下护照 12306强登 🥰🥰😎 带大头三要素报 国政名下证 🥰🥰😎 带大头报 美团后台地址 P图版 🥰🥰🥰 一年半内地址 保时间 一条也收费 不保时间的 🥰🥰🥰 一条也收费

28 Jul 2026, 19:45 UTC62 viewsread 9 August 2026

介绍:谁可以做移动无盲的 只有姓氏 不清楚名字几个字 需求:出现任机主 不要历史 价格:20-35u一个 保量 时间:尽量两天内出 1-3天回单 联系:@RX663 这条信息为需方信息 是我需要有人做 不是我做!!!

28 Jul 2026, 12:39 UTC196 viewsread 9 August 2026

公司名下卡 30U 对公账户 可排除 包漏 不用法人大头报单 税务局对公账户20u 自带法人大头报 保真不包漏

26 Jul 2026, 15:34 UTC268 viewsread 9 August 2026

出入境记录 🥰🥰 😎 12306强登 🥰🥰😎 国政名下证 🥰🥰😎 电子营业执照 🥰🥰😎 单头全户 🥰🥰🥰

25 Jul 2026, 17:40 UTC300 viewsread 9 August 2026

单头全户😀😀😃😀😀 单头板子如图 全头15u(私我看板子) 下午3点前报当天回!不翻车! 非真刑侦全户 介意勿报

Showing the 12 most recent of 20 posts we hold for @xingyunhua. 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 — 968,706 of 1,549,376entries 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 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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“Luckly☕️幸运九色鹿🍀” (@xingyunhua), 122 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/xingyunhua.

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.