Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝙎𝙩𝙤𝙧𝙞𝙎𝙝𝙞𝙠

Channel

𝙎𝙩𝙤𝙧𝙞𝙎𝙝𝙞𝙠

@StoriShik

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

7,802subscribers

-78 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-1001209321754
TypeChannel
Username@StoriShik
Description✨ ﷽ ✨ سلام به کانال استوری شیک خوش اومدین‌‌❤ ارتباط جهت درج استوری در کانال📌 @Shm_C64 کانال های دیگه مون📌 @StoriLive @StoryCity20 @StoryCaffee پیج رسمی استوری شیک دراینستاگرام📌 https://instagram.com/StoriShik
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live25 August 2026
Measurements held8
On Telegramt.me/StoriShik

Growth

7,8027,8807,8416 August 2026 — 7,880 subscribers7 August 2026 — 7,876 subscribers10 August 2026 — 7,852 subscribers13 August 2026 — 7,833 subscribers17 August 2026 — 7,822 subscribers20 August 2026 — 7,811 subscribers24 August 2026 — 7,802 subscribers25 August 2026 — 7,802 subscribers6 August 202625 August 2026
8 measurements spanning 19 days, net -78. 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,790–7,892 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 21:317,802no change
24 Aug 2026, 21:377,802-9
20 Aug 2026, 22:367,811-11
17 Aug 2026, 11:537,822-11
13 Aug 2026, 14:197,833-19
10 Aug 2026, 18:287,852-24
7 Aug 2026, 08:527,876-4
6 Aug 2026, 12:067,880first reading

Engagement

No public post preview. We read this entry on 25 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.

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.

دنیای پروفایل ❥❥
@piic_prof · 48,728
Telegram ranks this channel #9 of 64 here — alongside 63 others — read 26 August 2026
استور‌ی فیک (اینستاگرام)
@storyefake · 124,738
Telegram ranks this channel #33 of 77 here — alongside 76 others — read 15 August 2026
عشق يعنى...🖤
@loveispublic · 58,308
Telegram ranks this channel #36 of 83 here — alongside 82 others — read 23 August 2026
حس خوب آرامش🌱
@Hesse_Arammesh · 76,388
Telegram ranks this channel #56 of 79 here — alongside 78 others — read 19 August 2026
دلبرونه 🙈
@Delbaronhe · 54,283
Telegram ranks this channel #60 of 76 here — alongside 75 others — read 24 August 2026

This channel appears in 5 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“𝙎𝙩𝙤𝙧𝙞𝙎𝙝𝙞𝙠” (@StoriShik), 7,802 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/StoriShik.

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.