Telegram RegisterThe public register of Telegram
Telegram profile photo for Hybrid Works - 开发者

Channel

Hybrid Works - 开发者

@awnerx

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

478subscribers

-20 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002127857952
TypeChannel
Username@awnerx
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/awnerx

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

4784984887 August 2026 — 498 subscribers8 August 2026 — 498 subscribers14 August 2026 — 490 subscribers21 August 2026 — 487 subscribers29 August 2026 — 486 subscribers7 September 2026 — 483 subscribers14 September 2026 — 478 subscribers7 August 202614 September 2026
7 measurements spanning 38 days, net -20. 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 475–501 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 09:38478-5
7 Sept 2026, 10:57483-3
29 Aug 2026, 01:57486-1
21 Aug 2026, 15:35487-3
14 Aug 2026, 21:56490-8
8 Aug 2026, 04:18498no change
7 Aug 2026, 11:30498first reading

Engagement

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

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 2 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 1 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 April 2026 to 6 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

6 Aug 2026, 23:00 UTC16 viewsread 8 August 2026
Forwarded from @MassAdx

新版本更新 (v2.3.1): - 优化了加入群组的速度及任务进度处理 - 改进了消息发送核心机制,以规避检测与限制 - 优化了私信发送算法 - 新增群组加入时的成员数量筛选功能(可设置仅加入达到最低成员数量要求的群组) - 新增批量退群的成员数量筛选功能(可批量退出成员数低于设定阈值的已加入群组) - 修复了已知问题并进行了各项改进

25 May 2026, 08:53 UTC159 viewsread 8 August 2026

If you need robots, applications, websites, or programs made, contact me. @hexeg

25 May 2026, 08:53 UTC158 viewsread 8 August 2026

如果您需要制作机器人、应用程序、网站或程序,请联系我。🤖📱💻📩 @hexeg

16 May 2026, 06:52 UTC210 viewsread 8 August 2026

If you need robots, applications, websites, or programs made, contact me. @hexeg

16 May 2026, 06:52 UTC214 viewsread 8 August 2026

如果您需要制作机器人、应用程序、网站或程序,请联系我。🤖📱💻📩 @hexeg

15 May 2026, 10:22 UTC232 viewsread 8 August 2026

告别手动操作的时代!MassAdveSW 支持多账号同时管理、全自动加群与广告推送,内置 AI 验证码秒破引擎,无论是图片验证、GIF 闪烁码还是未知验证机制,统统一键攻克。 内置智能代理轮换系统,代理失效自动切换,账号永不掉线;全程无人值守,任务自动完成,让您的流量增长从不停歇。 无论您选择源码授权还是按月订阅激活码,一套系统即可覆盖大规模推广所需的全部场景——群发、拉人、评论、加群、换IP,一站搞定。 立即入手,抢占流量先机!名额有限,先到先得。 💎 免费试用 🎁 详情请见: https://docs.massads.xyz 联系 @hexeg

11 May 2026, 14:35 UTC265 views0 reactionsread 8 August 2026
Photo

花费 670 美元制作了一个带有管理面板的定制 Web 应用程序。 客户满意度是我们的首要任务。 ❤️ 如果你想开发应用程序、网站、机器人或脚本,请联系我。 @hexeg

11 May 2026, 07:07 UTC230 viewsread 8 August 2026

告别手动操作的时代!MassAdveSW 支持多账号同时管理、全自动加群与广告推送,内置 AI 验证码秒破引擎,无论是图片验证、GIF 闪烁码还是未知验证机制,统统一键攻克。 内置智能代理轮换系统,代理失效自动切换,账号永不掉线;全程无人值守,任务自动完成,让您的流量增长从不停歇。 无论您选择源码授权还是按月订阅激活码,一套系统即可覆盖大规模推广所需的全部场景——群发、拉人、评论、加群、换IP,一站搞定。 立即入手,抢占流量先机!名额有限,先到先得。 💎 免费试用 🎁 联系 @hexeg

2 May 2026, 08:12 UTC285 viewsread 8 August 2026

If you need robots, applications, websites, or programs made, contact me. @hexeg

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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.

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

“Hybrid Works - 开发者” (@awnerx), 478 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/awnerx.

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.