Telegram RegisterThe public register of Telegram
Telegram profile photo for الهيئة العامة للمنافذ والجمارك السورية

Channel

الهيئة العامة للمنافذ والجمارك السورية

@SyrGABC

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

26,458subscribers

+278 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-1002445223781
TypeChannel
Username@SyrGABC
Descriptionالقناة الرسمية للهيئة العامة للمنافذ والجمارك في الجمهورية العربية السورية
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/SyrGABC

Topic

Local community — 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 78% 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.

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 in near-verbatim form on 3 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@SyrGABC/4806 · this entry27 Aug 2026, 16:27 UTC@syrianevent1/5671627 Aug 2026, 18:37 UTC1.002.2 hours
@SyrGABC/5512 · this entry8 Nov 2026, 20:41 UTC@syrianevent1/578429 Nov 2026, 05:29 UTC1.008.8 hours
@SyrGABC/5520 · this entry9 Nov 2026, 12:38 UTC@syrianevent1/578499 Nov 2026, 16:24 UTC1.003.8 hours
@SyrGABC/5553 · this entry12 Nov 2026, 15:31 UTC@syrianevent1/5792012 Nov 2026, 20:01 UTC1.004.5 hours
@SyrGABC/5562 · this entry15 Nov 2026, 12:45 UTC@syrianevent1/5795315 Nov 2026, 13:21 UTC1.0036 minutes
@SyrGABC/5174 · this entry4 Oct 2026, 16:53 UTC@LatakiaGov1/209114 Oct 2026, 18:56 UTC1.002.0 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@syrianevent15 (5/5 hand-verifiable sample passed)1.003.8 hoursthis entry (5–0)
@babalhawabc86 (7/8 hand-verifiable sample passed)1.002.7 hoursthis entry (86–0)
@LatakiaGov16 (6/6 hand-verifiable sample passed)1.002.4 hoursthis entry (6–0)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 196 comparable posts for this entry, running 5 August 2026 to 16 November 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @SyrGABC — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 17 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

26,12726,52126,32426,4586 August 202616 November 2026
65 measurements spanning 103 days, net +278. 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 26,068–26,580 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
16 Nov 2026, 19:4726,458-31
13 Nov 2026, 09:2126,489+7
11 Nov 2026, 00:0626,482+15
9 Nov 2026, 10:0826,467-2
7 Nov 2026, 22:1926,469-8
6 Nov 2026, 20:5526,477-6
5 Nov 2026, 19:2526,483-11
4 Nov 2026, 22:3126,494-6
3 Nov 2026, 19:0826,500-4
2 Nov 2026, 17:4026,504-17
1 Nov 2026, 16:4726,521+10
31 Oct 2026, 18:4026,511+7
30 Oct 2026, 16:4126,504+81
29 Oct 2026, 14:1626,423+15
28 Oct 2026, 16:4026,408+35
27 Oct 2026, 13:1126,373+66
26 Oct 2026, 11:5626,307-4
25 Oct 2026, 10:5626,311-8
24 Oct 2026, 10:0426,319+5
23 Oct 2026, 08:3626,314first reading

Engagement

196 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 157 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
15.5%
avg views ÷ 26,458 subscribers
Avg views / post
4,100
51 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
51
of 196 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held196 (5 August 2026 – 16 November 2026)
Views total209,300
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 07:09 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
≈4,850
Videos
≈355
Links
≈378

Lifetime counters from Telegram’s own channel header, read 17 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
2h 07m
Average length
2m 02s

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

Recent posts

Telegram’s own ‘edited’ marker: 2 of 51 posts held from the last 30 days (3.92%) 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).

16 Nov 2026, 17:55 UTC≈1,620 viewsread 17 November 2026
Video

قسم المرور في مرفأ طرطوس.. متابعة حركة الشاحنات وتنظيم عمليات النقل داخل المرفأ #يوتيوب https://youtube.com/shorts/oCmQtwifxZg #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

15 Nov 2026, 16:32 UTC≈3,150 viewsread 17 November 2026
Photo

