Telegram RegisterThe public register of Telegram
Telegram profile photo for 蕾塞-业务通知

Channel

蕾塞-业务通知

@leisaichadang17

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

11,624subscribers

-57 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-1003783613052
TypeChannel
Username@leisaichadang17
Description@leisai777
CreatedBetween 1 February 2026 and 20 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/leisaichadang17

Growth

11,62411,68111,652.57 August 2026 — 11,681 subscribers7 August 2026 — 11,681 subscribers9 August 2026 — 11,675 subscribers10 August 2026 — 11,665 subscribers11 August 2026 — 11,664 subscribers12 August 2026 — 11,668 subscribers13 August 2026 — 11,664 subscribers14 August 2026 — 11,653 subscribers16 August 2026 — 11,630 subscribers17 August 2026 — 11,624 subscribers7 August 202617 August 2026
10 measurements spanning 10 days, net -57. 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,615–11,690 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 17:5711,624-6
16 Aug 2026, 14:1411,630-23
14 Aug 2026, 18:4811,653-11
13 Aug 2026, 07:3711,664-4
12 Aug 2026, 06:3811,668+4
11 Aug 2026, 03:5311,664-1
10 Aug 2026, 01:0611,665-10
9 Aug 2026, 01:1311,675-6
7 Aug 2026, 19:0111,681no change
7 Aug 2026, 18:5111,681first reading

Engagement

23 posts held, back to 20 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 20 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
5.58%
avg views ÷ 11,624 subscribers
Avg views / post
649
13 posts measured
Reaction rate
0.608%
reactions ÷ views · ER floor
Posts in window
13
of 23 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 4 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 17 August 2026
Posts held23 (20 June 202617 August 2026)
Views total8,431
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Aug 2026, 20:45 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
8

Lifetime counters from Telegram’s own channel header, read 17 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

23 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 69.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1669.6%
417.4%
👎14.35%
😎14.35%
🤩14.35%

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

Measured over the 23 most recent posts we hold, published 20 June 2026 to 17 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

17 Aug 2026, 14:24 UTC32 viewsread 17 August 2026

机主2️⃣🔤、联通5️⃣🔤 新菜法人1️⃣🔤、92法人2️⃣🔤 高爆支机3️⃣🔤、高爆卡反3️⃣🔤 公网户籍地4️⃣🔤、红底婚姻6️⃣🔤 支付宝码返5️⃣🔤地区空跑全国1️⃣0️⃣🔤 移民局出入境5️⃣🔤12306强登1️⃣0️⃣🔤 全国文全1️⃣2️⃣🔤税务局业务1️⃣5️⃣🔤 公网补齐1️⃣0️⃣🔤公网猎魔1️⃣0️⃣🔤 广东房产一套1️⃣5️⃣🔤所有2️⃣5️⃣🔤 邮政单地址3️⃣🔤、多地址6️⃣🔤 五年医疗1️⃣5️⃣🔤、手机轨迹6️⃣0️⃣🔤 个人大数据报告3️⃣0️⃣🔤 凌晨2点后夜间文全7️⃣🔤 微反手机号一件套4️⃣0️⃣🔤 微反手机号身份证两件套1️⃣4️⃣0️⃣🔤 不止于地区头,报单联系 @pingfanxin 查档找蕾塞就行,一站式服务

9 Aug 2026, 03:14 UTC442 views2 reactionsread 17 August 2026

湖南地区:新增公网户籍地带民族 神父空的或担心神父上户籍地址不是实时的都可以过来试下

2

8 Aug 2026, 17:13 UTC454 viewsread 17 August 2026

新增41河南神父4️⃣🔤 纯公网、另有河南个户3️⃣🔤 @pingfanxin

29 Jul 2026, 05:18 UTC940 viewsread 17 August 2026

新增62甘肃地址2️⃣🔤甘肃神父4️⃣🔤 @pingfanxin

28 Jul 2026, 07:53 UTC967 viewsread 17 August 2026

公网微反 手机号 身份证 两件套 有车1️⃣4️⃣0️⃣🔤明天回 @pingfanxin

24 Jul 2026, 15:46 UTC≈1,200 viewsread 17 August 2026
Photo

广东省业务:港澳人也可以开头了 提供名字、H开头短位通行证id即可 开完真支百、开不了头的也来

21 Jul 2026, 16:14 UTC≈1,180 viewsread 17 August 2026
Photo

广东全业务、社保卡照收 4u、不需要大头、有效期

21 Jul 2026, 05:32 UTC≈1,160 viewsread 17 August 2026

地区户籍地业务开 安徽、重庆、北京、青海、 广东、甘肃、湖南、福建 公网户籍地 😃 地区 结婚证 离婚证 🤖湖北婚姻🤖😀😀 🤖新疆婚姻🤖😀😀 🤖江苏婚姻🤖😀😀 🤖天津婚姻🤖😀😀 🤖海南婚姻🤖😀😀 🤖安徽婚姻🤖😀😀 🤖浙江婚姻🤖😀😀 湖北单页户口本 😀 江苏单页户口本 😀 浙江全户(户口本)😃 安徽全户(户口本)😃 @pingfanxin

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

Posts edited after publishing

@leisaichadang17 edited 6 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
17 August 2026

Citation-graph rank

Citation-graph rank — 1,479,316 of 1,481,306entries 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.

“蕾塞-业务通知” (@leisaichadang17), 11,624 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/leisaichadang17.

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.