Telegram RegisterThe public register of Telegram
Telegram profile photo for JUMMUU BOT⚡️

Channel

JUMMUU BOT⚡️

@jummuubot

Has discussion group

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

2,379subscribers

-115 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002351045660
TypeChannel
Username@jummuubot
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 September 2026
Last confirmed live6 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/jummuubot

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 16 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 why it has no browse page of its own yet.

Growth

2,3792,4942,436.57 August 2026 — 2,494 subscribers11 August 2026 — 2,486 subscribers14 August 2026 — 2,482 subscribers18 August 2026 — 2,470 subscribers21 August 2026 — 2,464 subscribers25 August 2026 — 2,458 subscribers27 August 2026 — 2,453 subscribers30 August 2026 — 2,450 subscribers2 September 2026 — 2,446 subscribers6 September 2026 — 2,434 subscribers11 September 2026 — 2,424 subscribers14 September 2026 — 2,414 subscribers16 September 2026 — 2,414 subscribers19 September 2026 — 2,407 subscribers29 September 2026 — 2,393 subscribers6 October 2026 — 2,379 subscribers7 August 20266 October 2026
16 measurements spanning 60 days, net -115. 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 2,362–2,511 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 20:202,379-14
29 Sept 2026, 20:572,393-14
19 Sept 2026, 13:422,407-7
16 Sept 2026, 14:472,414no change
14 Sept 2026, 22:172,414-10
11 Sept 2026, 07:202,424-10
6 Sept 2026, 07:362,434-12
2 Sept 2026, 00:342,446-4
30 Aug 2026, 10:032,450-3
27 Aug 2026, 19:052,453-5
25 Aug 2026, 00:152,458-6
21 Aug 2026, 06:542,464-6
18 Aug 2026, 05:522,470-12
14 Aug 2026, 23:152,482-4
11 Aug 2026, 04:512,486-8
7 Aug 2026, 19:132,494first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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.

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

“JUMMUU BOT⚡️” (@jummuubot), 2,379 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/jummuubot.

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.