Telegram RegisterThe public register of Telegram
Telegram profile photo for 永华广告频道

Channel

永华广告频道

@yonghua999

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

459subscribers

+0 since we began measuring on 22 August 2026

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

Register entry

Telegram ID-1001559525516
TypeChannel
Username@yonghua999
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 August 2026
Last confirmed live30 August 2026
Measurements held2
Confirmed unchanged2 times, most recently 30 August 2026
On Telegramt.me/yonghua999

Growth

45922 Aug 2026, 06:16 — 459 subscribers22 Aug 2026, 20:26 — 459 subscribers22 Aug 2026, 06:1622 Aug 2026, 20:26
2 measurements taken within a single day. 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 458–460 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 20:26459no change
22 Aug 2026, 06:16459first reading

Engagement

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

ERR · 30 days
12.0%
avg views ÷ 459 subscribers
Avg views / post
55.3
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 August 2026
Posts held20 (22 June 202618 August 2026)
Views total221
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 06: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.

Recent posts

18 Aug 2026, 00:19 UTC22 viewsread 22 August 2026

❤ 永华支付 专业UID ❤ ❤❤❤❤❤❤❤❤❤ 😀支付宝小额扫码 300-1000 😀支付宝中额扫码 500-1000 😀支付宝大额额扫码 800-10000 寻:盘口集团 包网 大四方 担保上押 6点半早班开车超牛逼UID收量 ————————————————— ❤❤❤❤❤❤❤❤ 商务对接联系:❤@ayonghua 官方频道:https://t.me/yonghua999

14 Aug 2026, 16:15 UTC42 viewsread 22 August 2026
Photo

支付类型】 微信京东高成率版 (三角洲) 【通道编码】:801 【固定金额】: 50,100,200,300,500 通道规则:【抗投,抗并发,全层. 查单24小时 必须是bc 棋牌量! 🈲三黑🈲杀猪🈲资金盘🈲诈,发现不回款‼️ 重复支付可以补 ⚠️会员需下载京东APP(支持微信和银行卡付款) ‼️不按指定链接支付的(指定店铺➕指定账号)一律不退不补‼️ ⚠️跳转京东后,复制账号按照教程进行支付,以下特别注意!!! 1.复制账号后页面出现活动火爆无法下单,建议会员换个京东账号重新下单即可 2.复制账号后跳转微信限制无法付款,请前往京东app绑定银行卡进行支付,一次绑定便可流畅上分,一劳永逸。 3.充值账号每次都不同样,请勿重复充值一个账号,造成损失自行承 ! 纯高成率微信京东(不掺假) 成率40+ 成率风采依旧 更胜一层!!! 成率风采依旧 更胜一层!!! 全新升级 高端成率!! 最稳的微信京东 !!!!

9 Aug 2026, 03:13 UTC80 viewsread 22 August 2026

【 通道】:😋 超级商家码固额 【编码】:8⃣8⃣8⃣ 【固额】:5⃣0⃣0⃣ 【成率】:❤️8⃣0⃣+❤️ 【状态】:正常开启🌈🌈🌈 【规则】:抗投诉、,❤️只接优质客户❤️ 通道统一规则‼️:只接正规博彩,棋牌。 通道规则】:🈲三黑,🈲电闸,🈲杀猪,🈲资金盘,🈲大头贴一旦发现一律不退不补赔付,禁止后期扯皮。如发现司法冻结,1:1赔付,不扯皮 ,引导会员不要重复支付,修改金额!不补不退(重复支付,修改金额会尽量配合追回!请勿选择转账待到账24小时到账,如追不回不补不退!!)⚠️请注意查单24小时内有效。】有投诉老板帮忙联系一下配合撤诉谢谢! 🈲涮单🈲空单 发现立即处理一下 ❤️通道成率70+ ‼️有老板玩的来

6 Jul 2026, 03:44 UTC150 views0 reactionsread 22 August 2026

❤ 永华支付 专业UID ❤ ❤❤❤❤❤❤❤❤❤ 😀支付宝小额扫码 300-1000 😀支付宝中额扫码 500-1000 😀支付宝大额额扫码 800-10000 寻:盘口集团 包网 大四方 担保上押 6点半早班开车超牛逼UID收量 ————————————————— ❤❤❤❤❤❤❤❤ 商务对接联系:❤@ayonghua 官方频道:https://t.me/yonghua999

5 Jul 2026, 00:29 UTC112 viewsread 22 August 2026
Photo

所有通道码足❤️无限并发 ❤️申请加加权重 回U嘎嘎快, 回U嘎嘎快,加量上并发哦

2 Jul 2026, 02:00 UTC94 viewsread 22 August 2026
Photo

所有通道码足❤️无限并发 ‼️汇率查询请群里输入 查询通道 ❤️申请加加权重 回U嘎嘎快, 回U嘎嘎快,加量上并发哦

2 Jul 2026, 00:47 UTC70 viewsread 22 August 2026
Photo

所有通道码足❤️无限并发 ‼️汇率查询请群里输入 查询通道 ❤️申请加加权重 回U嘎嘎快, 回U嘎嘎快,加量上并发哦

1 Jul 2026, 04:17 UTC61 viewsread 22 August 2026
Photo

所有通道码足❤️无限并发 ‼️汇率查询请群里输入 查询通道 ❤️申请加加权重 回U嘎嘎快, 回U嘎嘎快,加量上并发哦

1 Jul 2026, 03:17 UTC51 viewsread 22 August 2026
Photo

所有通道码足❤️无限并发 ‼️汇率查询请群里输入 查询通道 ❤️申请加加权重 回U嘎嘎快, 回U嘎嘎快,加量上并发哦

30 Jun 2026, 04:05 UTC44 viewsread 22 August 2026
Photo

所有通道码足❤️无限并发 ❤️申请加加权重 回U嘎嘎快, 回U嘎嘎快,加量上并发哦

26 Jun 2026, 03:37 UTC48 viewsread 22 August 2026
Photo

所有通道码足❤️无限并发 ‼️汇率查询请群里输入 查询通道 ❤️申请加加权重 回U嘎嘎快, 回U嘎嘎快,加量上并发哦

Showing the 12 most recent of 20 posts we hold for @yonghua999. 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 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 22 August 2026 — this entry's latest reading, not the date you are reading this.

“永华广告频道” (@yonghua999), 459 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/yonghua999.

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.