Telegram RegisterThe public register of Telegram
Telegram profile photo for Save Video Bot - скачать видео

Bot

Save Video Bot - скачать видео

@savegrabbot

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

46,077monthly users

+21,749 since we began measuring on 9 August 2026

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

Register entry

Telegram ID8572620044
TypeBot
Username@savegrabbot
First recorded15 August 2026
Last confirmed live28 October 2026
Measurements held37
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/savegrabbot

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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 the other topics.

Growth

22,99346,07734,5359 August 2026 — 24,328 monthly users11 August 2026 — 24,100 monthly users12 August 2026 — 24,001 monthly users13 August 2026 — 23,858 monthly users14 August 2026 — 23,786 monthly users15 August 2026 — 23,786 monthly users16 August 2026 — 22,993 monthly users17 August 2026 — 23,651 monthly users18 August 2026 — 23,536 monthly users20 August 2026 — 23,460 monthly users21 August 2026 — 23,504 monthly users24 August 2026 — 23,552 monthly users25 August 2026 — 23,455 monthly users27 August 2026 — 23,485 monthly users28 August 2026 — 23,571 monthly users29 August 2026 — 23,720 monthly users31 August 2026 — 23,812 monthly users3 September 2026 — 23,841 monthly users5 September 2026 — 24,209 monthly users8 September 2026 — 24,135 monthly users11 September 2026 — 23,632 monthly users13 September 2026 — 24,327 monthly users14 September 2026 — 24,407 monthly users18 September 2026 — 28,233 monthly users2 October 2026 — 33,945 monthly users7 October 2026 — 35,893 monthly users11 October 2026 — 41,333 monthly users14 October 2026 — 42,783 monthly users15 October 2026 — 43,338 monthly users16 October 2026 — 43,929 monthly users18 October 2026 — 44,416 monthly users21 October 2026 — 44,214 monthly users22 October 2026 — 44,323 monthly users24 October 2026 — 44,869 monthly users26 October 2026 — 45,294 monthly users27 October 2026 — 45,812 monthly users28 October 2026 — 46,077 monthly users9 August 202628 October 2026
37 measurements spanning 80 days, net +21,749. 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 19,530–49,540 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 37
Measured (UTC)Monthly usersChange
28 Oct 2026, 10:5946,077+265
27 Oct 2026, 09:0645,812+518
26 Oct 2026, 06:0545,294+425
24 Oct 2026, 04:1744,869+546
22 Oct 2026, 07:4144,323+109
21 Oct 2026, 04:0044,214-202
18 Oct 2026, 03:5744,416+487
16 Oct 2026, 03:3743,929+591
15 Oct 2026, 06:2043,338+555
14 Oct 2026, 03:0642,783+1,450
11 Oct 2026, 17:2041,333+5,440
7 Oct 2026, 08:5735,893+1,948
2 Oct 2026, 10:5533,945+5,712
18 Sept 2026, 17:5828,233+3,826
14 Sept 2026, 17:0124,407+80
13 Sept 2026, 03:5524,327+695
11 Sept 2026, 09:0123,632-503
8 Sept 2026, 15:1424,135-74
5 Sept 2026, 06:3824,209+368
3 Sept 2026, 12:1723,841first 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 2 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 28 October 2026 — this entry's latest reading, not the date you are reading this.

“Save Video Bot - скачать видео” (@savegrabbot), 46,077 monthly users as measured 28 October 2026. Telegram Register, tgregister.com/channel/savegrabbot.

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.