Channel
@aitelecomeng
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
201subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001639125063 |
|---|---|
| Type | Channel |
| Username | @aitelecomeng |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/aitelecomeng |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 21:14 | 201 | +3 |
| 7 Aug 2026, 04:32 | 198 | no change |
| 7 Aug 2026, 03:01 | 198 | first reading |
20 posts held, back to 23 January 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 pageof 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 31 July 2026 |
|---|---|
| Posts held | 20 (23 January 2024 – 31 July 2026) |
| Views total | 3,119 |
| Reactions total | 108 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 04:32 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.
121 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 38.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 47 | 38.8% | |
| 👍 | 44 | 36.4% | |
| 👏 | 14 | 11.6% | |
| 👎 | 4 | 3.31% | |
| 😁 | 4 | 3.31% | |
| 💩 | 3 | 2.48% | |
| 🥰 | 2 | 1.65% | |
| 🔥 | 1 | 0.826% | |
| 🤡 | 1 | 0.826% | |
| 🦄 | 1 | 0.826% |
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 17 of the 20 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 121reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 23 January 2024 to 31 July 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.
تمایل دارید در مورد کدوم یکی از مباحث زیر یه شبیه سازی تو متلب انجام بدم و نکاتش بررسی بشه؟
The shares total 118%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
👍5
سلام به همگی این جزوه رو دریابید که یکی از درسای ارشد مخابرات سیستمه این درس درک عمیقی از مبحاث لایه فیزیکی مخابرات سلولی به ما میده و تکنیک هایی مثل OFDM رو تدریس میکنه لایه فیزیکی مخابرات سلولی این جزوه و لایه های بالاتر شبکه تو ویدئو های درس شبکه سلولی موجوده(همین کانال اپلود شده) @aitelecomeng
❤5👍2
📌 حافظه در FPGA Block RAM vs Distributed RAM + Single/Dual-Port RAM سلام داشتم روی یه پروژه کار میکردم که توی اون نیاز به نعریف کردن حافظه تو FPGA داشتم واسه همین منابعی که داشتم رو دوباره مطالعه کردم و یه سری نکات بهشون رسیدم: اگر دارید روی طراحی دیجیتال/پیادهسازی روی FPGA کار میکنید، یکی از تصمیمهای مهم اینه که «حافظه رو کجا و چطور بسازیم؟» ──────────────────────── 1) مدل پورتها در RAM ✅ Single-Por…
❤4
جزوه درس مخابرات سلولی دکتر صباغیان دانشگاه تهران https://t.me/aitelecomeng
❤9🥰1
Posted without readable text
🥰1
سلام به همه عزیزان 👋🌟 محتوای این کانال بسیار ارزشمنده و من خودم خیلی نکات خوبی درباره رادیو نرمافزاری از شون یاد گرفتم 📡📚 کلا پیادهسازی الگوریتمها تو سختافزار روشهای متنوعی داره ⚙️ یکی از اون روشها رادیو نرمافزاری هست یا پیادهسازی تو FPGA 🛠️ هر شرکت و مجموعهای بر اساس رویکردی که داره، یکی از روشها رو انتخاب میکنه 🏢✅
👏7
به نام خدا سلام وقتتون بخیر در این سری از ویدئوها قصد داریم وارد جزییات یک فرستنده و گیرنده بشویم. به این صورت که هدف ما این است که به عنوان مثال مدولاسیون bpsk و pulse shaping را که در gnu radio پیاده سازی شده است را به محیط pycharm برد و کد آن را خودمان بزنیم این کار باعث درک عمیق می شود. پیشاپیش بابت بیان ضعیف عذرخواهم. قسمت اول پیادهسازی با پایتون موضوع: تبدیل رشته کاراکتر به دنباله بیت https://t.me/SDR_t…
👏7❤1
با تشکر از دوست خوبم @grok بابت طراحی پروفایل کانال
😁4❤3🔥1🤡1
Channel photo updated
جزوه تخمین و آشکار سازی دکتر الفت دانشگاه تهران
❤3👍2
مهندس مخابرات pinned «سلام به همگی 👋 امیدوارم حالتون خوب باشه ✨ من تصمیم گرفتم تو این کانال محتوای مفید تو حوزههای مخابرات و هوش مصنوعی بذارم 📡🤖 سعی میکنم مطالبی بذارم که کمک میکنه به پیدا کردن شغل و ارتقای شغلی و یا حتی مهاجرت 🚀🌍 برای همین اگر دوست داشتید میتونید مطالب…»
Channel name was changed to «مهندس مخابرات»
Showing the 12 most recent of 20 posts we hold for @aitelecomeng. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
تمایل دارید در مورد کدوم یکی از مباحث زیر یه شبیه سازی تو متلب انجام بدم و نکاتش بررسی بشه؟
The shares total 118%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 23 January 2024 to 31 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 452,493 of 1,176,251entries 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.
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 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.
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“مهندس مخابرات” (@aitelecomeng), 201 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/aitelecomeng.
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.