Telegram RegisterThe public register of Telegram
Telegram profile photo for GnoranceX社工库机器人

Bot

GnoranceX社工库机器人

@GnoranceX_bot

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

41,365monthly users

-12,478 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID6769108581
TypeBot
Username@GnoranceX_bot
First recorded11 August 2026
Last confirmed live16 November 2026
Measurements held51
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/GnoranceX_bot

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 the other topics.

Growth

38,02278,21258,1177 August 2026 — 53,843 monthly users8 August 2026 — 55,604 monthly users9 August 2026 — 68,828 monthly users11 August 2026 — 72,136 monthly users11 August 2026 — 72,136 monthly users13 August 2026 — 72,754 monthly users14 August 2026 — 73,057 monthly users16 August 2026 — 73,195 monthly users18 August 2026 — 73,460 monthly users19 August 2026 — 73,599 monthly users20 August 2026 — 75,002 monthly users22 August 2026 — 75,349 monthly users23 August 2026 — 76,463 monthly users24 August 2026 — 76,998 monthly users25 August 2026 — 77,799 monthly users26 August 2026 — 77,956 monthly users28 August 2026 — 78,212 monthly users1 September 2026 — 75,519 monthly users2 September 2026 — 55,416 monthly users3 September 2026 — 55,745 monthly users5 September 2026 — 55,987 monthly users8 September 2026 — 55,423 monthly users11 September 2026 — 41,546 monthly users13 September 2026 — 48,257 monthly users14 September 2026 — 47,343 monthly users16 September 2026 — 47,308 monthly users18 September 2026 — 47,001 monthly users2 October 2026 — 48,482 monthly users7 October 2026 — 48,493 monthly users11 October 2026 — 48,420 monthly users14 October 2026 — 38,421 monthly users16 October 2026 — 38,022 monthly users18 October 2026 — 38,658 monthly users19 October 2026 — 38,661 monthly users22 October 2026 — 39,765 monthly users23 October 2026 — 39,933 monthly users24 October 2026 — 40,077 monthly users25 October 2026 — 44,452 monthly users26 October 2026 — 46,054 monthly users28 October 2026 — 46,796 monthly users29 October 2026 — 46,441 monthly users31 October 2026 — 44,809 monthly users2 November 2026 — 43,251 monthly users4 November 2026 — 40,607 monthly users5 November 2026 — 40,742 monthly users5 November 2026 — 40,921 monthly users7 November 2026 — 40,490 monthly users9 November 2026 — 40,582 monthly users10 November 2026 — 40,166 monthly users12 November 2026 — 40,439 monthly users16 November 2026 — 41,365 monthly users41,3657 August 202616 November 2026
51 measurements spanning 101 days, net -12,478. 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 31,994–84,241 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 51
Measured (UTC)Monthly usersChange
16 Nov 2026, 07:1941,365+926
12 Nov 2026, 15:4540,439+273
10 Nov 2026, 15:3440,166-416
9 Nov 2026, 02:1140,582+92
7 Nov 2026, 21:0740,490-431
5 Nov 2026, 23:4840,921+179
5 Nov 2026, 03:0040,742+135
4 Nov 2026, 05:4740,607-2,644
2 Nov 2026, 07:1843,251-1,558
31 Oct 2026, 09:3044,809-1,632
29 Oct 2026, 10:1646,441-355
28 Oct 2026, 09:0946,796+742
26 Oct 2026, 08:5946,054+1,602
25 Oct 2026, 08:4444,452+4,375
24 Oct 2026, 11:2740,077+144
23 Oct 2026, 12:0939,933+168
22 Oct 2026, 08:4039,765+1,104
19 Oct 2026, 01:5138,661+3
18 Oct 2026, 04:2138,658+636
16 Oct 2026, 06:5938,022first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

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

“GnoranceX社工库机器人” (@GnoranceX_bot), 41,365 monthly users as measured 16 November 2026. Telegram Register, tgregister.com/channel/GnoranceX_bot.

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.