Telegram RegisterThe public register of Telegram
Telegram profile photo for MOCHI [ BOT NOKOS ]

Bot

MOCHI [ BOT NOKOS ]

@MochiOtpBot

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

36,710monthly users

-10,682 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 ID8181589193
TypeBot
Username@MochiOtpBot
First recorded12 August 2026
Last confirmed live17 September 2026
Measurements held24
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/MochiOtpBot

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 why it has no browse page of its own yet.

Growth

36,71047,39242,0517 August 2026 — 47,392 monthly users9 August 2026 — 46,839 monthly users11 August 2026 — 47,049 monthly users12 August 2026 — 47,049 monthly users13 August 2026 — 46,696 monthly users14 August 2026 — 46,661 monthly users16 August 2026 — 45,497 monthly users17 August 2026 — 45,326 monthly users19 August 2026 — 45,312 monthly users21 August 2026 — 45,037 monthly users24 August 2026 — 44,955 monthly users25 August 2026 — 44,608 monthly users27 August 2026 — 44,292 monthly users29 August 2026 — 44,501 monthly users30 August 2026 — 43,242 monthly users31 August 2026 — 43,178 monthly users1 September 2026 — 42,822 monthly users3 September 2026 — 42,433 monthly users6 September 2026 — 40,384 monthly users9 September 2026 — 39,628 monthly users12 September 2026 — 38,371 monthly users13 September 2026 — 37,513 monthly users15 September 2026 — 36,899 monthly users17 September 2026 — 36,710 monthly users7 August 202617 September 2026
24 measurements spanning 41 days, net -10,682. 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,108–48,994 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 24
Measured (UTC)Monthly usersChange
17 Sept 2026, 08:4036,710-189
15 Sept 2026, 06:1836,899-614
13 Sept 2026, 18:1937,513-858
12 Sept 2026, 01:0038,371-1,257
9 Sept 2026, 13:5739,628-756
6 Sept 2026, 04:3640,384-2,049
3 Sept 2026, 22:2142,433-389
1 Sept 2026, 10:3342,822-356
31 Aug 2026, 13:3743,178-64
30 Aug 2026, 10:1643,242-1,259
29 Aug 2026, 09:2844,501+209
27 Aug 2026, 10:4544,292-316
25 Aug 2026, 13:0244,608-347
24 Aug 2026, 14:0844,955-82
21 Aug 2026, 12:4645,037-275
19 Aug 2026, 16:1645,312-14
17 Aug 2026, 13:2445,326-171
16 Aug 2026, 08:4745,497-1,164
14 Aug 2026, 23:3746,661-35
13 Aug 2026, 17:2946,696first 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“MOCHI [ BOT NOKOS ]” (@MochiOtpBot), 36,710 monthly users as measured 17 September 2026. Telegram Register, tgregister.com/channel/MochiOtpBot.

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.