Telegram RegisterThe public register of Telegram
Telegram profile photo for بوت تنزيل ستوريات انستا VJ Plus

Bot

بوت تنزيل ستوريات انستا VJ Plus

@VjBoT

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

291,867monthly users

-20,489 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID1962436765
TypeBot
Username@VjBoT
First recorded6 August 2026
Last confirmed live26 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/VjBoT

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 8 August 2026 and assigned it the closest of 31 fixed categories, at 40% 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

291,867312,356302,111.56 August 2026 — 312,356 monthly users6 August 2026 — 312,356 monthly users6 August 2026 — 311,538 monthly users7 August 2026 — 310,908 monthly users8 August 2026 — 309,879 monthly users9 August 2026 — 308,494 monthly users10 August 2026 — 308,088 monthly users11 August 2026 — 307,598 monthly users12 August 2026 — 307,866 monthly users13 August 2026 — 307,851 monthly users15 August 2026 — 307,598 monthly users16 August 2026 — 307,752 monthly users17 August 2026 — 307,607 monthly users18 August 2026 — 307,093 monthly users19 August 2026 — 307,115 monthly users20 August 2026 — 306,189 monthly users22 August 2026 — 304,531 monthly users23 August 2026 — 302,528 monthly users25 August 2026 — 301,391 monthly users26 August 2026 — 296,765 monthly users27 August 2026 — 295,053 monthly users28 August 2026 — 292,717 monthly users29 August 2026 — 292,513 monthly users30 August 2026 — 299,734 monthly users31 August 2026 — 300,017 monthly users2 September 2026 — 299,681 monthly users3 September 2026 — 299,558 monthly users5 September 2026 — 298,804 monthly users8 September 2026 — 296,987 monthly users11 September 2026 — 296,765 monthly users13 September 2026 — 296,596 monthly users14 September 2026 — 295,043 monthly users16 September 2026 — 294,794 monthly users19 September 2026 — 294,309 monthly users26 September 2026 — 291,867 monthly users6 August 202626 September 2026
35 measurements spanning 51 days, net -20,489. 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 288,794–315,429 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 35
Measured (UTC)Monthly usersChange
26 Sept 2026, 06:57291,867-2,442
19 Sept 2026, 08:16294,309-485
16 Sept 2026, 20:19294,794-249
14 Sept 2026, 22:38295,043-1,553
13 Sept 2026, 06:15296,596-169
11 Sept 2026, 05:55296,765-222
8 Sept 2026, 08:17296,987-1,817
5 Sept 2026, 01:21298,804-754
3 Sept 2026, 08:58299,558-123
2 Sept 2026, 00:43299,681-336
31 Aug 2026, 22:05300,017+283
30 Aug 2026, 23:18299,734+7,221
29 Aug 2026, 20:26292,513-204
28 Aug 2026, 23:34292,717-2,336
27 Aug 2026, 19:57295,053-1,712
26 Aug 2026, 22:44296,765-4,626
25 Aug 2026, 02:38301,391-1,137
23 Aug 2026, 19:05302,528-2,003
22 Aug 2026, 01:34304,531-1,658
20 Aug 2026, 21:35306,189first 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

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 28 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“بوت تنزيل ستوريات انستا VJ Plus” (@VjBoT), 291,867 monthly users as measured 26 September 2026. Telegram Register, tgregister.com/channel/VjBoT.

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.