Telegram RegisterThe public register of Telegram
Telegram profile photo for T- G 协 -议- 号 直 -登 -号 批-发-源头

Channel

T- G 协 -议- 号 直 -登 -号 批-发-源头

@xieyihaodi003

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

2,033subscribers

-109 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002528666471
TypeChannel
Username@xieyihaodi003
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live16 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/xieyihaodi003

Topic

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 16 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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.

Growth

2,0322,1422,08715 August 2026 — 2,142 subscribers16 August 2026 — 2,139 subscribers18 August 2026 — 2,128 subscribers21 August 2026 — 2,124 subscribers25 August 2026 — 2,117 subscribers28 August 2026 — 2,107 subscribers31 August 2026 — 2,099 subscribers3 September 2026 — 2,088 subscribers9 September 2026 — 2,073 subscribers12 September 2026 — 2,032 subscribers16 September 2026 — 2,033 subscribers2,03315 August 202616 September 2026
11 measurements spanning 33 days, net -109. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,016–2,159 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 20:362,033+1
12 Sept 2026, 22:392,032-41
9 Sept 2026, 02:552,073-15
3 Sept 2026, 14:572,088-11
31 Aug 2026, 06:172,099-8
28 Aug 2026, 11:532,107-10
25 Aug 2026, 03:452,117-7
21 Aug 2026, 16:222,124-4
18 Aug 2026, 23:522,128-11
16 Aug 2026, 01:432,139-3
15 Aug 2026, 04:312,142first reading

Engagement

16 posts held, back to 16 February 2026the 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 16 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

89 reactions across 4 posts, in 10 distinct kinds. The most used accounts for 15.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉1415.7%
😁1415.7%
🔥1314.6%
1213.5%
👍1213.5%
👌66.74%
💋66.74%
🏆55.62%
💯44.49%
🥰33.37%

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 4 of the 16 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 89 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 16 February 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Aug 2026, 07:20 UTC149 views10 reactionsread 15 August 2026

菲律宾 +63 协议号 大量上货,

💋4🏆2👌2💯2

20 Jul 2026, 05:02 UTC196 views54 reactionsread 15 August 2026

新增关键词监听私信机器人 已经加入几万公群导航群 到时即可监听使用 @jiantinghdbot 支持试用。

😁14🔥1110👍10🎉9

19 Jul 2026, 03:12 UTC188 views11 reactionsread 15 August 2026

原发号机器人已封禁 , 新自动发货机器人已更新 @haodi0072bot 启动就可以了 数据不变

👌4🏆3💋2💯2

16 Jun 2026, 01:58 UTC211 viewsread 15 August 2026
Photo

一款好用的关键词监听机器人 @jiantinghdbot 推荐给大家使用 助大家业务更上一层楼

30 May 2026, 14:09 UTC71 viewsread 15 August 2026
Photo

解决TG收不到通知的问题 打开小火箭,点底部中间的“配置”,找到你正在用的配置文件,点右边的“i”进去。点右上角加号加一条规则:类型选 DOMAIN-SUFFIX,策略PROXY,域名输入 push.apple.com ,填完点蓝色勾保存。最后回到首页把全局路由改成“配置”模式,再开关一次飞行模式重连网络就行了。 这样TG推送基本就能正常收到了。

27 May 2026, 08:56 UTC166 viewsread 15 August 2026

登陆提示邮箱或付费提示或收不到验证码!解决方法 🛠 【TG 备用登录方案 & 资源合集】 遇到官方端风控限制 请直接使用以下优质第三方客户端登录: 🍎 苹果 iOS 用户: ▸ Nicegram:https://apps.apple.com/us/app/nicegram-ai-chat-for-telegram/id1608870673 ▸ iMe:https://apps.apple.com/us/app/ime-ai-messenger-for-telegram/id1450480822 🤖 安卓 Android 用户: ▸ Nicegram:https://github.com/nicegram/Nicegram-Android/releases/download/1.54.2/app.apk ▸ iMe:https://imem.app/download/android/apk 🌐 通用下载 & 资源:

5 Apr 2026, 17:19 UTC312 viewsread 15 August 2026

兄弟们 !单周临期会员号 2u 一个 ,有人需要吗?

Showing the 12 most recent of 16 posts we hold for @xieyihaodi003. 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.

Mentions

Named by 1 registered channel — 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.

Cite this entry

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“T- G 协 -议- 号 直 -登 -号 批-发-源头” (@xieyihaodi003), 2,033 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/xieyihaodi003.

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.