Telegram RegisterThe public register of Telegram

Channel

Info & Storage!

@enstorage

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

3subscribers

+0 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001403464840
TypeChannel
Username@enstorage
Descriptionin @ENHAsenada
CreatedBetween 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/enstorage

Growth

314 Aug 2026, 19:04 — 3 subscribers14 Aug 2026, 19:32 — 3 subscribers14 Aug 2026, 19:0414 Aug 2026, 19:32
2 measurements taken within a single day. 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 2–4 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:323no change
14 Aug 2026, 19:043first reading

Engagement

18 posts held, back to 6 November 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 18 March 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
49
Links
3

Lifetime counters from Telegram’s own channel header, read 14 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.

Recent posts

18 Mar 2022, 13:56 UTC107 viewsread 14 August 2026

Hai maaf, saya ingin memberitahukan bot kami @ENHAsenada_bot mengalami kesalahan (error), bot kami tidak menerima chat apapun dari tanggal 20 Januari. Maaf untuk kalian yang mungkin chat admin ke bot tersebut dari tanggal 20 Januari tapi tidak menerima respon apapun, karena dari tanggal itu bot kami tidak menerima satu chat apapun. Dan untuk kalian yang ingin chat admin atau memberikan semangat, kritsar, curhat, at

11 Nov 2021, 10:17 UTC357 viewsread 14 August 2026

yang tidak pake format saat request, saya tidak akan buatkan!

11 Nov 2021, 10:13 UTC348 viewsread 14 August 2026

btw kalo req kalian belum dibuatin sampe sekarang mungkin itu karena req kalian terlalu susah untuk dibuatkan atau karena adm lupa sama req kalian, jadi yang belum dibuatin reqnya bisa chat ulang bot! okay^^

11 Nov 2021, 10:04 UTC337 viewsread 14 August 2026

ohiya, kalo kalian mau chat bot terus belum dibales jangan asal block dulu yaa.. tunggu pasti bakal dibales, dan kalo belum dibales lebih dari 2 hari kalian bisa chat ulang bot mungkin aja chat kalian tenggelam atau admnya lagi sibuk^^

11 Nov 2021, 04:17 UTC283 viewsread 14 August 2026
Forwarded from @ENHAsenada

Hii? aku mau infoin sesuatu, budayakan membaca sampai selesai. Pict @ENHAsenada boleh dijadikan konten tiktok, story atau semacamnya tanpa izin dan di berikan cr, kecuali kalo pict ENHAsenada mau di repost ke ch help, akun pinterest atau semacamnya, kalian wajib izin dan memberikan cr dengan baik dan benar. [ kalian bisa langsung izin ke bot kami @ENHAsenada_bot ] kalian juga bisa memberikan kami semangat atau saran

11 Nov 2021, 04:07 UTC≈2,680 viewsread 14 August 2026

haloo! buat yang nanya, kalau buat konten tiktok harus di kasi cr ngga kak? itu seterah kalian ya mau ngasi cr atau ngga, ngga di kasi cr juga gapapa BUT jika ada yang bertanya pict nya dari mana kalian jawabnya dari ch @ENHAsenada ya, terimakasih.

Showing the 12 most recent of 18 posts we hold for @enstorage. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“Info & Storage!” (@enstorage), 3 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/enstorage.

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.