Channel
@sabzsaze
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
39,653subscribers
+32 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001371908160 |
|---|---|
| Type | Channel |
| Username | @sabzsaze |
| Description | ✅اینجا قراره از طراحی تا اجرای سازه رو تخصصی یاد بگیرید مسیر یادگیری حرفهای خودتون رو آغاز کنید 👇 https://sbz.one/akrw برای دریافت اطلاعات بیشتر درباره تورهای آموزشی، به آیدی زیر پیام بدین 👇 @moshavereh_sabzsaze ایتا👇 https://eitaa.com/sabzsaz |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/sabzsaze |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 12:29 | 39,653 | -4 |
| 13 Aug 2026, 04:13 | 39,657 | +6 |
| 12 Aug 2026, 05:12 | 39,651 | -7 |
| 11 Aug 2026, 04:33 | 39,658 | +11 |
| 10 Aug 2026, 04:28 | 39,647 | +32 |
| 8 Aug 2026, 03:55 | 39,615 | -3 |
| 7 Aug 2026, 03:47 | 39,618 | +1 |
| 6 Aug 2026, 05:00 | 39,617 | -4 |
| 6 Aug 2026, 01:48 | 39,621 | no change |
| 5 Aug 2026, 22:06 | 39,621 | first reading |
41 posts held, back to 29 July 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 22 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 14 August 2026 |
|---|---|
| Posts held | 41 (29 July 2026 – 14 August 2026) |
| Views total | 164,160 |
| Reactions total | 553 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 01:05 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.
Lifetime counters from Telegram’s own channel header, read 15 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.
Measured directly from 12 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.
524 reactions across 38 posts, in 8 distinct kinds. The most used accounts for 47.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 251 | 47.9% | |
| 👍 | 188 | 35.9% | |
| 👎 | 35 | 6.68% | |
| 🙏 | 22 | 4.20% | |
| 🔥 | 16 | 3.05% | |
| 👏 | 9 | 1.72% | |
| 😁 | 2 | 0.382% | |
| 🤷♂ | 1 | 0.191% |
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 41 of the 41 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 553reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 41 most recent posts we hold, published 29 July 2026 to 14 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.
📌 دو نکته طلایی در اجرای دیوار هبلکس ✅ با رعایت این دو نکته، میتونید یه دیوار هبلکس تمیز، دقیق و مقاوم اجرا کنید. ❓علاوه بر رعایت این دو نکته شما چه مورد دیگه ای رو پیشنهاد میدین؟ این پست رو حتما برای دوستاتون هم بفرستید🚀 #مهندس #مهندسی_عمران #عمران #هبلکس —————————- @SabzSaze 🌱
👍5❤2
مهمترین نکات مبحث ۲ رو براتون یکجا آوردم 💚 از وظایف طراح، ناظر و مجری گرفته تا نظام اداری و وظایف ادارات؛ همه نکات مهم مبحث ۲ رو براتون جمع کردم. 📌 ذخیرهش کنین، بعداً حتماً به کارتون میاد. حالا شما بگین 👇 دوست دارین نکات مهم کدوم مبحث رو هم به همین شکل براتون آماده کنم؟ #مهندسی_عمران #مبحث2 ———————— @SabzSaze 🌱
👍6🔥3❤1
📘 کتاب ضوابط طراحی ساختمان های مجهز به میراگر و جداگرهای لرزه ای منتشر شد کتاب «ضوابط طراحی ساختمانهای مجهز به میراگرها و جداگرهای لرزهای» با هدف ضابطهمند کردن طراحی، اجرا و کنترل این سامانهها و ارتقای ایمنی و تابآوری ساختمانها در برابر زلزله منتشر شده است. این کتاب مباحثی مانند انتخاب و طراحی، تحلیل لرزهای، آزمایش، کنترل اجرا و نگهداری میراگرها و جداگرها را پوشش میدهد. ⚠️ بر اساس ابلاغیه شماره ۴۰۰/۳۳۰۶۳ …
❤10👍2
این تکنیک رو درباره کنترل خیز میدونستین؟ ✅ توی این ویدئو، دکتر حمید صابری یه ترفند ویژه برای تعیین حداقل ضخامت دالهای یکطرفه رو با یه بیان ساده و دقیق توضیح دادن. 🎥 ببینین: یه قسمت ویژه از آموزش مبحث ۹ آزمون محاسبات با تدریس جذاب و روان دکتر حمید صابری 💎 منبع: تور تخصصی جامع آزمون محاسبات - مبحث ۹ اگه این آموزش براتون مفید بود، ادامه آموزشها رو هم میتونین از اینجا ببینین👇 📎 https://zaya.io/vlppj #عمران #مهن…
❤6👍4
به نظرتون آجرنما نیاز به اسکوپ داره؟ 🤔 توی پست قبلی گفتم که آجرنما بهطور معمول نیاز به اسکوپ نداره؛ اما بعضی مهندسین برای آجرهای زیرسقفی و بالای پنجرهها، اسکوپ رو الزامی میدونن. حالا سؤال اینجاست: ❓این روش اسکوپ کردن واقعاً جواب میده؟ #مهندسی_عمران #آجر_نما #اجرا —————————- @SabzSaze 🌱
👍15👏1
بازخورد شما، بزرگترین انگیزه ماست. ❤️ همیشه بعد از هر وبینار، خوندن پیامها و نظراتتون یکی از بهترین بخشهای کاره. خوشحالیم که این وبینار براتون مفید بوده. هدفمون این بود که علاوه بر انتقال تجربه، مسیر درست یادگیری و آینده طراحی سازه رو هم براتون شفاف کنیم ممنون از همه دوستانی که توی وبینار شرکت کردن و نظرشون رو با ما به اشتراک گذاشتن. 🙏 #طراحی_سازه #مهندسی_عمران #وبینار ————————— @SabzSaze 🌱
❤20👍2👎1
این اعداد رو هر مهندس عمرانی باید بلد باشه|قسمت دوم اگه قسمت اول رو ندیدین، حتماً اول اون رو ببینین 👌 توی قسمت اول دربارهی حدود و رواداریهای مجاز در اجرا صحبت کردیم برای دیدن قسمت اول روی لینک زیر کلیک کنین👇 🔗 دیدن قسمت اول این پست رو برای دوستان و همکارانتون هم بفرستین تا اونها هم استفاده کنن 🚀 #مهندسی_عمران #اجرای_ساختمان ———————— @SabzSaze 🌱
❤13
۴ فایل مهم برای مهندسین ناظر👌 💼 اگه ناظر هستین این ۴ تا فایل ضروری رو حتماً باید داشته باشین: 1️⃣ چکلیست نظارت سازه 2️⃣ شرح وظایف مهندس ناظر 3️⃣ نمونه قرارداد نظارت تکناظره 4️⃣ نمونه قرارداد نظارت چهارناظره برای همکارانتون هم بفرستین تا اونا هم استفاده کنن ☘️ #عمران #مهندسی_عمران #ناظر #اجرا —————————- @SabzSaze 🌱
❤12👍2
✅فایل شرح وظایف ناظر عمران ————————— @SabzSaze
❤8🙏3
✅فایل چک لیست نظارت سازه —————————- @SabzSaze
❤5🙏4
✅فایل نمونه قرارداد 4 ناظره —————————- @SabzSaze
🙏7
✅فایل قراردادهای شخص حقیقی تک ناظره —————————- @SabzSaze
❤8
Showing the 12 most recent of 41 posts we hold for @sabzsaze. 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.
@sabzsaze 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.
Citation-graph rank — 282,019 of 1,478,351entries 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.
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.
Named by 7 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.
@sabzsaze named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“مهندسی عمران | سبزسازه” (@sabzsaze), 39,653 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/sabzsaze.
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.