Telegram RegisterThe public register of Telegram
Telegram profile photo for بوت سناب تيوب | Bot

Bot

بوت سناب تيوب | Bot

@J3KBOT

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

12,355monthly users

-205 since we began measuring on 6 August 2026

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

Register entry

Telegram ID5578267242
TypeBot
Username@J3KBOT
First recorded20 August 2026
Last confirmed live26 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/J3KBOT

Growth

12,34212,79712,569.56 August 2026 — 12,560 monthly users6 August 2026 — 12,561 monthly users8 August 2026 — 12,554 monthly users10 August 2026 — 12,664 monthly users11 August 2026 — 12,717 monthly users12 August 2026 — 12,732 monthly users14 August 2026 — 12,797 monthly users16 August 2026 — 12,643 monthly users17 August 2026 — 12,595 monthly users18 August 2026 — 12,342 monthly users20 August 2026 — 12,466 monthly users20 August 2026 — 12,466 monthly users21 August 2026 — 12,476 monthly users22 August 2026 — 12,423 monthly users25 August 2026 — 12,361 monthly users26 August 2026 — 12,355 monthly users12,3556 August 202626 August 2026
16 measurements spanning 20 days, net -205. 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 12,274–12,865 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
26 Aug 2026, 05:0412,355-6
25 Aug 2026, 04:2812,361-62
22 Aug 2026, 13:4312,423-53
21 Aug 2026, 05:1612,476+10
20 Aug 2026, 18:2912,466no change
20 Aug 2026, 08:2412,466+124
18 Aug 2026, 11:2312,342-253
17 Aug 2026, 12:0412,595-48
16 Aug 2026, 02:1312,643-154
14 Aug 2026, 10:3712,797+65
12 Aug 2026, 02:0612,732+15
11 Aug 2026, 00:1112,717+53
10 Aug 2026, 00:5512,664+110
8 Aug 2026, 23:1212,554-7
6 Aug 2026, 22:2212,561+1
6 Aug 2026, 16:4112,560first 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 4 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 26 August 2026 — this entry's latest reading, not the date you are reading this.

“بوت سناب تيوب | Bot” (@J3KBOT), 12,355 monthly users as measured 26 August 2026. Telegram Register, tgregister.com/channel/J3KBOT.

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.