رئيس الهيئة العامة للمنافذ والجمارك يستقبل محافظ السويداء استقبل رئيس الهيئة العامة للمنافذ والجمارك، السيد قتيبة بدوي، بحضور معاونيه، محافظ السويداء السيد مصطفى البكور، حيث جرى خلال اللقاء بحث عدد من الملفات المتعلقة بالشؤون الجمركية في المحافظة، ومناقشة واقع العمل الجمركي والتحديات المرتبطة به. كما تناول اللقاء سبل تعزيز التنسيق والتعاون المشترك بين الهيئة والمحافظة، وتطوير آليات العمل وتسهيل الإجراءات، بما يسهم …

15 Nov 2026, 12:45 UTC≈2,960 viewsread 17 November 2026
Photo

منفذ العريضة.. استكمال المرحلة الأخيرة من أعمال التأهيل تمهيداً لافتتاحه تستكمل الورش الفنية أعمال تعبيد الطرق والساحات ضمن منفذ العريضة الحدودي مع لبنان، وإنجاز التشطيبات الأخيرة لمشروع إعادة التأهيل، تمهيداً لافتتاحه واستئناف حركة العبور. وشمل المشروع إعادة بناء الجسر الواصل بين سوريا ولبنان، وتأهيل البنية التحتية، وتعبيد الطرق والساحات ضمن المنفذ، إلى جانب تنفيذ الأعمال الفنية والإنشائية والخدمية اللازمة لتجهيز …

14 Nov 2026, 15:41 UTC≈3,110 viewsread 17 November 2026
Video

تسهيلات وإجراءات ميسرة تعزز حركة العبور في منفذ جوسية الحدودي #يوتيوب https://youtu.be/XWNwReIri58 #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

13 Nov 2026, 17:48 UTC≈4,440 viewsread 17 November 2026
Video

أعمال تطوير متواصلة لرفع الجاهزية التشغيلية لمنفذ تل أبيض الحدودي #يوتيوب https://youtu.be/0dLTkkVAfQc #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

13 Nov 2026, 12:39 UTC≈4,710 viewsread 17 November 2026
Video

مرفأ اللاذقية.. إجراءات مرورية لضمان انسيابية حركة الشاحنات #يوتيوب https://youtu.be/PEloyXaBXOY #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

12 Nov 2026, 15:31 UTC≈5,200 viewsread 17 November 2026
Photo

ضبط محاولة تهريب طيور جارحة في منفذ جوسية الحدودي تمكنت أمانة الجمارك في منفذ جوسية الحدودي من ضبط محاولة تهريب طيور جارحة، وذلك خلال إجراءات التفتيش والكشف على إحدى المركبات العابرة للمنفذ باتجاه الأراضي اللبنانية. وأثناء عملية الكشف، عثرت الكوادر الجمركية على طيور مخبأة داخل المركبة، ليتم ضبطها ومصادرتها أصولاً، وتنظيم محضر ضبط بالواقعة، تمهيداً لإحالتها إلى الجهات المختصة واستكمال الإجراءات القانونية اللازمة. و…

12 Nov 2026, 11:57 UTC≈3,580 viewsread 15 November 2026
Video

30 ألف طن كبريت عراقي تصل إلى مرفأ اللاذقية في أولى عمليات التصدير #يوتيوب https://youtu.be/cFmV1HnHaTQ #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

12 Nov 2026, 09:01 UTC≈3,550 viewsread 15 November 2026
Video

منفذ باب الهوى.. خطوات متسارعة نحو استكمال التأهيل #يوتيوب https://youtube.com/shorts/OqkAyQ9t694 #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

11 Nov 2026, 15:10 UTC≈3,640 viewsread 15 November 2026
Video

336 طالباً جديداً مع انطلاق العام الدراسي في الثانويات البحرية #يوتيوب https://youtu.be/0CEiDWhgx08 #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

11 Nov 2026, 11:51 UTC≈4,300 viewsread 15 November 2026
Photo

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

11 Nov 2026, 08:59 UTC≈3,250 viewsread 14 November 2026
Video

المنطقة الحرة في عدرا.. وجهة استثمارية متنامية في قطاع السيارات والآليات #يوتيوب https://youtu.be/CTn-iuEFKzY #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

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

Posts edited after publishing

@SyrGABC edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
25 August 2026
Most recent edit
25 August 2026

Forward network

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.

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“الهيئة العامة للمنافذ والجمارك السورية” (@SyrGABC), 26,458 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/SyrGABC.

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.