1219实名换绑香港,可进百人群,国内国外IP都可以上!包秒,强调一下硬货!盘的来!价格420 ✈️ @wuxin88888
💩10❤9👍4👎3🕊2🔥1

Channel
@wuxin6677
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
511subscribers
-38 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001916658504 |
|---|---|
| Type | Channel |
| Username | @wuxin6677 |
| Created | Between 1 April 2023 and 6 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/wuxin6677 |
Hacking & security — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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, 07:37 | 511 | -3 |
| 25 Sept 2026, 10:19 | 514 | -9 |
| 12 Sept 2026, 16:40 | 523 | -7 |
| 3 Sept 2026, 21:00 | 530 | -6 |
| 27 Aug 2026, 14:08 | 536 | -6 |
| 21 Aug 2026, 08:03 | 542 | -3 |
| 14 Aug 2026, 21:37 | 545 | -4 |
| 8 Aug 2026, 03:45 | 549 | no change |
| 7 Aug 2026, 14:07 | 549 | first reading |
20 posts held, back to 6 September 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 20 posts for this entry, the most recent from 14 December 2023. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
149 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 45.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 67 | 45.0% | |
| 👍 | 36 | 24.2% | |
| 👎 | 16 | 10.7% | |
| 💩 | 14 | 9.40% | |
| 🤮 | 9 | 6.04% | |
| 🕊 | 2 | 1.34% | |
| 🤯 | 2 | 1.34% | |
| 👏 | 1 | 0.671% | |
| 🔥 | 1 | 0.671% | |
| 😁 | 1 | 0.671% |
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 20 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 149 reactions 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 6 September 2023 to 14 December 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
1219实名换绑香港,可进百人群,国内国外IP都可以上!包秒,强调一下硬货!盘的来!价格420 ✈️ @wuxin88888
💩10❤9👍4👎3🕊2🔥1
🔥通知:全网最牛逼的微信号来了❗️ 售后时间当天死号包补号 售后时间当天死号包补号 售后时间当天死号包补号 改头像死号,加好友死号 炒群秒死号,被投诉死号 恶意营销死号,都有售后 记住:一切死号,都有售后 国外私人换+86 全网无视ip 无需养号,上号就直接开干 完美售后 😍 全靠质量说话 😍 ——————————————— 价格420 联系客服✈️@wuxin88888
❤13👍12🤮9👎6😁1
✅出国内无视ip实名微信号,非解封,带资料,国内网络直上,不用挂同地区VPN。扫码登录,不限机型 🈶1 2 3 5 6月无视IP 实名带资料可进企业,可进群,加人 接粉 炒群 当管理都ok ♦️长期使用毫无压力,包15天密错 🔥只要是国内网络就能上🔥 ❗️包10分钟秒死,包新设备❗️ 联系客服✈️@wuxin88888
❤6👍3👎3🤯2💩1
👍点下面链接进入支付宝频道 👍频道:https://t.me/wuxin5566 👍收款专用支付宝,点击频道自行选择
❤3👍2👎1💩1
长期大量出地推【满月静养实名🍉】 -------------------------------- 实名,绑卡,支付冻结 国内无视IP -------------------------------- 售后:包秒,包永久找回,360一个 -------------------------------- 稳稳的 养几天随便造 加人 加群首选 -------------------------------- 联系客服✈️@wuxin88888
❤1👍1👎1
国内5-8年实名(支付正常)带资料,非解封,无视IP国内外都能直接上,质量比解封的好5倍,登上去不用养7天,随便养2-3天后就能用,包秒,包永不找回,价格600一个,联系客服✈️@wuxin88888 国内5-8年实名(支付冻结)带资料,非解封,无视IP国内外都能直接上,质量比解封的好5倍,登上去不用养7天,随便养2-3天后就能用,包秒,包永不找回,价格530一个,联系客服✈️@wuxin88888
❤3👎1💩1
☀️大量出12-19国内静养微信☀️ 国内3-5年未实名 320/个 国内3-5年实名(支付冻结)390/个 国内3-5年实名(支付正常)收藏带身份证正反450/一个 ======================== 售后:1.保首登问题(包秒包新设备5分钟反馈时间 ,超过不售后,) 2.保15天内不找回.上号7天后改密,不改自负!(卖家设备保3天、帐户掉号3天内配合辅助补登) 3.其他封号.限制不售后 4.找回掉设备带图,要不没售后 ======================== 联系客服✈️@wuxin88888
❤7👍3👎1💩1
台湾1-11年。 都是私人非解的 质量好用,十名带支付,换绑锅内,无视ip,短信上号,价格480。包秒,包15天以内找回,有1000的支付额度,来盘
👍4❤1
越南🇻🇳 马来西亚🇲🇾 全网首家新出 高质量货源! 国内实名认证 额度1000 可收付红包 😳😳❤️❤️❤️❤️❤️❤️ 越南490。 马来510
❤6
企业支付宝量大的可以来谈价。 价格给到底,每天供应20-50套
👍2
企业支付宝跳楼价,1拖4,1拖2,独立主,统统2500一套,同行代理来拿货,单独拿子号,主号都有货,包永不找回,联系客服✈️@wuxin88888
❤1
国内5-8年实名(支付正常)带资料,非解封,无视IP国内外都能直接上,质量比解封的好5倍,登上去不用养7天,随便养2-3天后就能用,包秒,包永不找回,价格600一个,联系客服✈️@wuxin88888 国内5-8年实名(支付冻结)带资料,非解封,无视IP国内外都能直接上,质量比解封的好5倍,登上去不用养7天,随便养2-3天后就能用,包秒,包永不找回,价格530一个,联系客服✈️@wuxin88888
❤2👏1
Showing the 12 most recent of 20 posts we hold for @wuxin6677. 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.
Named by 3 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.
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.
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.
“【无心】🟪微信🟪国内外微信号🟪” (@wuxin6677), 511 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/wuxin6677.
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.