17 Oct 2022, 01:33 UTC461 viewsread 8 August 2026
اذكرو فقيدتي بدعوه🤎
Channel
﮼غيمة .
@sss48
On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry
158subscribers
-2 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001063443886 |
|---|---|
| Type | Channel |
| Username | @sss48 |
| Created | Between 1 May 2016 and 28 February 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/sss48 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 03:05 | 158 | -1 |
| 14 Aug 2026, 19:55 | 159 | -1 |
| 8 Aug 2026, 17:15 | 160 | no change |
| 5 Aug 2026, 23:02 | 160 | first reading |
Engagement
20 posts held, back to 5 March 2021 — the 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 20 posts for this entry, the most recent from 17 October 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 26s
- Average length
- 26s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
17 Oct 2022, 01:33 UTC466 viewsread 8 August 2026
Video
مرت ثلاث سنين وكنها ثلاث ايام😔.
10 Oct 2022, 18:23 UTC519 viewsread 8 August 2026
من لا يداري خاطرك لا تداريه بعض المدارى للخواطر مذله🤝🏻
27 Aug 2022, 02:03 UTC514 viewsread 8 August 2026
تشهد عليّ هزايمي إني حاولت*
2 Apr 2022, 21:13 UTC629 viewsread 8 August 2026
مَررنا بالأسوء ليس صَعباً هذهِ المرة ، سَنتخطى.
2 Apr 2022, 21:13 UTC627 viewsread 8 August 2026
ليرحل من يشاء فالله لا يبعد إلا السيئين .
9 Feb 2022, 22:26 UTC656 viewsread 8 August 2026
لقد عز عليّ قلبي جدًا، فلا يقربه بعد اليوم ظالم ولا طيّب
17 Jan 2022, 18:14 UTC744 viewsread 8 August 2026
"أودّهُ، حدّ أنني أودّ ان أنوب عنه في أحزانه
31 Dec 2021, 18:43 UTC759 viewsread 8 August 2026
الإنسحاب من حياة بعض الأشخاص لا يعني دائما الإستسلام بل غالبا يعني أنك صمدت طويلاً من أجل شيء لا يستحق.!
31 Dec 2021, 18:42 UTC725 viewsread 8 August 2026
"أتمنى أن يكون أحدهم فخور بوجودي في حياته، ولا يراني عبئًا كَما أشعر"
16 Oct 2021, 16:57 UTC787 viewsread 8 August 2026
"مثل إللي جُوفه يحترق ؟ — ولاقدر يقول شي"
7 Aug 2021, 00:40 UTC826 viewsread 8 August 2026
- أحد يدور لك خطاً و أنت ماخطيت و أحد يدور لك عذر و أنت مخطي
Showing the 12 most recent of 20 posts we hold for @sss48. 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.
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.
“ ﮼غيمة .” (@sss48), 158 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/sss48.
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.