Telegram RegisterThe public register of Telegram

Channel

اخبار سوریه به فارسی

@SyriainPersian

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

12,298subscribers

-994 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001676674922
TypeChannel
Username@SyriainPersian
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/SyriainPersian

Topic

National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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 why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@SyrianToPersian/705497 Aug 2026, 14:54 UTC@SyriainPersian/21766 · this entry7 Aug 2026, 14:54 UTC0.98under a minute
@SyrianToPersian/705397 Aug 2026, 12:24 UTC@SyriainPersian/21760 · this entry7 Aug 2026, 12:24 UTC0.98under a minute
@SyrianToPersian/705277 Aug 2026, 09:31 UTC@SyriainPersian/21753 · this entry7 Aug 2026, 09:31 UTC0.97under a minute
@SyrianToPersian/705727 Aug 2026, 21:39 UTC@SyriainPersian/21785 · this entry7 Aug 2026, 21:39 UTC0.97under a minute
@SyrianToPersian/705567 Aug 2026, 17:55 UTC@SyriainPersian/21772 · this entry7 Aug 2026, 17:55 UTC0.97under a minute
@SyrianToPersian/705237 Aug 2026, 09:20 UTC@SyriainPersian/21752 · this entry7 Aug 2026, 09:20 UTC0.96under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@SyrianToPersian15 (8/8 hand-verifiable sample passed)0.97under a minute@SyrianToPersian (150)
@salam_iraniann5 (5/5 hand-verifiable sample passed)0.987 minutes@salam_iraniann (50)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 20 of the 20 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 32 comparable posts for this entry, running 7 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @SyrianToPersian. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

12,29813,29212,7957 August 2026 — 13,292 subscribers7 August 2026 — 13,292 subscribers7 August 2026 — 13,188 subscribers9 August 2026 — 12,929 subscribers10 August 2026 — 12,837 subscribers10 August 2026 — 12,725 subscribers11 August 2026 — 12,436 subscribers12 August 2026 — 12,298 subscribers7 August 202612 August 2026
8 measurements spanning 5 days, net -994. 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 12,149–13,441 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 14:2412,298-138
11 Aug 2026, 17:3512,436-289
10 Aug 2026, 20:3412,725-112
10 Aug 2026, 00:0212,837-92
9 Aug 2026, 02:0112,929-259
7 Aug 2026, 23:4213,188-104
7 Aug 2026, 17:4613,292no change
7 Aug 2026, 17:3513,292first reading

Engagement

192 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.9%
avg views ÷ 12,298 subscribers
Avg views / post
2,200
192 posts measured
Reaction rate
0.039%
reactions ÷ views · ER floor
Posts in window
192
of 192 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 36 of 192 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 12 August 2026
Posts held192 (7 August 202612 August 2026)
Views total422,513
Reactions total38
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 12:27 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

Video runtime
56m 19s
Average length
53s

Measured directly from 64 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

38 reactions across 32 posts, in 4 distinct kinds. The most used accounts for 44.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎1744.7%
1026.3%
👍821.1%
🔥37.89%

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

Measured over the 192 most recent posts we hold, published 7 August 2026 to 12 August 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

12 Aug 2026, 12:10 UTC≈2,130 viewsread 12 August 2026
Video

🎥 شکایت یک برانداز سابق سوری از بی‌عدالتی و فراموش شدن حقوقش 🔹یکی از شهروند برانداز سابق و ضد اسد، معروف به ابو وديع از مرصد الجانودية، گفته است پس از ۱۴ سال فعالیت در شرایط جنگی و هشدار درباره حملات هوایی حکومت پیشین، در نهایت به‌عنوان کارگر نظافت شهرداری با حقوقی ناچیز معادل ۱۵۰ دلار مشغول شده و امروز خود را فراموش‌شده می‌بیند. او می‌گوید انتظار داشته در نهادهای رسمی جایگاهی متناسب با سابقه‌اش پیدا کند، اما در عمل

12 Aug 2026, 11:37 UTC≈2,120 viewsread 12 August 2026
Video

🎥 بستن دفاتر سازمان‌های فلسطینی در سوریه 🔹 رامی عبد الرحمن مدیر دیده‌بان حقوق بشر سوریه گفت: الجولانی دستور داده همه دفاتر سازمان‌های فلسطینی در سوریه بسته شود؛ اقدامی که به‌گفته منتقدان، برای جلب رضایت اسرائیل انجام گرفته است. این تصمیم، نگرانی‌ها درباره تشدید فشارهای سیاسی و امنیتی بر فلسطینیان و دیگر گروه‌های آسیب‌پذیر در سوریه را افزایش داده است. @SyriainPersian

12 Aug 2026, 11:10 UTC≈1,680 viewsread 12 August 2026
Video

🎥 ضرب‌وشتم یک مرد در الحسکه توسط عناصر قسد 🔹در حسکه، ویدیویی منتشر شده که نشان می‌دهد عناصر وابسته به قسد در محله النشوة الغربية یک مرد را مورد ضرب‌وشتم قرار داده‌اند. این حادثه، بار دیگر از ادامه رفتارهای خشونت‌آمیز و بی‌ضابطه در مناطق تحت کنترل گروه‌های مسلح حکایت دارد؛ مناطقی که مردم در آن‌ها از امنیت واقعی و رفتار قانون‌مند محروم‌اند. @SyriainPersian

