Telegram RegisterThe public register of Telegram
Telegram profile photo for @zesendaifa

Channel

@zesendaifa

@lieyingdage

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

22subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002511711304
TypeChannel
Username@lieyingdage
Created30 April 2025measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/lieyingdage

Growth

212221.57 August 2026 — 21 subscribers11 August 2026 — 21 subscribers22 August 2026 — 22 subscribers7 August 202622 August 2026
3 measurements spanning 15 days, 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 21–22 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 23:5622+1
11 Aug 2026, 14:4621no change
7 Aug 2026, 15:5721first reading

Engagement

17 posts held, back to 30 April 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.

ERR · 30 days
13.6%
avg views ÷ 22 subscribers
Avg views / post
3.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 17 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 9 August 2026
Posts held17 (30 April 20259 August 2026)
Views total3
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 14:46 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.

Recent posts

9 Aug 2026, 12:13 UTC3 viewsread 11 August 2026

业务联系: @LC6663 我们是一家全球OTC商家,对接有盘口有大量的u归集到我们盘口,我们找用户帮我们消耗给出5%点位,目的是分散流向防止后期追溯风控

12 Jul 2026, 17:11 UTC511 viewsread 11 August 2026
Photo

百万量tg协议号库存现货 自助提货 |tg号库存百万 |直登协议批发 TG日出万量!打粉硬号!自助批发| 打粉硬号 |老号会员号批发 |全球协议直登百万库存

25 Jun 2026, 14:19 UTC≈1,990 viewsread 11 August 2026

😀😀😀😀😀😀😀😀 😀😀😀😀😀😀😀 😀😀😀😀😀😀😀 🏦😀😀😀😀😀😀😀😀😀😀 ✅🔤🔤游戏中心上压40万美金 实力保障,信誉第一,服务至上 福利不断/彩金不停/返利无上限 (每日救援金/夜宵/下午茶/周常驻/月开运/逢3活动/每日助力红包/打码送外围) 😀白马庄园上下分群:@bmzyvip 😀白马庄园导航频道:@bmzy 😀白马庄园导航网址: bmzy.com 😀白马庄园旗下公群: ⚡️😀😀😀⚡️⚡️😀😀😀😀😀😄😀😀 😀😀😀😀😀😀😀😀😀😀😀😀 😀😀😀 @bmkf @bbbm @bmmm 😀😀😀 @bmcw 😀😀😀 @bmcj

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

Mentions

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

“@zesendaifa” (@lieyingdage), 22 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/lieyingdage.

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.