دوره های آنلاین و حضوری بدون مجوز ۲ تا ۵ سال زندان! تو یاد می گیری چطور فکر کنی... You learn how to think... @GARD_Academy GARD-Academy.com

Channel
گارد
@GARD_Academy
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
7,064subscribers
+19 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001009894001 |
|---|---|
| Type | Channel |
| Username | @GARD_Academy |
| Created | Between 1 October 2015 and 31 January 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/GARD_Academy |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 09:33 | 7,064 | -1 |
| 30 Aug 2026, 16:58 | 7,065 | -1 |
| 27 Aug 2026, 22:27 | 7,066 | +8 |
| 24 Aug 2026, 12:56 | 7,058 | +16 |
| 21 Aug 2026, 04:54 | 7,042 | +4 |
| 15 Aug 2026, 00:49 | 7,038 | -3 |
| 9 Aug 2026, 05:02 | 7,041 | -2 |
| 6 Aug 2026, 15:24 | 7,043 | -2 |
| 6 Aug 2026, 08:48 | 7,045 | first reading |
Engagement
38 posts held, back to 8 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 13 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 18.4%
- avg views ÷ 7,064 subscribers
- Avg views / post
- 1,300
- 24 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 24
- of 38 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.
| Window | Rolling 30 days · latest post in window 20 August 2026 |
|---|---|
| Posts held | 38 (8 July 2026 – 20 August 2026) |
| Views total | 31,263 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Aug 2026, 17:29 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
- 19m 30s
- Average length
- 2m 47s
Measured directly from 7 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
فردا شروع قطعی دوره انلاین زنده «میکروکنترلرهای AVR» مدرس: مهندس حمید نجفی لینک سرفصل ها و ثبت نام: https://gard-academy.com/avr-learning
معرفی قطعات کاربردی TPS51206 تامین کننده تغذیه های لازم تراشه های: DDR2 DDR3 DDR3L DDR4 تو یاد می گیری چطور فکر کنی... You learn how to think... @GARD_Academy GARD-Academy.com
شروع ثبت نام دوره آموزشی حضوری «طراحی مدارهای منطقی کاربردی» مدرس: مهندس حمید نجفی دوشنبه ها ۹ الی ۱۳ یک دوره تخصصی عالی طراحی دیجیتال و کلیه نیازهای پایه ای در این الکترونیک دیجیتال این دوره پیشنیاز دوره FPGA بوده بعد از این دوره در همین روز و ساعت دوره FPGA برگزار می گردد. بهمراه مدرک معتبر و فنی حرفه ای لینک سرفصل ها و ثبت نام: https://gard-academy.com/presence-digital لینک تقویم آموزشی کلیه دوره های در حال ثب…
اجرای یک تمرین منزل، درایو VGA و کنترل رنگ با ADC در دوره FPGA و نظر مهندس سروش بندانی در رابطه دوره اموزشی تخصصی «تراشه های FPGA» مدرس: مهندس حمید نجفی مجتمع آموزشی گارد تبلیغ ما نتیجه کار ماست... تو یاد می گیری چطور فکر کنی... You learn how to think... @GARD_Academy GARD-Academy.com
توضیحات فوق آشنایی و نحوه راه اندازی سیستم عامل اهورا می باشد که اقای مهندس امین خادم الحسینی زحمت کشیدن @amin98hosseini
🎧 بررسی عمیقتر AhuraRTOS در راستای معرفی و بررسی پروژه AhuraRTOS که توسعهی آن توسط مهندس عسکری انجام شده، مطالبی که در ۵ بخش دربارهی معماری، هسته، زمانبندی، مدیریت منابع و قابلیتهای این RTOS بررسی و جمعآوری کردم و در روزهای قبل به اشتراک گذاشتم را ، به همراه مستندات اصلی پروژه در اختیار NotebookLM قرار گرفت. نتیجه، تولید ۳ فایل صوتی تحلیلی و توضیحی است که موضوعات مطرحشده را از زاویهای متفاوت و عمیقتر بررسی م…
⚙️ کالبدشکافی فنی AhuraRTOS بخش ۵ | Integration و جمعبندی نهایی 🔧 ۹. راهنمای یکپارچهسازی با STM32CubeMX اگر قصد دارید AhuraRTOS را به پروژهای مبتنی بر STM32CubeMX اضافه کنید، دو نکته مهم را باید در نظر بگیرید: 1️⃣ PendSV باید در اختیار RTOS باشد در تنظیمات NVIC، تولید Handler مربوط به PendSV را غیرفعال کنید. چرا؟ چون AhuraRTOS از PendSV برای Context Switching استفاده میکند و Kernel باید کنترل این Exception را در…
⚙️ کالبدشکافی فنی AhuraRTOS بخش ۴ | Security، TrustZone و فلسفه Debugging 🛡 ۷. امنیت و قابلیتهای پیشرفته در نسلهای جدید ARM، امنیت فقط یک قابلیت نرمافزاری نیست و بخشی از آن مستقیماً در سختافزار پردازنده پیادهسازی شده است. در ARMv8-M و پردازندههایی مانند Cortex-M33، قابلیتهایی مثل TrustZone امکان جداسازی محیط Secure و Non-Secure را فراهم میکنند. AhuraRTOS برای این معماری از قابلیتهایی مانند PSPLIM (Process S…
⚙️ کالبدشکافی فنی AhuraRTOS بخش ۳ | IPC، Preemption، Atomics و مدیریت حافظه 🔐 ۵. ارتباطات بینتسکی و کنترل Preemption در یک RTOS، فقط انتقال داده بین Taskها مهم نیست؛ نحوه محافظت از دادههای مشترک هم اهمیت زیادی دارد. AhuraRTOS برای این کار دو مکانیزم متفاوت در اختیار برنامهنویس قرار میدهد: 🔹 Scheduler Lock با: os_kernel_lock() Scheduler متوقف میشود، اما Interruptها همچنان فعال هستند. یعنی Task دیگری نمیتواند جا…
⚙️ کالبدشکافی فنی AhuraRTOS بخش ۲ | Scheduling، Priority و Context Switching 🧠 ۳. مکانیسم Scheduling و مدیریت Priority یکی از ویژگیهای مهم AhuraRTOS، استفاده از Scheduler با پیچیدگی O(1) است. یعنی زمان انتخاب Task بعدی به تعداد Taskهای سیستم وابسته نیست؛ چه ۲ Task داشته باشیم و چه ۳۲ Task، انتخاب Task آماده با زمان ثابت انجام میشود. 🔹 ۳۲ سطح Priority AhuraRTOS از ۳۲ سطح اولویت، از 0 تا 31، استفاده میکند. این ساخت…
🧩 کالبدشکافی فنی AhuraRTOS رویکردی نوین در طراحی RTOS برای ARM Cortex-M بخش ۱ | معماری Kernel و فلسفه Portability 🔹 ۱. فراتر از انتزاعهای رایج در Embedded اگر با سیستمهای نهفته کار کرده باشید، احتمالاً با یک سؤال مهم روبهرو شدهاید: ❓ چرا با تغییر معماری یا مدل پردازنده، باید بخشهایی از Kernel یک RTOS را نیز تغییر دهیم؟ در بسیاری از RTOSهای سنتی، Port کردن سیستمعامل به یک معماری جدید فقط به تغییر HAL محدود نمی…
Showing the 12 most recent of 38 posts we hold for @GARD_Academy. 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 — 498,226 of 1,630,085 entries 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
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.
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.
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.
@elecz · 52,580
Telegram ranks this channel #65 of 69 here — alongside 68 others — read 24 August 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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“گارد” (@GARD_Academy), 7,064 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/GARD_Academy.
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.