Telegram RegisterThe public register of Telegram
Telegram profile photo for 我本将心向明月

Channel

我本将心向明月

@zghnb666

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

193subscribers

-9 since we began measuring on 19 September 2026

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

Register entry

Telegram ID-1003580669645
TypeChannel
Username@zghnb666
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 September 2026
Last confirmed live7 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/zghnb666

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 7 October 2026 and assigned it the closest of 31 fixed categories, at 64% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

193202197.519 September 2026 — 202 subscribers26 September 2026 — 198 subscribers7 October 2026 — 193 subscribers19 September 20267 October 2026
3 measurements spanning 18 days, net -9. 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 192–203 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 15:02193-5
26 Sept 2026, 00:59198-4
19 Sept 2026, 09:22202first reading

Engagement

15 posts held, back to 25 August 2026 — the 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
59.4%
avg views ÷ 193 subscribers
Avg views / post
115
9 posts measured
Reaction rate
0.98%
reactions ÷ views · ER floor
Posts in window
10
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. It is computed over the 3 of 9 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 19 September 2026
Posts held15 (25 August 2026 – 19 September 2026)
Views total1,031
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Sept 2026, 09:22 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 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4100.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 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 4 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 25 August 2026 to 19 September 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

19 Sept 2026, 07:15 UTC35 viewsread 19 September 2026
Photo

公网补齐一分钟一单全天在秒 🤩🤩🤩🤩🤩🤩

Signed 雪下紫禁城 春江 5213

19 Sept 2026, 04:02 UTC24 viewsread 19 September 2026
Forwarded from @weittkx

进我公群送头!!https://t.me/+H5y2hp2EJnhkMDVh

Signed 雪下紫禁城 春江 5213

18 Sept 2026, 15:47 UTC88 views1 reactionsread 19 September 2026
Photo

源头实时公网在逃数据 雪下紫禁城 9.18 网逃已回完 三个版本只出最新只出最新! 无历史数据 纯公网 出最新实时数据 1.实时网逃 无撤销 无详情 🤩🤩🤩🤩🤩🤩 (适合查询是否为网逃的客户) 每天限定15单 控制别的版本单量 先到先得 2.实时网逃 在逃无详情 带撤销 撤销或结案带详情 🤩🤩🤩🤩🤩🤩 (物美价廉的最佳选择)无限量 3.实时网逃 所有带详情 带撤销 带案件号 带编号 🤩🤩🤩🤩🤩🤩 (适合需要查所有详细网逃客户)无限量 源头条子一天多批回 最迟当天 空也收费 一分钱一分货 同行代理来拿价格 源头厂家 一手条子 已包线 价格给到最优 人工唯一客服 @tg_520u

❤1

Signed 雪下紫禁城 春江 5213

18 Sept 2026, 14:46 UTC92 views1 reactionsread 19 September 2026

文全补齐猎魔 秒线文字全户🤩🤩🤩🤩🤩🤩 秒线公网猎魔🤩🤩🤩🤩🤩🤩 秒线公网补齐🤩🤩🤩🤩🤩🤩 全天秒线文全 一手源头出单 保真不保漏!!! 寻量大同行代理 盘口老板 催收老板 你有量我有价 欢迎拿屠龙刀来砍我 支持报备 春江公群5213已压1666🤩! 人工唯一客服 @tg_520u

❤1

Signed 雪下紫禁城 春江 5213

17 Sept 2026, 10:43 UTC228 views2 reactionsread 19 September 2026

https://t.me/+MOskrYlD0x4zYmI5 春江已压1666u 欢迎各位来聊天

❤2

Signed 雪下紫禁城

12 Sept 2026, 02:09 UTC213 viewsread 19 September 2026

微反🤩🤩🤩 破解支百🤩🤩🤩 文全🤩🤩🤩 公网补齐🤩🤩🤩 破解电百🤩🤩 支机🤩🤩 法人🤩🤩 机主🤩🤩 抖反🤩🤩 其他业务后台自己问 @tg_520u

Signed 雪下紫禁城

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

Forward network

Republished by

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“我本将心向明月” (@zghnb666), 193 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/zghnb666.

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.