Telegram RegisterThe public register of Telegram

Channel

灰姑娘已跑|唯必安永恒 @BAGQ

@hgn01

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

41,923subscribers

-662 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001819456022
TypeChannel
Username@hgn01
Description‼️本频道作废,速迁至我们的官方供需广告频道,提供更稳定、更安全、更有保障的服务。 🧧3月8日官方频道红包雨🧧 官方频道1: @BAGQ (必安公群) 官方频道2: @DJDJ(币安公群) 官方频道3: @BADB (优选公群)
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/hgn01

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 62% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hgn01/77782 · this entry24 Feb 2026, 11:35 UTC@m416/1044824 Feb 2026, 11:35 UTC1.00under a minute
@hgn01/77784 · this entry24 Feb 2026, 12:29 UTC@m416/1045024 Feb 2026, 12:29 UTC1.00under a minute
@hgn01/77786 · this entry24 Feb 2026, 13:54 UTC@m416/1045224 Feb 2026, 13:54 UTC1.00under a minute
@hgn01/77788 · this entry24 Feb 2026, 15:54 UTC@m416/1045424 Feb 2026, 15:54 UTC1.00under a minute
@hgn01/77789 · this entry25 Feb 2026, 05:22 UTC@m416/1045525 Feb 2026, 05:22 UTC1.00under a minute
@hgn01/77792 · this entry25 Feb 2026, 05:56 UTC@m416/1045825 Feb 2026, 05:56 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@m41617 (8/8 hand-verifiable sample passed)1.00under a minute@m416 (161)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 16 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 24 February 2026 to 25 February 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @m416. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

41,92342,58542,2547 August 2026 — 42,585 subscribers7 August 2026 — 42,585 subscribers8 August 2026 — 42,462 subscribers9 August 2026 — 42,314 subscribers10 August 2026 — 42,220 subscribers11 August 2026 — 42,075 subscribers12 August 2026 — 41,923 subscribers7 August 202612 August 2026
7 measurements spanning 5 days, net -662. 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 41,824–42,684 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:1841,923-152
11 Aug 2026, 19:5142,075-145
10 Aug 2026, 17:1642,220-94
9 Aug 2026, 14:1242,314-148
8 Aug 2026, 11:0142,462-123
7 Aug 2026, 11:3042,585no change
7 Aug 2026, 11:1942,585first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 25 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
103
Videos
15
Links
70,900

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
133.3%
👏133.3%
🥰133.3%

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

Measured over the 20 most recent posts we hold, published 24 February 2026 to 25 February 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

25 Feb 2026, 08:08 UTC≈1,650 views2 reactionsread 13 August 2026

项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群026 高价收抖音代评论团散24小时开工 押金3000u 公群链接:👉 https://t.me/+O49UP3FX0WE4OGI1 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布59次】

1👏1

Signed @BADB新公群自动播报

25 Feb 2026, 08:01 UTC≈1,500 views1 reactionsread 13 August 2026

项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群814 未来国际码接回U 押金7300U 公群链接:👉 https://t.me/+vxUCZL8dy6MwYmI0 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布58次】

🥰1

Signed @BADB新公群自动播报

25 Feb 2026, 07:59 UTC923 viewsread 13 August 2026

项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群599 租闲鱼·首选【路易集团】 位置无限{全网最稳续租 福利待遇最高}押金4500U 公群链接:👉 https://t.me/+GZyTW5xUMcg4ZjA0 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布57次】

Signed @BADB新公群自动播报

25 Feb 2026, 06:09 UTC688 viewsread 13 August 2026

项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群2538 🏆Q7集团 微信精聊超强续租|诚招各位散户 号商 团队 待遇拉满【单价全网最高】 押金6100u 公群链接:👉 https://t.me/+_ysQutcgUfY1Njdk 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布56次】

Signed @BADB新公群自动播报

25 Feb 2026, 05:56 UTC456 viewsread 13 August 2026

项目名称:🔰 币安担保在押公群播报 项目介绍:✅ 公群789 协议球六合彩内幕15U 卖料 押金789U 公群链接:👉 https://t.me/+7c0JbqZByLhhOTNl 币安担保新开公群信息自动同步至本频道‼选币安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布35次】

Signed @BADB新公群自动播报

25 Feb 2026, 05:45 UTC354 viewsread 13 August 2026

项目名称:🔰 币安担保在押公群播报 项目介绍:✅ 公群006 租小红书全网最高价 押金788u 公群链接:👉 https://t.me/+bCSSxvezfNYwYjll 币安担保新开公群信息自动同步至本频道‼选币安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布34次】

Signed @BADB新公群自动播报

25 Feb 2026, 05:25 UTC302 viewsread 13 August 2026

项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群911 顺富集团苹果im 押金3000u 公群链接:👉 https://t.me/+DiDLeAE-yYRhNDA1 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布55次】

Signed @BADB新公群自动播报

25 Feb 2026, 05:22 UTC256 viewsread 13 August 2026

项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群3333 长租微信首选【韩立集团】精聊账密/PC登记全天·全网最稳 超强续租{必安推荐3333公群} 押金3611U 公群链接:👉 https://t.me/+XnFGVuAzwqE1M2E0 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布54次】

Signed @BADB新公群自动播报

24 Feb 2026, 15:54 UTC238 viewsread 13 August 2026

项目名称:🔰 币安担保在押公群播报 项目介绍:✅ 公群499 海鸥集团 | 博彩纯文 | 高价0.45 | 押金999u 公群链接:👉 https://t.me/+jk629FM-LmwwYTJk 币安担保新开公群信息自动同步至本频道‼选币安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布33次】

Signed @BADB新公群自动播报

24 Feb 2026, 13:55 UTC222 viewsread 13 August 2026

项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群6789 太乙一道大混码/卡接回U 押金7300U 公群链接:👉 https://t.me/+J2V_jSYIuK0xMjk0 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布53次】

Signed @BADB新公群自动播报

24 Feb 2026, 13:54 UTC196 viewsread 13 August 2026

项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群880 海鸥集团丨博彩纯文丨高价0.45丨 押金3333u 公群链接:👉 https://t.me/+_JxCLHauKxpkZDg1 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布52次】

Signed @BADB新公群自动播报

24 Feb 2026, 12:33 UTC183 viewsread 13 August 2026

项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群456 微信支付宝码接回u/卡50点位 日量50+ 押金7000U 公群链接:👉 https://t.me/+fpUojcL_ZwRkMTlk 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布51次】

Signed @BADB新公群自动播报

Showing the 12 most recent of 20 posts we hold for @hgn01. 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 — 989,012 of 1,176,251entries 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 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“灰姑娘已跑|唯必安永恒 @BAGQ” (@hgn01), 41,923 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/hgn01.

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.