项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群469 大老王ID贷|50元利息|介绍客户最高888红包|10分钟下款|周期可选 |老牌靠谱! 押金3000U 公群链接:👉 https://t.me/+1xF_uje6J38wYWQ5 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布44次】
Signed @BADB新公群自动播报

Channel
@xifu
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
61,838subscribers
-937 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001713874131 |
|---|---|
| Type | Channel |
| Usernames | @hgndb @xifu |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/xifu |
Marketing & affiliate — 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 61% 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.
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.
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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @xifu/128211 · this entry22 Feb 2026, 10:06 UTC | @hgn02/867722 Feb 2026, 10:06 UTC | 1.00 | under a minute |
| @xifu/128212 · this entry22 Feb 2026, 11:17 UTC | @hgn02/867822 Feb 2026, 11:17 UTC | 1.00 | under a minute |
| @xifu/128216 · this entry23 Feb 2026, 02:03 UTC | @hgn02/868323 Feb 2026, 02:03 UTC | 1.00 | under a minute |
| @xifu/128217 · this entry23 Feb 2026, 04:06 UTC | @hgn02/868423 Feb 2026, 04:07 UTC | 1.00 | under a minute |
| @xifu/128218 · this entry23 Feb 2026, 05:11 UTC | @hgn02/868523 Feb 2026, 05:11 UTC | 1.00 | under a minute |
| @xifu/128219 · this entry23 Feb 2026, 06:34 UTC | @hgn02/868623 Feb 2026, 06:34 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @hgn02 | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @hgn02 (11–6) |
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 11 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 22 February 2026 to 23 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.
Across the whole group of 2, the earliest publisher we hold is @xifu — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 00:04 | 61,838 | -187 |
| 12 Aug 2026, 00:53 | 62,025 | -199 |
| 10 Aug 2026, 21:32 | 62,224 | -122 |
| 9 Aug 2026, 23:45 | 62,346 | -196 |
| 8 Aug 2026, 23:21 | 62,542 | -194 |
| 7 Aug 2026, 20:13 | 62,736 | -39 |
| 7 Aug 2026, 09:45 | 62,775 | first reading |
20 posts held, back to 22 February 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 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 23 February 2026. An engagement rate over an empty window would be a number about nothing.
项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群469 大老王ID贷|50元利息|介绍客户最高888红包|10分钟下款|周期可选 |老牌靠谱! 押金3000U 公群链接:👉 https://t.me/+1xF_uje6J38wYWQ5 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布44次】
Signed @BADB新公群自动播报
项目名称:🔰 币安担保新开公群播报 项目介绍:✅ 公群1232 回忆苹果im单图0.5 押金788u 公群链接:👉 t.me/jubaopeng1232 币安担保 @DJDJ 新开公群信息自动同步至本频道‼选币安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布25次】
Signed @BADB新公群自动播报
项目名称:🔰 币安担保新开公群播报 项目介绍:✅ 公群939 飞驰 IM盘口直招 押金788u 公群链接:👉 https://t.me/+JGhiijaJtg41MWFk 币安担保 @DJDJ 新开公群信息自动同步至本频道‼选币安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布24次】
Signed @BADB新公群自动播报
项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群3333 长租微信首选【韩立集团】精聊账密/PC登记全天·全网最稳 超强续租{必安推荐3333公群} 押金3611U 公群链接:👉 https://t.me/+XnFGVuAzwqE1M2E0 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布43次】
Signed @BADB新公群自动播报
项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群188 小熊集团租咸鱼QQ 押金3000u 公群链接:👉 https://t.me/+4qchxDsyaHo1ZDQ0 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布42次】
Signed @BADB新公群自动播报
项目名称:🔰 币安担保新开公群播报 项目介绍:✅ 公群008 盛源集团-盘口直收小红书等各类账号社交账号 押金788u 公群链接:👉 https://t.me/+BZqbDKM4KEcwZGU0 币安担保 @DJDJ 新开公群信息自动同步至本频道‼选币安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布23次】
Signed @BADB新公群自动播报
项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群3333 长租微信首选【韩立集团】精聊账密/PC登记全天·全网最稳 超强续租{必安推荐3333公群} 押金3611U 公群链接:👉 https://t.me/+XnFGVuAzwqE1M2E0 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布41次】
Signed @BADB新公群自动播报
项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群269 小小远程短信接听 押金3000u 公群链接:👉 https://t.me/+5wHh9CjvywRlOWZk 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布40次】
Signed @BADB新公群自动播报
项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群3333 长租微信首选【韩立集团】精聊账密/PC登记全天·全网最稳 超强续租{必安推荐3333公群} 押金3611U 公群链接:👉 https://t.me/+XnFGVuAzwqE1M2E0 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布39次】
Signed @BADB新公群自动播报
项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群333 派大星手机口120u-200u下课秒结账 押金5000U 公群链接:👉 https://t.me/+lZ4dlPzD63s1Nzc0 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布38次】
Signed @BADB新公群自动播报
项目名称:🔰 币安担保新开公群播报 项目介绍:✅ 公群008 盛源集团-盘口直收小红书等各类账号社交账号 押金788u 公群链接:👉 https://t.me/+BZqbDKM4KEcwZGU0 币安担保 @DJDJ 新开公群信息自动同步至本频道‼选币安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布22次】
Signed @BADB新公群自动播报
项目名称:🔰 必安担保新开公群播报 项目介绍:✅ 公群014 腾辉集团催收短信口 200 盘口直招 押金3000U 公群链接:👉 https://t.me/+OoEZJIMIYvIwMDQ1 必安担保 @USDD 新开公群信息自动同步至本频道‼选必安❤心必安!‼本频道已作废,请关注以下频道 👉查看发布者 【累计广告发布37次】
Signed @BADB新公群自动播报
Showing the 12 most recent of 20 posts we hold for @xifu. 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 — 967,629 of 1,151,006entries 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.
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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“姑娘已跑|供需广告认准 @BAGX” (@xifu), 61,838 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/xifu.
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.