Channel
@huidjfdhf
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
13subscribers
+1 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001633190522 |
|---|---|
| Type | Channel |
| Username | @huidjfdhf |
| Created | 21 August 2022 — measured — dated from the channel’s first post |
| First recorded | 23 August 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 29 September 2026 |
| On Telegram | t.me/huidjfdhf |
Other / unclassifiable — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 82% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 14:58 | 13 | +1 |
| 24 Aug 2026, 09:32 | 12 | no change |
| 23 Aug 2026, 14:45 | 12 | first reading |
2 posts held, back to 21 August 2022 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 12 September 2022. An engagement rate over an empty window would be a number about nothing.
16 reactions across 1 post, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 8 | 50.0% | |
| 👎 | 8 | 50.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 1 of the 2 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 2 most recent posts we hold, published 21 August 2022 to 12 September 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
易步骤(通用版)： 第一步、供需双方联系CA联盟担保官方 @CAlianmengdanbao01 安排交易群对接，非CA联盟担保官方工作人员建群一律无效； 第二步、供需双方需在CA联盟担保官方交易群内说明、协商并确认交易详情，如：商品描述、收货标准、结算账期、收款标准、交易金额、交易数量、佣金金额、手续费等相关内容。 第三步、由交易员汇总编辑买卖双方交易详情并最终由买卖双方确认后方可正式开始交易； 第四步、买家将货款转入CA联盟担保官方上押账户并提供凭证; 第五步、由交易员确认收款后通知卖家发货; 第六步、卖家接到交易员发货通知后开始发货，并提供发货凭证; 第七步、买家确认收货后通知交易员放款; 第八步、收到买家收货确认或放款通知后交易员扣除佣金向卖家解押放款，并提供放款凭证; 第九步、卖家确认收款，交易完成。 纠纷处理原则： 1、交易过程中买卖双方一切沟通、协商、交易记录必须在官方交易群中进行，一切私聊内容均视为无效； …
👍8👎8
Channel created
Showing the 2 most recent of 2 posts we hold for @huidjfdhf. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@huidjfdhf named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“CA担保规则” (@huidjfdhf), 13 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/huidjfdhf.
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.