Telegram RegisterThe public register of Telegram
Telegram profile photo for سائد السويركي .. قناة آر تي Saed swerki Rt

Channel

سائد السويركي .. قناة آر تي Saed swerki Rt

@saedelswerki

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

16,775subscribers

-1,122 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001589210341
TypeChannel
Username@saedelswerki
Descriptionمراسل قناة آر تي في قطاع غزة
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live5 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/saedelswerki

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 80% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

16,77517,89717,3366 August 2026 — 17,897 subscribers6 August 2026 — 17,896 subscribers7 August 2026 — 17,880 subscribers8 August 2026 — 17,865 subscribers9 August 2026 — 17,858 subscribers11 August 2026 — 17,847 subscribers12 August 2026 — 17,825 subscribers13 August 2026 — 17,804 subscribers14 August 2026 — 17,784 subscribers16 August 2026 — 17,769 subscribers17 August 2026 — 17,749 subscribers18 August 2026 — 17,736 subscribers19 August 2026 — 17,725 subscribers20 August 2026 — 17,712 subscribers21 August 2026 — 17,700 subscribers22 August 2026 — 17,680 subscribers24 August 2026 — 17,658 subscribers25 August 2026 — 17,641 subscribers26 August 2026 — 17,631 subscribers27 August 2026 — 17,617 subscribers28 August 2026 — 17,603 subscribers29 August 2026 — 17,585 subscribers30 August 2026 — 17,577 subscribers31 August 2026 — 17,560 subscribers1 September 2026 — 17,550 subscribers2 September 2026 — 17,530 subscribers4 September 2026 — 17,514 subscribers6 September 2026 — 17,483 subscribers9 September 2026 — 17,457 subscribers12 September 2026 — 17,450 subscribers13 September 2026 — 17,428 subscribers15 September 2026 — 17,414 subscribers17 September 2026 — 17,392 subscribers27 September 2026 — 17,288 subscribers4 October 2026 — 17,191 subscribers9 October 2026 — 17,123 subscribers13 October 2026 — 17,069 subscribers14 October 2026 — 17,051 subscribers15 October 2026 — 17,037 subscribers16 October 2026 — 17,021 subscribers17 October 2026 — 17,009 subscribers18 October 2026 — 16,995 subscribers19 October 2026 — 16,992 subscribers20 October 2026 — 16,975 subscribers21 October 2026 — 16,960 subscribers23 October 2026 — 16,953 subscribers24 October 2026 — 16,942 subscribers25 October 2026 — 16,926 subscribers26 October 2026 — 16,913 subscribers27 October 2026 — 16,911 subscribers28 October 2026 — 16,901 subscribers29 October 2026 — 16,886 subscribers30 October 2026 — 16,870 subscribers31 October 2026 — 16,849 subscribers1 November 2026 — 16,838 subscribers1 November 2026 — 16,827 subscribers3 November 2026 — 16,810 subscribers4 November 2026 — 16,802 subscribers4 November 2026 — 16,791 subscribers5 November 2026 — 16,775 subscribers6 August 20265 November 2026
60 measurements spanning 91 days, net -1,122. 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 16,607–18,065 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
5 Nov 2026, 21:2616,775-16
4 Nov 2026, 23:0616,791-11
4 Nov 2026, 00:2916,802-8
3 Nov 2026, 00:1916,810-17
1 Nov 2026, 23:3616,827-11
1 Nov 2026, 02:5516,838-11
31 Oct 2026, 03:1716,849-21
30 Oct 2026, 00:5016,870-16
29 Oct 2026, 03:5016,886-15
28 Oct 2026, 02:4716,901-10
27 Oct 2026, 00:3916,911-2
26 Oct 2026, 01:4016,913-13
25 Oct 2026, 03:0616,926-16
24 Oct 2026, 00:3416,942-11
23 Oct 2026, 02:2716,953-7
21 Oct 2026, 22:2716,960-15
20 Oct 2026, 20:5916,975-17
19 Oct 2026, 18:5116,992-3
18 Oct 2026, 19:0716,995-14
17 Oct 2026, 19:0817,009first reading

