Telegram RegisterThe public register of Telegram

Channel

Save Restricted Content

@SaveContentTempBot

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

7,452subscribers

+32 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001930863242
TypeChannel
Username@SaveContentTempBot
CreatedBetween 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/SaveContentTempBot

Growth

7,4207,4527,4366 August 2026 — 7,420 subscribers7 August 2026 — 7,424 subscribers9 August 2026 — 7,446 subscribers12 August 2026 — 7,452 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net +32. 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 7,415–7,457 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 06:177,452+6
9 Aug 2026, 15:167,446+22
7 Aug 2026, 01:387,424+4
6 Aug 2026, 14:487,420first reading

Engagement

19 posts held, back to 21 September 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
12.7%
avg views ÷ 7,452 subscribers
Avg views / post
950
1 post measured
Reaction rate
0.526%
reactions ÷ views · ER floor
Posts in window
1
of 19 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 August 2026
Posts held19 (21 September 20241 August 2026)
Views total950
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 17:26 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
3
Links
3

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

195 reactions across 19 posts, in 13 distinct kinds. The most used accounts for 31.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6231.8%
👍3920.0%
🔥2412.3%
👏178.72%
🤩115.64%
😭84.10%
🥰84.10%
🎉63.08%
😎63.08%
52.56%
😍42.05%
31.54%
💔21.03%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 195reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 21 September 2024 to 1 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

1 Aug 2026, 18:33 UTC950 views5 reactionsread 12 August 2026

Thrilled to announce a major milestone in our strategic video engagement ecosystem! We are excited to share that our Video Player has successfully pivoted to a new chapter of innovation, now fully empowering users to curate multi-audio experiences, select subtitles, or directly integrate custom subtitles for a truly personalized journey. The highlight of this evolution? Our platform is now delightfully aligned with

2🔥2👏1

13 May 2026, 09:58 UTC≈4,760 views4 reactionsread 12 August 2026

Someone tried DDOS attack on the service which lead to bandwidth limits. Service is Currently Up. Please use it Fairly Note: There are some issues with updated video player , will be fixed soon. fixed ~ Bot Link -> @AnimeTorrent_Bot ~ @SaveContentTempBot

2👍2

3 Mar 2026, 18:41 UTC≈8,150 views8 reactionsread 12 August 2026

If download stucks after starting and speed reaches 0 B/s , Please Change the Browser and use a different one . This Issue was Noticed in : 1. Microsoft Edge (Desktop, Windows)

5👍3

22 Dec 2025, 11:59 UTC≈11,700 views15 reactionsread 12 August 2026

We are now taking paid bot requests, starting from just 3$ / 249₹ ⚡ Come with proper documentation of the bot and it's features you need and we will quote the price and development time. After development, we can set things up and deploy it for you. But you have to provide your hosting. Free 6 Months Error Fix Support and Additional Features Requests on chargeable basis. To Start your Journey with us Message @Cod

👏543🔥2🤩1

1 Dec 2025, 15:51 UTC≈11,000 views6 reactionsread 12 August 2026

Something's either wrong with the hosting or with the bot itself. I am currently looking into it, will soon release a fix Fixed Enjoy 😋

🔥32👏1

22 Oct 2025, 13:56 UTC≈13,400 views11 reactionsread 12 August 2026

Free tier Changes : 1. Only 3 links per 24 hrs 2. Direct DL Link for files < 100MB 3. Adlinkfly Url for files above > 100MB 4. Reminder: All Files should comply with Telegram's TOS Do read this : https://t.me/SaveContentTempBot/72 Want Paid Access⚡ DM @AJMODS_BOT ~ Bot Link -> @AnimeTorrent_Bot ~ @SaveContentTempBot

7👍2👏2

3 Oct 2025, 18:29 UTC≈11,800 views7 reactionsread 12 August 2026

Its a Shame that people instantly spam large files at @AnimeTorrent_bot in the start of the month , even though we try to provide nearly 600GB of Bandwidth , it vanishes into thin air. Its only 3 days and its almost full. Login is Disabled. Some tweaks coming in the next month to keep the free service free for everyone to provide everyone a fair chance. Regards, @SaveContentTempBot

32👍1👏1

15 Sept 2025, 05:38 UTC≈10,900 views6 reactionsread 12 August 2026

Hello Everyone, We have completed our project @AnimeTorrent_bot , which allows to generate both private and public url. Now we are done with development phase. We will accept feature requests here on @AJMODS_bot and all requests will be looked upon every Sunday. Thanks for all the support , Have a Good Day . ~ @SaveContentTempBot

4🔥1🥰1

6 Sept 2025, 17:49 UTC≈10,200 views8 reactionsread 12 August 2026

Guys a quick note !! Please use session based link generation only when : 1. The Post is banned but is accessible to you. 2. Private Content 3. Forward Restricted Never Use Session based Link Generation Normally or you can risk your account getting Banned especially Newer Accounts .

😭8

4 Sept 2025, 04:33 UTC≈8,800 views7 reactionsread 12 August 2026

Major Update Coming 🎉 - Ability to Login and Download Private Save Restricted Content - Improved Security - Share the Post URL and download link will be generated . Updates will be Live Midnight ~ Bot Link -> @AnimeTorrent_Bot ~ @SaveContentTempBot

31🎉1🔥1😍1

3 Jul 2025, 10:37 UTC≈11,700 views14 reactionsread 12 August 2026

its a new month and bot is up and active. All Limits have been reset 😊 ~ Bot Link -> @AnimeTorrent_Bot ~ @SaveContentTempBot

🔥642👏1🤩1

1 Jun 2025, 06:58 UTC≈14,300 views21 reactionsread 12 August 2026

Yup the issue was caused due to Floodwait from Telegram. Adding another client fixed it temporarily ~ Enjoy 🙃

🥰65🎉3👏3💔2😍1😎1

Showing the 12 most recent of 19 posts we hold for @SaveContentTempBot. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 454,515 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 5 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Save Restricted Content” (@SaveContentTempBot), 7,452 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SaveContentTempBot.

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.