Channel
@xieyihao588
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
6subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001581561302 |
|---|---|
| Type | Channel |
| Username | @xieyihao588 |
| Created | Between 1 August 2021 and 26 August 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/xieyihao588 |
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 6 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 |
|---|---|---|
| 6 Oct 2026, 18:21 | 6 | +1 |
| 13 Aug 2026, 02:03 | 5 | no change |
| 7 Aug 2026, 07:27 | 5 | first reading |
11 posts held, back to 26 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 11 posts for this entry, the most recent from 4 January 2024. An engagement rate over an empty window would be a number about nothing.
13 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 53.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 7 | 53.8% | |
| 🔥 | 3 | 23.1% | |
| 🥰 | 2 | 15.4% | |
| 👏 | 1 | 7.69% |
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 11 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 26 August 2022 to 4 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.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
😍😍这惊人的私发量👍👍 🥳购买联系: @xieyihao58
👍1
🦁session协议小号🦁 💰零售3元 💰1000起 2.5元 💪定制拉人，私信协议号 🉑包质量 包售后（死号包补） ⚠️好用，好用，不好用来找我⚠️ 👍购买联系： @xieyihao588
👍1🥰1
😘😘每个协议号能拉满设置人数，还没死号，说的天花乱坠都不如卖来试试有用，还是那句话协议号不好用来砍我😁😁 ✅购买联系： @xieyihao58
👍1👏1
🥰🥰感谢客户支持信任，用过才知道，协议号拉人效果，嘎嘎猛💪💪 ✅购买联系: @xieyihao58
👍1🔥1🥰1
🦁session协议小号🦁 💰零售3元 💰1000起 2.5元 🉑包质量 包售后（死号包补） ⚠️量大请提前预定⚠️ ✈️购买认准：@xieyihao588
👍1🔥1
🙏🙏🙏感谢8️⃣月老板们的支持信任，9️⃣月继续开干，好不好用，用过才知道💪💪💪 ✅诚信经营，购买认准：@xieyihao58
👍2🔥1
1️⃣私发【先分小批量号测试再发送】 内容有：@，群链接；蓝色字样；会增加被封率⚠️⚠️ 发送相同内容，相同图片，私发成功超一定数量，被官方标记风控，之后发送该内容的号会被拦截，封禁。 出现上述内容表现为私发成功数停滞不动，私发失败数增加，如遇此情况，立即停止私发，避免协议号大 量被封！更改内容后再私发⚠️⚠️ 每次私发结束，关闭软件后，换vpn节点，优先选择发送用户的国家，更改完重新打开使用，最好更换另 一批号之后再私发⚠️⚠️ 2️⃣拉人【先分小批量号测试再发送】 用户活跃度越高，越容易被举报，群短时间被多次举报就可能被封禁，新群（半个月内的群）建议先拉僵尸粉 再拉活跃用户 如果工具显示拉人成功数在增加，群内人数不在增加，甚至反而减少，证明已经被官方风控标记，请36小时内不要对该群进行拉人.⚠️⚠️ 3️⃣群发，转发 建议内容链接放频道链接，放直登号链接，群发量大容易被封⚠️⚠️ 发送间隔时间太短【建…
👊【出一手协议号 】 【抗TG封号机制】 👊【群发】【 转发 】【私信 】【拉人】 👊【零售3💰】【1000+ 2.5💰】 💐吸引你的，首先是广告‼️‼️ 💐征服你的，最终是效果💪💪 ⚠️可先买少量试用，好用再买🥰🥰 ✅购买联系：@xieyihao588
🙏🙏感谢兄弟信任，深夜要几百个号开干，出优质协议号，24小时在线服务✊✊ 购买认准: @xieyihao58 （发仔）
Showing the 11 most recent of 11 posts we hold for @xieyihao588. 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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“TG协议号 ▏一手协议号session号批发出售✈️飞机号批发出售✈️” (@xieyihao588), 6 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/xieyihao588.
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.