Telegram RegisterThe public register of Telegram

Channel

معبر باب الهوى

@babalhawabc

Verified by Telegram

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

16,151subscribers

-82 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001146057471
TypeChannel
Username@babalhawabc
Descriptionالقناة الرسمية لمنفذ باب الهوى الحدودي التابع للهيئة العامة للمنافذ والجمارك في الجمهورية العربية السورية
CreatedBetween 1 May 2017 and 30 June 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/babalhawabc

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 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 1 other registered channel. 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@SyrGABC/44525 Aug 2026, 12:08 UTC@babalhawabc/15900 · this entry5 Aug 2026, 13:59 UTC1.001.9 hours
@SyrGABC/44615 Aug 2026, 14:32 UTC@babalhawabc/15909 · this entry5 Aug 2026, 14:46 UTC1.0014 minutes
@SyrGABC/44685 Aug 2026, 17:03 UTC@babalhawabc/15916 · this entry5 Aug 2026, 17:11 UTC1.008 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@SyrGABC8 (8/8 hand-verifiable sample passed)1.0038 minutes@SyrGABC (80)

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 3 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 8 comparable posts for this entry, running 5 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 2, the earliest publisher we hold is @SyrGABC. 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 1 other registered channel, 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

16,15116,23316,1925 August 2026 — 16,233 subscribers6 August 2026 — 16,233 subscribers6 August 2026 — 16,227 subscribers7 August 2026 — 16,214 subscribers8 August 2026 — 16,204 subscribers9 August 2026 — 16,193 subscribers10 August 2026 — 16,183 subscribers11 August 2026 — 16,162 subscribers12 August 2026 — 16,151 subscribers5 August 202612 August 2026
9 measurements spanning 6 days, net -82. 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,139–16,245 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 06:0216,151-11
11 Aug 2026, 04:5516,162-21
10 Aug 2026, 06:3116,183-10
9 Aug 2026, 08:0416,193-11
8 Aug 2026, 09:3116,204-10
7 Aug 2026, 11:4016,214-13
6 Aug 2026, 15:0416,227-6
6 Aug 2026, 02:1916,233no change
5 Aug 2026, 22:0216,233first reading

Engagement

18 posts held, back to 5 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 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.76%
avg views ÷ 16,151 subscribers
Avg views / post
446
18 posts measured
Reaction rate
0.162%
reactions ÷ views · ER floor
Posts in window
18
of 18 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 4 of 18 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 11 August 2026
Posts held18 (5 August 202611 August 2026)
Views total8,035
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 10:13 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
15,200
Videos
501
Links
5,210

Lifetime counters from Telegram’s own channel header, read 12 August 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
7m 10s
Average length
1m 48s

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

4 reactions across 4 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4100.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 4 of the 18 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

11 Aug 2026, 20:42 UTC348 viewsread 12 August 2026
Forwarded from @SyrGABCPhoto

مرفأ طرطوس يعزّز قدراته التشغيلية بوصول رافعتين متنقلتين حديثتين استقبل مرفأ طرطوس رافعتين متنقلتين حديثتين من طراز KONECRANES MHC ESP.7B، في إطار خطط تحديث منظومة العمل في المرفأ ورفدها بأحدث المعدات والآليات التشغيلية. ومن شأن الرافعتين الإسهام في رفع كفاءة عمليات المناولة، وتسريع أعمال شحن البضائع وتفريغها، وزيادة الطاقة التشغيلية للمرفأ، بما يعزّز قدرته على استيعاب حركة السفن والبضائع بكفاءة وانسيابية أكبر. وي

11 Aug 2026, 20:42 UTC260 viewsread 12 August 2026
Forwarded from @SyrGABCVideo

يقظة خفر السواحل تحبط محاولة هجرة غير نظامية عبر البحر #يوتيوب https://youtu.be/KNfsm2WtWWM #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

11 Aug 2026, 20:42 UTC247 viewsread 12 August 2026
Forwarded from @SyrGABCPhoto

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

