Telegram RegisterThe public register of Telegram
Telegram profile photo for inMax Bot

Bot

inMax Bot

@inmaxbot

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

11,045monthly users

-1,010 since we began measuring on 10 August 2026

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

Register entry

Telegram ID7448568061
TypeBot
Username@inmaxbot
First recorded21 August 2026
Last confirmed live6 November 2026
Measurements held42
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/inmaxbot

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 11 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

10,97012,05511,512.510 August 2026 — 12,055 monthly users12 August 2026 — 11,993 monthly users13 August 2026 — 11,960 monthly users14 August 2026 — 11,852 monthly users15 August 2026 — 11,846 monthly users18 August 2026 — 11,762 monthly users20 August 2026 — 11,713 monthly users20 August 2026 — 11,692 monthly users21 August 2026 — 11,692 monthly users23 August 2026 — 11,656 monthly users25 August 2026 — 11,655 monthly users26 August 2026 — 11,670 monthly users28 August 2026 — 11,695 monthly users31 August 2026 — 11,720 monthly users1 September 2026 — 11,595 monthly users3 September 2026 — 11,751 monthly users5 September 2026 — 11,750 monthly users11 September 2026 — 11,710 monthly users13 September 2026 — 11,686 monthly users17 September 2026 — 11,652 monthly users25 September 2026 — 11,567 monthly users4 October 2026 — 11,298 monthly users8 October 2026 — 11,264 monthly users13 October 2026 — 11,271 monthly users14 October 2026 — 11,260 monthly users15 October 2026 — 11,255 monthly users16 October 2026 — 11,137 monthly users17 October 2026 — 11,257 monthly users19 October 2026 — 11,214 monthly users21 October 2026 — 11,176 monthly users22 October 2026 — 11,161 monthly users24 October 2026 — 11,118 monthly users25 October 2026 — 11,106 monthly users26 October 2026 — 10,970 monthly users27 October 2026 — 11,049 monthly users28 October 2026 — 11,063 monthly users30 October 2026 — 11,062 monthly users31 October 2026 — 11,044 monthly users3 November 2026 — 11,029 monthly users4 November 2026 — 10,979 monthly users5 November 2026 — 11,003 monthly users6 November 2026 — 11,045 monthly users11,04510 August 20266 November 2026
42 measurements spanning 88 days, net -1,010. 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 10,807–12,218 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 42
Measured (UTC)Monthly usersChange
6 Nov 2026, 07:1711,045+42
5 Nov 2026, 04:3811,003+24
4 Nov 2026, 05:4110,979-50
3 Nov 2026, 05:0811,029-15
31 Oct 2026, 07:3611,044-18
30 Oct 2026, 07:4711,062-1
28 Oct 2026, 09:3711,063+14
27 Oct 2026, 11:2911,049+79
26 Oct 2026, 10:2810,970-136
25 Oct 2026, 11:3011,106-12
24 Oct 2026, 13:4711,118-43
22 Oct 2026, 09:5011,161-15
21 Oct 2026, 06:0011,176-38
19 Oct 2026, 06:4911,214-43
17 Oct 2026, 09:1411,257+120
16 Oct 2026, 12:2711,137-118
15 Oct 2026, 15:4111,255-5
14 Oct 2026, 14:2811,260-11
13 Oct 2026, 02:5611,271+7
8 Oct 2026, 18:1911,264first 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 6 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“inMax Bot” (@inmaxbot), 11,045 monthly users as measured 6 November 2026. Telegram Register, tgregister.com/channel/inmaxbot.

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.