Telegram RegisterThe public register of Telegram
Telegram profile photo for NitroSeen [ENG]

Bot

NitroSeen [ENG]

@NitroSeen_GlobalBot

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

28,632monthly users

-8,607 since we began measuring on 7 August 2026

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

Register entry

Telegram ID8088676005
TypeBot
Username@NitroSeen_GlobalBot
First recorded14 August 2026
Last confirmed live11 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/NitroSeen_GlobalBot

Topic

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

25,36337,23931,3017 August 2026 — 37,239 monthly users8 August 2026 — 35,101 monthly users10 August 2026 — 35,250 monthly users11 August 2026 — 34,818 monthly users12 August 2026 — 33,604 monthly users13 August 2026 — 29,660 monthly users14 August 2026 — 29,660 monthly users15 August 2026 — 29,199 monthly users16 August 2026 — 28,625 monthly users17 August 2026 — 28,563 monthly users18 August 2026 — 28,533 monthly users20 August 2026 — 28,396 monthly users22 August 2026 — 27,366 monthly users23 August 2026 — 27,683 monthly users25 August 2026 — 27,884 monthly users25 August 2026 — 27,870 monthly users26 August 2026 — 27,728 monthly users28 August 2026 — 26,149 monthly users29 August 2026 — 26,487 monthly users31 August 2026 — 26,572 monthly users1 September 2026 — 27,263 monthly users2 September 2026 — 27,318 monthly users3 September 2026 — 27,612 monthly users6 September 2026 — 27,473 monthly users9 September 2026 — 27,476 monthly users11 September 2026 — 26,988 monthly users13 September 2026 — 27,010 monthly users15 September 2026 — 27,711 monthly users17 September 2026 — 27,520 monthly users25 September 2026 — 27,585 monthly users4 October 2026 — 25,428 monthly users8 October 2026 — 25,856 monthly users12 October 2026 — 26,337 monthly users14 October 2026 — 26,287 monthly users15 October 2026 — 26,114 monthly users17 October 2026 — 25,788 monthly users18 October 2026 — 25,639 monthly users19 October 2026 — 25,759 monthly users20 October 2026 — 25,930 monthly users21 October 2026 — 25,867 monthly users22 October 2026 — 25,363 monthly users24 October 2026 — 26,107 monthly users25 October 2026 — 25,883 monthly users26 October 2026 — 25,789 monthly users27 October 2026 — 25,922 monthly users28 October 2026 — 26,148 monthly users29 October 2026 — 26,211 monthly users30 October 2026 — 26,231 monthly users31 October 2026 — 25,957 monthly users1 November 2026 — 26,488 monthly users2 November 2026 — 26,401 monthly users3 November 2026 — 26,730 monthly users4 November 2026 — 27,219 monthly users5 November 2026 — 29,412 monthly users7 November 2026 — 29,096 monthly users8 November 2026 — 28,044 monthly users9 November 2026 — 28,628 monthly users11 November 2026 — 28,632 monthly users28,6327 August 202611 November 2026
58 measurements spanning 96 days, net -8,607. 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 23,582–39,020 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 58
Measured (UTC)Monthly usersChange
11 Nov 2026, 11:4028,632+4
9 Nov 2026, 18:0928,628+584
8 Nov 2026, 10:0028,044-1,052
7 Nov 2026, 07:3129,096-316
5 Nov 2026, 07:3429,412+2,193
4 Nov 2026, 10:1927,219+489
3 Nov 2026, 09:3026,730+329
2 Nov 2026, 06:4626,401-87
1 Nov 2026, 07:3126,488+531
31 Oct 2026, 08:3825,957-274
30 Oct 2026, 06:0726,231+20
29 Oct 2026, 07:5626,211+63
28 Oct 2026, 03:4026,148+226
27 Oct 2026, 06:3625,922+133
26 Oct 2026, 05:2725,789-94
25 Oct 2026, 03:0025,883-224
24 Oct 2026, 01:4726,107+744
22 Oct 2026, 23:4025,363-504
21 Oct 2026, 22:3025,867-63
20 Oct 2026, 14:2725,930first 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.

Forward network

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

“NitroSeen [ENG]” (@NitroSeen_GlobalBot), 28,632 monthly users as measured 11 November 2026. Telegram Register, tgregister.com/channel/NitroSeen_GlobalBot.

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.