Telegram RegisterThe public register of Telegram
Telegram profile photo for بوت تحميل ستوريات من انستا

Bot

بوت تحميل ستوريات من انستا

@VAFBoT

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

456,820monthly users

-188,795 since we began measuring on 6 August 2026

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

Register entry

Telegram ID5355257847
TypeBot
Username@VAFBoT
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/VAFBoT

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 56% 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

456,820645,615551,217.56 August 2026 — 645,615 monthly users6 August 2026 — 645,615 monthly users8 August 2026 — 632,849 monthly users9 August 2026 — 612,045 monthly users10 August 2026 — 608,290 monthly users11 August 2026 — 608,465 monthly users12 August 2026 — 611,234 monthly users13 August 2026 — 612,640 monthly users14 August 2026 — 614,248 monthly users16 August 2026 — 620,794 monthly users17 August 2026 — 632,475 monthly users18 August 2026 — 629,183 monthly users19 August 2026 — 627,549 monthly users20 August 2026 — 626,937 monthly users21 August 2026 — 624,152 monthly users22 August 2026 — 595,037 monthly users24 August 2026 — 592,332 monthly users25 August 2026 — 590,402 monthly users26 August 2026 — 589,425 monthly users27 August 2026 — 579,098 monthly users28 August 2026 — 578,965 monthly users29 August 2026 — 578,890 monthly users30 August 2026 — 568,034 monthly users31 August 2026 — 566,860 monthly users1 September 2026 — 566,001 monthly users2 September 2026 — 565,696 monthly users3 September 2026 — 565,421 monthly users5 September 2026 — 565,581 monthly users8 September 2026 — 562,580 monthly users11 September 2026 — 558,295 monthly users13 September 2026 — 545,316 monthly users14 September 2026 — 539,815 monthly users16 September 2026 — 510,579 monthly users18 September 2026 — 484,101 monthly users25 September 2026 — 456,820 monthly users6 August 202625 September 2026
35 measurements spanning 49 days, net -188,795. 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 428,501–673,934 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 35
Measured (UTC)Monthly usersChange
25 Sept 2026, 02:18456,820-27,281
18 Sept 2026, 18:37484,101-26,478
16 Sept 2026, 10:02510,579-29,236
14 Sept 2026, 17:17539,815-5,501
13 Sept 2026, 03:19545,316-12,979
11 Sept 2026, 04:18558,295-4,285
8 Sept 2026, 10:19562,580-3,001
5 Sept 2026, 04:15565,581+160
3 Sept 2026, 10:24565,421-275
2 Sept 2026, 08:06565,696-305
1 Sept 2026, 09:44566,001-859
31 Aug 2026, 10:04566,860-1,174
30 Aug 2026, 10:03568,034-10,856
29 Aug 2026, 10:13578,890-75
28 Aug 2026, 07:37578,965-133
27 Aug 2026, 09:13579,098-10,327
26 Aug 2026, 12:28589,425-977
25 Aug 2026, 14:04590,402-1,930
24 Aug 2026, 14:37592,332-2,705
22 Aug 2026, 19:34595,037first 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 26 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 23 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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“بوت تحميل ستوريات من انستا” (@VAFBoT), 456,820 monthly users as measured 25 September 2026. Telegram Register, tgregister.com/channel/VAFBoT.

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.