Channel
@fjsjshcrfs
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
245subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003506891333 |
|---|---|
| Type | Channel |
| Username | @fjsjshcrfs |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/fjsjshcrfs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 22:00 | 245 | -1 |
| 9 Sept 2026, 23:17 | 246 | -1 |
| 31 Aug 2026, 02:13 | 247 | -2 |
| 23 Aug 2026, 14:37 | 249 | -1 |
| 8 Aug 2026, 15:41 | 250 | +1 |
| 8 Aug 2026, 09:32 | 249 | no change |
| 7 Aug 2026, 18:31 | 249 | first reading |
20 posts held, back to 20 July 2026 — 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 20 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤬 | 1 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 1 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 20 July 2026 to 21 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
صفحة نيتسان شابيرا العبرية: إيميلي داماري، المحررة من الأسر، ترد على إغتيال أدهم نسمان:" هناك لحظات لا يعيد فيها التاريخ نفسه، بل يذكرنا بمبدأ.بعد مذبحة ميونيخ، أطلقت إسرائيل عملية "غضب الله" برسالة بسيطة؛ أولئك الذين يشاركون في قتل اليهود لن يتمكنوا من الاختباء إلى الأبد.حتى بعد السابع من أكتوبر، بقيت هذه الرسالة عالقة في أذهاننا.يجب أن يعلم كل مخرب شارك في المذبحة أو القتل أو الاختطاف أو حراسة الأسرى أن الحساب سيأ…
🤬1
قضى جيش الدفاع والشاباك على رئيس قسم العمليات في لواء مدينة غزة، الذي وجّه عملية الاقتحام من لواء مدينة غزة إلى داخل الأراضي الإسرائيلية خلال مجزرة السابع من أكتوبر الدموية، وشارك في احتجاز عدد كبير من المختطفين. ⭕️هاجم جيش الدفاع وجهاز الشاباك خلال نهاية الأسبوع (السبت) في منطقة مدينة غزة، وقضيا على المخرب أدهم إبراهيم شعبان نسمان، رئيس قسم العمليات في لواء مدينة غزة التابع لمنظمة حماس الإرهابية. ⭕️شغل نسمان خل…
Photo, posted without a caption
مسؤول حكومي أفغاني للجزيرة: مقتل 20 شخصا وإصابة 80 وفقدان أكثر من 100 جراء فيضانات في ولاية نورستان
• القناة 12 الصهيونية: بدء اجتماع الكابينيت الأمني والسياسي حول إيران بمشاركة كافة قادة الأجهزة الأمنية.
استهداف بصاروخ استطلاع على صلاح الدين محيط بركس اللجنة المصرية
شهداء ومصابون في استهداف بصاروخين استطلاع للطابق الأول من مبنى مستشفى اليمن السعيد.
إطلاق صفارات الإنذار في البحرين الآن
استهداف خيمة تتبع لقوة تأمين الشاحنات محيط مسجد معاوية في مواصي رفح
حالة اخلاء وخوف وسط النازحين في مخيم الارض الطيبة بخانيونس
استهداف جديد قرب شاليه شمس في مواصي مدينة رفح..
سكان منطقة بئر 19 في مواصي خانيونس يطالبون بإنشاء نقطة اسعاف بالقرب منهم بسبب كثرة الاصابات التي يتعرضون لها برصاص الاحتلال العشوائي والذي يطلق عليهم من مدينة رفح..
Showing the 12 most recent of 20 posts we hold for @fjsjshcrfs. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“غزة لحظة بلحظة🇵🇸” (@fjsjshcrfs), 245 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/fjsjshcrfs.
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.