婚姻5u排队在秒! 收大头 真地址个户 支机 支百 公网 联通也在秒
❤1
Signed 泪昏查档-婚姻无限收 🌅

Channel
@leihunchadang
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
74subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001884606542 |
|---|---|
| Type | Channel |
| Username | @leihunchadang |
| Created | Between 1 October 2022 and 20 August 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/leihunchadang |
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 7 October 2026 and assigned it the closest of 31 fixed categories, at 65% 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 |
|---|---|---|
| 7 Oct 2026, 06:19 | 74 | -1 |
| 9 Aug 2026, 21:15 | 75 | no change |
| 7 Aug 2026, 11:57 | 75 | first reading |
17 posts held, back to 20 August 2023 — 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 17 posts for this entry, the most recent from 10 January 2024. An engagement rate over an empty window would be a number about nothing.
15 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 5 | 33.3% | |
| ❤ | 4 | 26.7% | |
| 😁 | 4 | 26.7% | |
| 🔥 | 1 | 6.67% | |
| 🥰 | 1 | 6.67% |
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 17 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 15 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 20 August 2023 to 10 January 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
婚姻5u排队在秒! 收大头 真地址个户 支机 支百 公网 联通也在秒
❤1
Signed 泪昏查档-婚姻无限收 🌅
免费机器人 t.me/aishegongkubot?start=AISGK_IP8R0K0P
Signed 泪昏查档-婚姻无限收 🌅
婚姻4u排队在秒! 收大头 真地址个户 支机 支百 公网 联通也在秒
Signed 泪昏查档-婚姻无限收 🌅
婚姻4u排队在秒! 收大头 真地址个户 支机 支百 公网 联通也在秒
😁3
Signed 泪昏查档-婚姻无限收 🌅
大头单子收大头单子 真地址个户也在收 收公网机主 支机,支百在秒 婚姻还是在收4u在收 @leihunchadang666
Signed 泪昏查档-婚姻无限收 🌅
来点大头单子,10r/1u 秒秒秒,另外也接真地址个户,婚姻4u无限收 @leihunchadang666
🥰1
Signed 泪昏查档/三网机/婚姻无限收 🌅
来点大头单子,10r/1u 秒秒秒,另外也接真地址个户,婚姻4u无限收 @leihunchadang666
Signed 泪昏查档/三网机/婚姻无限收 🌅
收拍照个户,公网,联通晚点开秒,电信,支机
Signed 泪昏查档/三网机/婚姻无限收 🌅
无限收真地址个户,公网,联通,在线秒
Signed 泪昏查档/三网机/婚姻无限收 🌅
收点真地址个户,5u在秒
❤1👍1
Signed 泪昏查档/三网机/婚姻无限收 🌅
10省 JS 湖南 湖北 广东 广西 四川 重庆 江西 安徽 浙江 云南 以上业务 人在均秒出 速度超快 堪比全户
Signed 泪昏查档/三网机/婚姻无限收 🌅
泪昏查档 pinned «联机移机电百🔥 支百 支机 文字猎 人脸猎 名下房 名下车 @leihunchadang666»
Showing the 12 most recent of 17 posts we hold for @leihunchadang. 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.
@leihunchadang named 1 handle 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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“泪昏查档” (@leihunchadang), 74 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/leihunchadang.
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.