2 measurements spanning 2 days, net +1. 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 4,155–4,156 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Sept 2026, 22:19
4,156
+1
12 Sept 2026, 09:22
4,155
first reading
Engagement
14 posts held, back to 28 August 2024 — 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.
ERR · 30 days
7.25%
avg views ÷ 4,156 subscribers
Avg views / post
301
3 posts measured
Reaction rate
0.325%
reactions ÷ views · ER floor
Posts in window
3
of 14 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 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 5 September 2026
Posts held
14 (28 August 2024 – 5 September 2026)
Views total
904
Reactions total
2
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Sept 2026, 09:22 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.
Reaction mix
44 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 88.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
39
88.6%
👍
5
11.4%
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 9 of the 14 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 44 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 28 August 2024 to 5 September 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- مشكله ترحیل أسياخ التسلیح الرئيسي للأعمدة أثناء الصب.
--------------------------------------------
- الأسباب :
1- عدم استخدام كانة بعیون أثناء الصب لربط الأسياخ من أعلى ومن أسفل .
2- عدم استخدام بسكوت للحفاظ على الغطاء الخرسانى حول الحدید.
3- عدم ربط الكانات بالحدید بصورة جیدة بإستخدام سلك رباط.
4- اثناء الصب يقوم العمال بتحريك الاسياخ بهدف تحريك الخرسانه …
اطول عملية نقل مواسير في تاريخ قناة السويس 🇪🇬
12 ماسورة بولي ايثيلين HDPE عملاقة تسافر عائمة على وش المياه عبر البحار والمحيطات .. قادمة من النرويج و متجهها الى بنجلاديش .. مرورا بقناة السويس
6 مواسير منها يبلغ طول الواحدة منها 620 متراً بقطر 2.3 متر، فيما يصل طول الـ 6 مواسير الأخرى 500 متر للماسورة بنفس القطر ، ليكون اجمالي طول المواسير ٦٧٢٠متر
مرور المواسير لأول مرة عبر قناة السويس بدلا من طريق رأس الرجاء الصال…
امستردام هولندا 🇳🇱
كانتيليفر (كابولي) بطول 16m حديد وخرسانة😀💯
Join us 👇
https://www.facebook.com/groups/706689403450537/?ref=share
Join us on Telegram 👇
t.me/CivilEngineering124
❤9👍2
Signed M E
Showing the 12 most recent of 14 posts we hold for @CivilEngineering124. 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.
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.
وعجلت إليك رب لترضى @waagelto · 26,552 Telegram ranks this channel #84 of 85 here — alongside 84 others — read 12 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. 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 13 September 2026 — this
entry's latest reading, not the date you are reading this.
“الهندسه المدنيه-Civil Engineering” (@CivilEngineering124), 4,156 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/CivilEngineering124.
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.