12 Aug 2026, 10:40 UTC≈2,900 viewsread 12 August 2026
Photo

🔴گزارش‌هایی منتشر شده که آمریکا میان سوریه و اسرائیل در پرونده‌ای محرمانه میانجی‌گری کرده تا مواد هسته‌ای ذخیره‌شده در یک مکان سری داخل سوریه با نظارت آژانس حذف شود؛ اقدامی که نشان می‌دهد بخشی از پرونده‌های حساس دوره اسد همچنان بر امنیت و آینده سوریه سایه انداخته‌اند. @SyriainPersian

12 Aug 2026, 10:10 UTC≈3,840 viewsread 12 August 2026
Video

🎥 کارزار آگاهی‌بخشی علیه توهین به مقدسات در سوریه 🔹در واکنش به گسترش توهین به مقدسات و فحاشی دینی، یک کارزار آگاهی‌بخشی راه‌اندازی شده است. این اقدام نشان می‌دهد که فروپاشی اجتماعی و خشونت کلامی در سوریه نیز به مرحله نگران‌کننده‌ای رسیده و شکاف‌های اخلاقی و فرهنگی در سایه بحران طولانی‌مدت کشور، عمیق‌تر شده‌اند. @SyriainPersian

12 Aug 2026, 09:38 UTC≈1,110 viewsread 12 August 2026
Photo

🔴تداوم همکاری‌های هسته‌ای و نگرانی از پرونده پنهان سوریه 🔹هیئت انرژی اتمی سوریه با صدور بیانیه‌ای اعلام کرده که همکاری با آژانس بین‌المللی انرژی اتمی و کشورهای دوست برای رسیدگی به «میراث رژیم سابق» و احیای عضویت کامل سوریه در آژانس ادامه دارد. @SyriainPersian

12 Aug 2026, 09:10 UTC≈1,110 viewsread 12 August 2026
Video

🎥 حمله پلیس ترکیه به یک جوان سوری 🔹گزارش‌ها حاکی است پلیس ترکیه به یک جوان سوری حمله کرده و او را مورد ضرب‌وشتم قرار داده است. این رخداد بار دیگر از آسیب‌پذیری پناهجویان سوری در خارج از کشور و استمرار فشار و تحقیر علیه آنان خبر می‌دهد؛ مردمی که پس از سال‌ها جنگ، همچنان در داخل و خارج از سوریه از امنیت و کرامت محروم‌اند. @SyriainPersian

12 Aug 2026, 08:41 UTC≈1,110 views1 reactionsread 12 August 2026
Video

🎥ایرانی‌ها اوباش هستند، چون تسلیم نمی‌شوند 🔹مایک پمپئو، وزیر خارجه سابق ترامپ: "ایرانی‌ها هنوز حاضر نیستند تسلیم بشوند؛ نه به این دلیل که مذاکره‌کنندگان خوبی نیستند، بلکه چون اصلاً اهل معامله نیستند؛ آنها تروریست‌ها و اوباشی هستند که می‌خواهند اسرائیل و ایالات متحده آمریکا را نابود کنند. بنابراین، محاصره باید ادامه پیدا کند؛ نه برای فشار آوردن به مردم ایران، بلکه برای تحت فشار قرار دادن خود رژیم ... یکی از اهدافی

👎1

12 Aug 2026, 08:37 UTC≈1,110 viewsread 12 August 2026
Photo

📸 پیدا شدن نوزاد رهاشده در دیرالزور 🔹در بلدة محیمیده در حومه دیرالزور، یک نوزاد تازه‌متولدشده در کنار جاده رها شده و پیدا شده است. این حادثه تکان‌دهنده، تصویری تلخ از فقر، فروپاشی اجتماعی و بحران انسانی در سوریه امروز ارائه می‌دهد؛ کشوری که خانواده‌های زیادی در آن زیر فشار جنگ و بی‌ثباتی از هم پاشیده‌اند. @SyriainPersian

12 Aug 2026, 08:33 UTC≈1,100 views1 reactionsread 12 August 2026
Video

🎥دو تروریست مسلح در سیستان و بلوچستان توسط وزارت اطلاعات مورد حمله قرار گرفته و داخل خودروی پوشش سوختبری خود به هلاکت رسیدند. @SyriainPersian

1

12 Aug 2026, 08:33 UTC≈1,100 viewsread 12 August 2026
Photo

📸تصویر هوایی از آلودگی نفتی در سواحل قشم @SyriainPersian

12 Aug 2026, 08:32 UTC≈1,110 viewsread 12 August 2026
Video

🎥روایت جدید زاکانی از جزئیات اصابت موشک به منزل رهبر انقلاب و شهادت همسر ایشان @SyriainPersian

Showing the 12 most recent of 192 posts we hold for @SyriainPersian. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“اخبار سوریه به فارسی” (@SyriainPersian), 12,298 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SyriainPersian.

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.