Telegram RegisterThe public register of Telegram

Bot

FILE MANTAN

@FILE_MANTANBOT

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

58,954monthly users

-17,942 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 ID7688991626
TypeBot
Username@FILE_MANTANBOT
First recorded11 August 2026
Last confirmed live18 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/FILE_MANTANBOT

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 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

41,22776,89659,061.57 August 2026 — 76,896 monthly users9 August 2026 — 76,406 monthly users9 August 2026 — 76,528 monthly users11 August 2026 — 76,528 monthly users12 August 2026 — 75,368 monthly users13 August 2026 — 76,016 monthly users14 August 2026 — 75,660 monthly users16 August 2026 — 74,478 monthly users17 August 2026 — 75,599 monthly users21 August 2026 — 74,921 monthly users25 August 2026 — 71,152 monthly users26 August 2026 — 70,577 monthly users28 August 2026 — 68,661 monthly users2 September 2026 — 64,660 monthly users3 September 2026 — 63,843 monthly users4 September 2026 — 63,030 monthly users7 September 2026 — 60,409 monthly users10 September 2026 — 55,066 monthly users12 September 2026 — 52,940 monthly users14 September 2026 — 51,042 monthly users15 September 2026 — 46,271 monthly users18 September 2026 — 44,538 monthly users29 September 2026 — 41,227 monthly users5 October 2026 — 48,195 monthly users10 October 2026 — 50,843 monthly users13 October 2026 — 52,365 monthly users15 October 2026 — 53,082 monthly users16 October 2026 — 53,341 monthly users17 October 2026 — 53,310 monthly users19 October 2026 — 54,369 monthly users20 October 2026 — 54,646 monthly users21 October 2026 — 54,821 monthly users22 October 2026 — 54,883 monthly users23 October 2026 — 55,002 monthly users25 October 2026 — 55,184 monthly users27 October 2026 — 55,520 monthly users28 October 2026 — 55,710 monthly users29 October 2026 — 55,836 monthly users30 October 2026 — 55,945 monthly users31 October 2026 — 57,124 monthly users1 November 2026 — 57,855 monthly users3 November 2026 — 58,374 monthly users4 November 2026 — 59,042 monthly users5 November 2026 — 59,240 monthly users7 November 2026 — 59,374 monthly users8 November 2026 — 59,125 monthly users9 November 2026 — 58,460 monthly users11 November 2026 — 59,425 monthly users15 November 2026 — 58,542 monthly users18 November 2026 — 58,954 monthly users58,9547 August 202618 November 2026
50 measurements spanning 103 days, net -17,942. 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 35,877–82,246 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 50
Measured (UTC)Monthly usersChange
18 Nov 2026, 00:0958,954+412
15 Nov 2026, 00:1758,542-883
11 Nov 2026, 19:4059,425+965
9 Nov 2026, 22:4958,460-665
8 Nov 2026, 13:4659,125-249
7 Nov 2026, 08:0159,374+134
5 Nov 2026, 06:4859,240+198
4 Nov 2026, 07:5759,042+668
3 Nov 2026, 06:3958,374+519
1 Nov 2026, 10:2657,855+731
31 Oct 2026, 07:0657,124+1,179
30 Oct 2026, 03:4755,945+109
29 Oct 2026, 07:0155,836+126
28 Oct 2026, 05:4755,710+190
27 Oct 2026, 07:4155,520+336
25 Oct 2026, 09:5555,184+182
23 Oct 2026, 15:2555,002+119
22 Oct 2026, 12:2954,883+62
21 Oct 2026, 06:4854,821+175
20 Oct 2026, 01:2054,646first 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 2 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.

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

“FILE MANTAN” (@FILE_MANTANBOT), 58,954 monthly users as measured 18 November 2026. Telegram Register, tgregister.com/channel/FILE_MANTANBOT.

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.