Engagement

886 posts held, back to 5 August 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 62 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.07%
avg views ÷ 16,775 subscribers
Avg views / post
348
104 posts measured
Reaction rate
0.181%
reactions ÷ views · ER floor
Posts in window
104
of 886 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 21 of 104 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 November 2026
Posts held886 (5 August 2026 – 6 November 2026)
Views total36,174
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 04:28 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈28,500
Videos
≈16,600
Links
≈3,380

Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1h 05m
Average length
57s

Measured directly from 69 videos 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.

Reaction mix

192 reactions across 152 posts, in 11 distinct kinds. The most used accounts for 79.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤15379.7%
🤬105.21%
💔94.69%
👍63.13%
😢42.08%
😁31.56%
😱21.04%
🤔21.04%
🔥10.521%
🤣10.521%
🤨10.521%

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 182 of the 886 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 192 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 886 most recent posts we hold, published 5 August 2026 to 6 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 104 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

6 Nov 2026, 00:55 UTC132 viewsread 6 November 2026

تقدمت آليات عسكرية إسرائيلية باتجاه محيط وادي أبو رشيد، في المناطق الشرقية الواقعة بين مخيم المغازي وبلدة المصدر وسط قطاع غزة، بالتزامن مع إطلاق نار وانفجارات في المنطقة

6 Nov 2026, 00:51 UTC128 viewsread 6 November 2026

الإنفجار الأخير ناجم عن قيام الإحتلال بتفجير مكعب مفخخ محيط رمزون السنافور شرقي مدينة غزة..

6 Nov 2026, 00:47 UTC129 viewsread 6 November 2026

آليات الاحتلال تطلق النار بشكل كثيف اتجاه منازل المواطنين شرق مخيم المغازي وسط قطاع غزة

5 Nov 2026, 17:01 UTC451 viewsread 6 November 2026

الدولار يصل لأعلى مستوى له منذ أشهر مقابل الشيكل الدولار = 3.20 شيكل.

5 Nov 2026, 16:59 UTC475 views0 reactionsread 6 November 2026
Video

استهداف مجموعة مواطنين في مخيم الشاطئ غرب مدينة غزة

5 Nov 2026, 16:58 UTC383 viewsread 6 November 2026
Video

استهداف في مخيم الشاطئ غرب مدينة غزة، أسفر عن وصول شهيد وعدد من الإصابات إلى مجمع الشفاء الطبي

5 Nov 2026, 16:54 UTC353 viewsread 6 November 2026

وصول شهيد لمستشفى الشفاء الشهيد محمد القيشاوي وإصابتين خطيرة

5 Nov 2026, 16:51 UTC358 viewsread 6 November 2026

وزارة الصحة بغزة: - بلغ إجمالي ما وصل إلى مستشفيات قطاع غزة خلال الـ24 ساعة الماضية: 5 إصابات. - منذ وقف إطلاق النار في 11 أكتوبر 2025: إجمالي الشهداء: 1,602 شهيدًا. إجمالي الإصابات: 5,799 إصابة. إجمالي حالات الانتشال: 847 شهيدًا. - الحصيلة التراكمية منذ بداية العدوان: إجمالي الشهداء: 74,618 إجمالي الإصابات: 175,925

5 Nov 2026, 16:38 UTC306 viewsread 6 November 2026

اصابات بينها خطيرة باستهداف مجموعة مواطنين بمحيط ميدان الشهداء في مخيم الشاطئ غرب غزة

5 Nov 2026, 15:48 UTC380 viewsread 6 November 2026

(محدث) مجمع الشفاء الطبي: مصابون في غارة إسرائيلية استهدفت فلسطينيين في مخيم الشاطئ غربي مدينة غزة

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

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.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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.

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.

