Telegram RegisterThe public register of Telegram
Telegram profile photo for tg引流|私信代发|群发私信|tg引流

Channel

tg引流|私信代发|群发私信|tg引流

@zesendaifa

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

6,483subscribers

-1,683 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002559784380
TypeChannel
Username@zesendaifa
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live5 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/zesendaifa

Growth

6,4838,1667,324.511 August 2026 — 8,166 subscribers11 August 2026 — 8,166 subscribers11 August 2026 — 8,157 subscribers15 August 2026 — 7,851 subscribers17 August 2026 — 7,401 subscribers20 August 2026 — 7,211 subscribers24 August 2026 — 7,174 subscribers27 August 2026 — 7,062 subscribers29 August 2026 — 6,904 subscribers1 September 2026 — 6,738 subscribers5 September 2026 — 6,483 subscribers11 August 20265 September 2026
11 measurements spanning 25 days, net -1,683. 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 6,231–8,418 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 20:186,483-255
1 Sept 2026, 16:356,738-166
29 Aug 2026, 16:166,904-158
27 Aug 2026, 00:077,062-112
24 Aug 2026, 05:187,174-37
20 Aug 2026, 18:157,211-190
17 Aug 2026, 20:387,401-450
15 Aug 2026, 05:477,851-306
11 Aug 2026, 17:428,157-9
11 Aug 2026, 15:008,166no change
11 Aug 2026, 14:518,166first reading

Engagement

18 posts held, back to 19 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 6 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.23%
avg views ÷ 6,483 subscribers
Avg views / post
210
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 18 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 18 August 2026
Posts held18 (19 June 202618 August 2026)
Views total838
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 11:25 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

4 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
375.0%
😁125.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 3 of the 18 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

18 Aug 2026, 15:19 UTC194 viewsread 20 August 2026

50u出公开群 质量群发链接 刚洗完的 用了好多双向号洗出来的 3万左右链接公开

18 Aug 2026, 15:18 UTC18 viewsread 20 August 2026

https://t.me/usdt_king https://t.me/KK5868998 https://t.me/xianyu01 https://t.me/qihang666 https://t.me/lgyuho https://t.me/Sygj8888 https://t.me/q274914398 https://t.me/sfgs63 https://t.me/wsjt8886 https://t.me/chuhai168998 https://t.me/fx2_usdt https://t.me/STKJ90325 https://t.me/danbao58group https://t.me/fw988 https://t.me/chuhairm https://t.me/xiaoz1954 https://t.me/awbotts https://t.me/FulyJRB https://t.me/qing

13 Aug 2026, 04:44 UTC551 viewsread 20 August 2026

50u出 公开群 质量群发链接 刚洗完的 3万左右 代客户出售刚开两个小时的全功能群发卡 180u 联系 @zesenyinliu

2 Aug 2026, 04:12 UTC155 viewsread 20 August 2026
Photo

永久部署 tg访客机器人 可连接多个bot @zesenyinliu

2 Aug 2026, 04:08 UTC248 viewsread 20 August 2026
Photo

一键模仿id 自动发送关键词 霸屏 模仿id 全局关键词 永久部署仅需 588u 接任何机器人 脚本定制 @zesenyinliu

15 Jul 2026, 13:28 UTC165 views3 reactionsread 20 August 2026
Photo

号没死 不仅重发一遍 而且还赠送群发广告🪧

2😁1

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

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

Names

Channels on the register whose handles appear in this channel's posts.

【AFUN集团】出海大群
@afunCH88 · 36,746
1 post
全网需求线索商机-橙子出海
@c69966 · 15,396
1 post
成都老马 专业出海项目群
@chengdulaoma520 · 5,607
1 post
🎖🎖🎖灰产-粉商-外汇-Mt5-合约-交易所-商城-数据-搭建-出海项目交流群
@chuhai168998 · 23,667
1 post
九州联盟|出海交流
@cn_svip8 · 5,585
1 post
小飞侠出海资源交流群
@dsfsdfsdf58 · 42,041
1 post
舵手联盟出海
@dslm888 · 34,262
1 post
二哥【出海社群】
@egsq8 · 12,085
1 post
法拉利海外项目资源交流群|法拉利出海
@falalichuhai · 14,400
1 post
东南亚吃瓜日记/出海必看
@fsfdserr · 16,031
1 post
风行OTC/usdt承兑担保交易
@FX2_usdt · 11,806
1 post
【华人出海】东南亚社区
@HA88668866 · 88,762
1 post
想出海 走四方 四方担保出海-交流群
@haidun_1 · 8,768
1 post
全网出海需求-海华出海@HHCH
@haihuachaxun · 29,425
1 post
出海TG讨论组
@haiwaioscom · 5,042
1 post
海王出海-SCRM-官方客服【请添加我为联系人】
@HaiWangApap · 5,515
1 post
【出海/资源/项目】
@haizyuanxm · 17,039
1 post
浩鲸出海🐳出海项目交流群
@haojing168 · 20,676
1 post
华宏汇出海🌈资源整合交流社群
@hhhch · 84,535
1 post
【江湖】出海资源群
@JHCH01 · 9,642
1 post
金手指出海 - 出海联盟
@jinshouzhichuhai · 90,443
1 post
全网需求商机群-金手指出海
@jinshouzhixuqiu · 31,247
1 post
❤️深圳爱情交易
@lgyuho · 26,076
1 post
东南亚出海⚜️(业务交流共享解答)🅥
@yy188 · 36,499
1 post

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

“tg引流|私信代发|群发私信|tg引流” (@zesendaifa), 6,483 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/zesendaifa.

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.