Telegram RegisterThe public register of Telegram
Telegram profile photo for 九号代发官方频道

Channel

九号代发官方频道

@JHYLGF

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

992subscribers

-25 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-1002632097645
TypeChannel
Username@JHYLGF
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live25 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/JHYLGF

Growth

9921,0171,004.57 August 2026 — 1,017 subscribers8 August 2026 — 1,017 subscribers11 August 2026 — 1,012 subscribers15 August 2026 — 1,002 subscribers18 August 2026 — 995 subscribers25 August 2026 — 992 subscribers7 August 202625 August 2026
6 measurements spanning 17 days, net -25. 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 988–1,021 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 01:29992-3
18 Aug 2026, 08:26995-7
15 Aug 2026, 09:361,002-10
11 Aug 2026, 16:311,012-5
8 Aug 2026, 00:321,017no change
7 Aug 2026, 19:011,017first reading

Engagement

15 posts held, back to 26 May 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
58.4%
avg views ÷ 992 subscribers
Avg views / post
579
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 15 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 7 August 2026
Posts held15 (26 May 20267 August 2026)
Views total1,158
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:32 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

107 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 46.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5046.7%
💯1211.2%
1110.3%
💩1110.3%
🤝1110.3%
🤮76.54%
🔥43.74%
👎10.935%

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

Measured over the 15 most recent posts we hold, published 26 May 2026 to 7 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

7 Aug 2026, 18:42 UTC118 viewsread 8 August 2026
Photo

找我们群发私信强拉 标准配备❶日志❷客户转化比❸数据分析❹免费配备文案❺免费美工做图 群发日志=在什么时间-在哪个群-发了些什么

Signed Channel Help

5 Aug 2026, 21:51 UTC≈1,040 viewsread 8 August 2026
Photo

需要做图联系@dayel

Signed 九号·大爷 代发负责人 @dayel

27 Jul 2026, 02:07 UTC≈2,300 views33 reactionsread 8 August 2026

僵尸粉 飞机号 下单网站 jiuhao.fjapp.vip 僵尸粉低至4元!

👍312

Signed Channel Help

25 Jul 2026, 19:19 UTC≈2,310 views4 reactionsread 8 August 2026
Photo

群发私信强拉是什么? 群发:在各大群聊发送你的广告 公群 聊天群 业务群等等 私信:将你的广告精准发到有需求的人 强拉:把别人拉入你的群聊 (可以指定群采集) 群发 私信 强拉 都可接受查看日志或者随机抽查 供需10U/条赠送人工群发配备录屏一次!

💯21👍1

Signed Channel Help

19 Jul 2026, 17:46 UTC≈2,490 views21 reactionsread 8 August 2026
Photo

九号老牌精品代发 3年无黑料 🙂TG群发 🙂TG私信 🙂TG强拉 🙂TG采集 🙂TG会员 🙂TG僵尸粉 🙂TG浏览量(未来浏览量) 🙂TG各国账号 🙂星星/NFT代购 需要的老板联系 @dayel @jhqfkf

👍8💯4🤝42💩2🤮1

Signed 九号·大爷 代发负责人 @dayel

14 Jul 2026, 13:43 UTC≈2,190 viewsread 8 August 2026

现在只接 供需 群发 私信 强拉 僵尸粉 代开会员 跑分业务暂时不接 跑分业务欢迎来对接 我这边给你对接好

Signed 九号代发负责人 @dayel

9 Jul 2026, 04:18 UTC≈3,180 views40 reactionsread 8 August 2026

广告供需 自己找的群 自己发 没有效果怎么办? 不如您看看群发私信强拉 群发是什么? 群发:在适配您项目的群聊中发布您的专属广告精准发布您的广告 私信是什么? 私信:精准私信有意向或者定向客户 发送你的广告 (可以指定群采集进行私信! 强拉是什么? 强拉:精准把顾客或者意向顾客拉入自己的群聊 (可指定群采集拉人) 群发私信强拉寻找九号 @JHYLGF 提供日志让顾客一清二楚 日志=在什么时间(清楚到秒) 什么群 发了什么 点击下方按钮 进行咨询吧!

👍9🤝7💯65💩5🔥4🤮4

Signed Channel Help

13 Jun 2026, 20:12 UTC308 views8 reactionsread 8 August 2026

九号支付群 https://t.me/jiuhaoguanfang

💩4🤮2👍1👎1

Signed 九号代发负责人(私聊加我为联系人)

9 Jun 2026, 10:48 UTC840 viewsread 8 August 2026
Photo

广告供需 自己找的群 自己发 没有效果怎么办? 不如您看看群发广告 群发是什么? 群发:在各个支付群 三方群 四方群 码商群 卡商群 一道 二道群 核销群 交流群业务群公群精准发布您的广告 群发私信强拉寻找九号 提供日志让顾客一清二楚 日志=在什么时间(清楚到秒) 什么群 发了什么 需要群发就联系九号 @JHKF1010

Signed Channel Help

3 Jun 2026, 12:46 UTC392 viewsread 8 August 2026

如果你连测试的钱都不想出,我怎么给你打,我上号要钱,要花时间去准备,我什么都要去做,你挣多挣少 我也不眼红我也不过问 我只挣我那些微薄利润,你打多久的我都欢迎你尊重你把你当朋友当兄弟,我很多客户都是这么来的。但是 你说能不能免费测试,我这真的不欢迎,你们这叫没有同理心 没有共情力 我伺候不了。

Signed 九号代发负责人

Showing the 12 most recent of 15 posts we hold for @JHYLGF. 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 — 372,308 of 1,629,372 entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

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

“九号代发官方频道” (@JHYLGF), 992 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/JHYLGF.

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.