Telegram RegisterThe public register of Telegram
Telegram profile photo for PremTempStorage

Channel

PremTempStorage

@PPStorage

On this record: Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

18,289subscribers

+299 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 ID-1002117094283
TypeChannel
Username@PPStorage
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live22 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/PPStorage

Growth

17,99018,28918,139.56 August 2026 — 17,990 subscribers7 August 2026 — 17,998 subscribers8 August 2026 — 18,020 subscribers9 August 2026 — 18,025 subscribers10 August 2026 — 18,058 subscribers11 August 2026 — 18,092 subscribers12 August 2026 — 18,105 subscribers13 August 2026 — 18,127 subscribers14 August 2026 — 18,148 subscribers16 August 2026 — 18,175 subscribers17 August 2026 — 18,175 subscribers17 August 2026 — 18,194 subscribers18 August 2026 — 18,229 subscribers19 August 2026 — 18,245 subscribers20 August 2026 — 18,261 subscribers22 August 2026 — 18,289 subscribers6 August 202622 August 2026
16 measurements spanning 15 days, net +299. 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 17,945–18,334 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 01:4818,289+28
20 Aug 2026, 17:0218,261+16
19 Aug 2026, 19:2418,245+16
18 Aug 2026, 21:3418,229+35
17 Aug 2026, 20:0618,194+19
17 Aug 2026, 10:0918,175no change
16 Aug 2026, 16:5418,175+27
14 Aug 2026, 22:1718,148+21
13 Aug 2026, 12:1718,127+22
12 Aug 2026, 13:5518,105+13
11 Aug 2026, 16:5818,092+34
10 Aug 2026, 14:3618,058+33
9 Aug 2026, 12:3418,025+5
8 Aug 2026, 14:5718,020+22
7 Aug 2026, 12:5717,998+8
6 Aug 2026, 18:4717,990first reading

Engagement

No public post preview. We read this entry on 17 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Citation-graph rank

Citation-graph rank — 251,103 of 1,584,142entries 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 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

AE Storage
@AEStorage · 86,058
Telegram ranks this channel #10 of 70 here — alongside 69 others — read 18 August 2026
Premiere Pro | Motion Design
@premiere_pro · 64,191
Telegram ranks this channel #15 of 75 here — alongside 74 others — read 21 August 2026
After Effects Templates
@AETemp · 183,041
Telegram ranks this channel #42 of 77 here — alongside 76 others — read 13 August 2026
After Effects | Motion Design
@after_effects_motion · 65,263
Telegram ranks this channel #67 of 78 here — alongside 77 others — read 21 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“PremTempStorage” (@PPStorage), 18,289 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/PPStorage.

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.