Channel
@yam0sha
On this record: Growth · Engagement · Posts · Citations · Cite this entry
126subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001192433453 |
|---|---|
| Type | Channel |
| Username | @yam0sha |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 9 September 2026 |
| On Telegram | t.me/yam0sha |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 10:15 | 126 | -1 |
| 22 Aug 2026, 22:18 | 127 | -1 |
| 9 Aug 2026, 01:46 | 128 | no change |
| 6 Aug 2026, 20:39 | 128 | first reading |
19 posts held, back to 21 March 2022 — 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 page of 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 19 posts for this entry, the most recent from 17 June 2025. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 7 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 30 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
"لا تَحزني فالحُزن لم يُخلق لكِ صدري لهَمكِ قبلَ حُضنك يحملُهْ مَن ذا الذي يطغى عليك ويُحزنك؟ أولم يَرى حُسناً تجلَّا فأخجلهْ؟"
وَأَنَّ سَعيَهُ سَوفَ يُرى"
صباح الخير .. مبدئياً كده حسبي الله ونعم الوكيل في التعليم
ليس لهُ مكانٌ في القلب ، لا لهُ القلب كله.
<3
تذهب لأنك تعبت وتأتي لإنك تُحبه.
امرأتان لا يقوى الرجل على نسيانهُما : المرأة التي منحته العاطفه بسخاء ، و المرأة التي أحرق نفسه من أجل أن تلتفت إليه ، و لم تفعل .
" إًنَّ اللهَ يُشَدِّدُ ليُخَفِّف "
مُش مُهم الحاجة تعدي أو لا، المُهم إنك تَلاقي حَد ماسك إيدك و بيعديها مَعاك
Showing the 12 most recent of 19 posts we hold for @yam0sha. 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.
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“يَ” (@yam0sha), 126 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/yam0sha.
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.