11 Aug 2026, 14:02 UTC429 viewsread 12 August 2026
Forwarded from @SyrGABCPhoto

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

10 Aug 2026, 14:08 UTC188 viewsread 10 August 2026
Forwarded from @SyrGABCPhoto

الهيئة العامة للمنافذ والجمارك ووزارة الإدارة المحلية والبيئة تبحثان تعزيز التنسيق في الملفات البيئية والرقابة الحدودية استقبل رئيس الهيئة العامة للمنافذ والجمارك السيد قتيبة بدوي، وزير الإدارة المحلية والبيئة السيد محمد عنجراني والوفد المرافق له، بحضور مدير إدارة الجمارك العامة السيد خالد البراد، وفريق عمل مديرية المخابر والجودة، حيث عقد الجانبان اجتماعاً موسعاً لبحث عدد من الملفات ذات الاهتمام المشترك، وتعزيز التن

10 Aug 2026, 14:07 UTC140 viewsread 10 August 2026
Forwarded from @SyrGABCPhoto

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

10 Aug 2026, 10:36 UTC276 viewsread 10 August 2026
Forwarded from @SyrGABCPhoto

معاون رئيس الهيئة يتفقد سير العمل الجمركي في منفذ جديدة يابوس الحدودي أجرى معاون رئيس الهيئة العامة للمنافذ والجمارك لشؤون الجمارك، مدير إدارة الجمارك العامة، السيد خالد البراد، جولة ميدانية في منفذ جديدة يابوس الحدودي، برفقة مدير المنفذ السيد محمد خالد قره قاش، لمتابعة سير العمل والاطلاع على الإجراءات الجمركية والخدمات المقدمة. وشملت الجولة عدداً من المرافق والوحدات الحيوية، من بينها وحدة الكلاب البوليسية (K9)، وس

8 Aug 2026, 20:59 UTC551 views1 reactionsread 10 August 2026
Forwarded from @SyrGABCPhoto

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

1

8 Aug 2026, 19:11 UTC551 views1 reactionsread 10 August 2026
Forwarded from @SyrGABCPhoto

نحو 29 ألف رأس من المواشي.. مرفأ طرطوس يستقبل ثلاث بواخر ترانزيت متجهة إلى الأردن والعراق استقبل مرفأ طرطوس ثلاث بواخر ترانزيت محمّلة بنحو 29 ألف رأس من المواشي، في إطار النشاط المتنامي الذي يشهده المرفأ في حركة العبور الإقليمية، ودوره في خدمة التجارة والنقل بين سوريا ودول المنطقة. ووصلت إلى المرفأ باخرتان قادمتان من البرازيل، تحملان نحو 15 ألف رأس من العجول، فيما وصلت باخرة ثالثة قادمة من إسبانيا، محمّلة بأكثر من 14

1

8 Aug 2026, 17:49 UTC578 views1 reactionsread 10 August 2026
Forwarded from @SyrGABCVideo

دخول السوريين بسياراتهم إلى تركيا.. إجراءات مبسّطة وعبور أكثر سهولة #يوتيوب https://youtu.be/Guv1FOaA9fI #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

1

7 Aug 2026, 20:23 UTC788 views1 reactionsread 10 August 2026
Forwarded from @SyrGABCVideo

وحدات K9.. خط الدفاع الأول في كشف المواد المحظورة في المنافذ. #يوتيوب https://youtu.be/gUqGWabgkQ0 #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

1

6 Aug 2026, 20:50 UTC944 viewsread 10 August 2026
Forwarded from @SyrGABCVideo

العودة الطوعية تتواصل.. أكثر من مليون و385 ألف عائد إلى سوريا #يوتيوب https://youtube.com/shorts/OQEg127XToc #الجمهورية_العربية_السورية #الهيئة_العامة_للمنافذ_والجمارك

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

Citation-graph rank

Citation-graph rank — 918,175 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

Named by 1 registered channel — 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.

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.

“معبر باب الهوى” (@babalhawabc), 16,151 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/babalhawabc.

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.