🇪🇬 اخبار معبر رفح - رفح نيوز🇵🇸
@rafahbordernews · 21,937
Telegram ranks this channel #9 of 84 here — alongside 83 others — read 20 September 2026
مناشدات ومفقودين غزة
@GAZA20249 · 32,910
Telegram ranks this channel #10 of 82 here — alongside 81 others — read 4 September 2026
شبكة وظائف فلسطين
@jobspals2 · 46,524
Telegram ranks this channel #16 of 83 here — alongside 82 others — read 27 August 2026
RT Online
@rtonlinearabic · 24,768
Telegram ranks this channel #19 of 75 here — alongside 74 others — read 14 September 2026
الصحفية صافيناز اللوح_غزة
@safypress90 · 43,316
Telegram ranks this channel #24 of 87 here — alongside 86 others — read 29 August 2026
علم 24 - Alam24
@alam24press · 19,886
Telegram ranks this channel #26 of 85 here — alongside 84 others — read 28 September 2026
مساعدات غزة الصفحة الرسمية
@musaeadatgaza · 36,649
Telegram ranks this channel #28 of 80 here — alongside 79 others — read 1 September 2026
شبكة الخامسة للأنباء
@alkhamisapal · 19,298
Telegram ranks this channel #29 of 88 here — alongside 87 others — read 29 September 2026
ألكسندر نازاروف
@futurecrimean · 20,036
Telegram ranks this channel #30 of 73 here — alongside 72 others — read 28 September 2026
التسجيل لمساعدات غزة
@GazaAid24 · 61,963
Telegram ranks this channel #35 of 85 here — alongside 84 others — read 21 August 2026
الإعلامي أحمد سعيد
@ahmedsaedd · 45,431
Telegram ranks this channel #37 of 90 here — alongside 89 others — read 22 August 2026
الرسالة
@alresalahpress · 25,561
Telegram ranks this channel #39 of 82 here — alongside 81 others — read 12 September 2026
Captain Ella كابتن ايلا
@IDFSpokespersonArabic · 41,770
Telegram ranks this channel #39 of 82 here — alongside 81 others — read 28 August 2026
⁨شادي صبح | shady sopoh | 🇵🇸
@shadysopoh · 21,057
Telegram ranks this channel #40 of 81 here — alongside 80 others — read 22 September 2026
Ultra palestine | الترا فلسطين
@ultrapalestine · 43,561
Telegram ranks this channel #40 of 80 here — alongside 79 others — read 27 August 2026
فلسطين أون لاين
@pl24online · 23,040
Telegram ranks this channel #41 of 85 here — alongside 84 others — read 17 September 2026
شبكة الشمال أون لاين
@shamal_online1 · 20,471
Telegram ranks this channel #43 of 82 here — alongside 81 others — read 24 September 2026
التحليل العبري הפרשנות בעברית
@EabriAnalysis · 20,924
Telegram ranks this channel #44 of 79 here — alongside 78 others — read 25 September 2026
وكالة سند للأنباء
@sndnewsa · 20,742
Telegram ranks this channel #44 of 84 here — alongside 83 others — read 23 September 2026
RT - Egypt روسيا اليوم - مصر
@Rtegypt · 36,521
Telegram ranks this channel #44 of 77 here — alongside 76 others — read 1 September 2026
الصحفي مثنى النجار
@muthanapress84 · 257,384
Telegram ranks this channel #44 of 83 here — alongside 82 others — read 10 August 2026
حسن اصليح | صحفي
@hpress · 519,442
Telegram ranks this channel #44 of 80 here — alongside 79 others — read 9 August 2026
الصحفي مهند قشطة
@mohnadQ · 106,921
Telegram ranks this channel #46 of 87 here — alongside 86 others — read 15 August 2026
نبض الشرقية
@Alsharqiapulse · 19,825
Telegram ranks this channel #48 of 85 here — alongside 84 others — read 27 September 2026

This channel appears in 69 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“سائد السويركي .. قناة آر تي Saed swerki Rt” (@saedelswerki), 16,775 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/saedelswerki.

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.