Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐— ๐—ถ๐˜๐˜€๐˜‚๐—ฟ๐—ถ ๐—ž๐—ฎ๐—ป๐—ฟ๐—ผ๐—ท๐—ถ

Bot

๐— ๐—ถ๐˜๐˜€๐˜‚๐—ฟ๐—ถ ๐—ž๐—ฎ๐—ป๐—ฟ๐—ผ๐—ท๐—ถ

@mitsurii_kanroji1_bot

On this record: Topic ยท Growth ยท Engagement ยท Citations ยท Cite this entry

11,459monthly users

-14,573 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 ID8317459742
TypeBot
Username@mitsurii_kanroji1_bot
First recorded14 August 2026
Last confirmed live18 November 2026
Measurements held39
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/mitsurii_kanroji1_bot

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 99% 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,30930,23320,2717 August 2026 โ€” 26,032 monthly users9 August 2026 โ€” 26,103 monthly users12 August 2026 โ€” 27,712 monthly users13 August 2026 โ€” 28,243 monthly users14 August 2026 โ€” 28,243 monthly users16 August 2026 โ€” 28,662 monthly users18 August 2026 โ€” 29,592 monthly users19 August 2026 โ€” 30,233 monthly users22 August 2026 โ€” 29,794 monthly users26 August 2026 โ€” 28,435 monthly users28 August 2026 โ€” 25,806 monthly users31 August 2026 โ€” 24,079 monthly users2 September 2026 โ€” 22,523 monthly users3 September 2026 โ€” 21,008 monthly users8 September 2026 โ€” 18,456 monthly users11 September 2026 โ€” 16,994 monthly users13 September 2026 โ€” 15,391 monthly users14 September 2026 โ€” 13,482 monthly users16 September 2026 โ€” 12,091 monthly users18 September 2026 โ€” 10,309 monthly users24 September 2026 โ€” 10,635 monthly users3 October 2026 โ€” 16,474 monthly users8 October 2026 โ€” 18,232 monthly users12 October 2026 โ€” 19,822 monthly users14 October 2026 โ€” 20,935 monthly users16 October 2026 โ€” 21,926 monthly users18 October 2026 โ€” 23,468 monthly users20 October 2026 โ€” 24,534 monthly users22 October 2026 โ€” 24,924 monthly users26 October 2026 โ€” 24,303 monthly users30 October 2026 โ€” 21,124 monthly users31 October 2026 โ€” 19,635 monthly users3 November 2026 โ€” 18,785 monthly users5 November 2026 โ€” 17,806 monthly users6 November 2026 โ€” 16,694 monthly users8 November 2026 โ€” 15,933 monthly users11 November 2026 โ€” 14,772 monthly users15 November 2026 โ€” 13,594 monthly users18 November 2026 โ€” 11,459 monthly users11,4597 August 202618 November 2026
39 measurements spanning 102 days, net -14,573. 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 7,320โ€“33,222 and does not start at zero.
Measurement log โ€” every monthly users count we have recorded, most recent 20 of 39
Measured (UTC)Monthly usersChange
18 Nov 2026, 04:5711,459-2,135
15 Nov 2026, 00:1713,594-1,178
11 Nov 2026, 22:0014,772-1,161
8 Nov 2026, 12:4915,933-761
6 Nov 2026, 08:2916,694-1,112
5 Nov 2026, 08:1017,806-979
3 Nov 2026, 04:3118,785-850
31 Oct 2026, 07:1919,635-1,489
30 Oct 2026, 09:2821,124-3,179
26 Oct 2026, 03:0124,303-621
22 Oct 2026, 07:3724,924+390
20 Oct 2026, 22:2824,534+1,066
18 Oct 2026, 22:2623,468+1,542
16 Oct 2026, 17:0521,926+991
14 Oct 2026, 11:1820,935+1,113
12 Oct 2026, 20:4119,822+1,590
8 Oct 2026, 08:3918,232+1,758
3 Oct 2026, 19:4016,474+5,839
24 Sept 2026, 23:2110,635+326
18 Sept 2026, 20:4010,309first 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 1 registered channel โ€” 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.

โ€œ๐— ๐—ถ๐˜๐˜€๐˜‚๐—ฟ๐—ถ ๐—ž๐—ฎ๐—ป๐—ฟ๐—ผ๐—ท๐—ถโ€ (@mitsurii_kanroji1_bot), 11,459 monthly users as measured 18 November 2026. Telegram Register, tgregister.com/channel/mitsurii_kanroji1_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.