Channel
@ece_tabrizu
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,860subscribers
+0 since we began measuring on 19 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001071218139 |
|---|---|
| Type | Channel |
| Username | @ece_tabrizu |
| Description | کانال اطلاع رسانی دانشکده مهندسی برق و کامپیوتر دانشگاه تبریز |
| Created | Between 1 October 2016 and 31 July 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ece_tabrizu |
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
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.
2,780 average views per post against 3,860 subscribers — an engagement rate of 72.0%. Across the 1,909 registered channels in the same cohort — 3,167–9,999 subscribers, posting mainly in Persian — the middle half sit between 3.40% and 14.2%, with a median of 7.38%.
| Window | 30 days (24 August 2026 – 23 September 2026) |
|---|---|
| Posts measured | 20 of 20 published in the window (0 exact, 20 rounded by Telegram) |
| Views totalled | 55,580 |
| Mature posts only | 72.0% over 20 posts read at least 24h after publication |
| Subscribers | 3,860 measured 19 September 2026 |
| Cohort | b3162:fas · 1,909 channels · p10 1.58% · p25 3.40% · p50 7.38% · p75 14.2% · p90 24.6% |
| Position in cohort | 99.266th percentile · 9.8× the cohort median |
| Uncertainty | ±0.023% of the figure, from Telegram’s rounding |
| Post language | Persian · 100.0% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 23 September 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 16:22 | 3,860 | no change |
| 19 Sept 2026, 15:47 | 3,860 | first reading |
20 posts held, back to 3 September 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 1 page of 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. It is computed over the 18 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 September 2026 |
|---|---|
| Posts held | 20 (3 September 2026 – 15 September 2026) |
| Views total | 55,580 |
| Reactions total | 220 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Sept 2026, 16: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.
Lifetime counters from Telegram’s own channel header, read 19 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
220 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 39.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 86 | 39.1% | |
| 🤬 | 47 | 21.4% | |
| 🤩 | 32 | 14.5% | |
| 👍 | 29 | 13.2% | |
| 😁 | 15 | 6.82% | |
| 👎 | 6 | 2.73% | |
| 🔥 | 2 | 0.909% | |
| 🤯 | 2 | 0.909% | |
| 🎉 | 1 | 0.455% |
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 18 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 220 reactions 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 3 September 2026 to 15 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.
شروع نیمسال تحصیلی ۱۴۰۶-۱۴۰۵ با سلام و احترام؛ ضمن تبریک و شادباش پیشاپیش فرارسیدن ماه مهر و آغاز سال تحصیلی، به اطلاع دانشجویان عزیز دانشگاه تبریز می رساند با توجه به کثرت جلسات دفاع از پایان نامه های کارشناسی ارشد و رساله های دکتری در هفته پایانی شهریورماه، جهت رفاه حال دانشجویان عزیز، شروع سال تحصیلی دانشگاه تبریز، به صورت حضوری و از روز شنبه چهارم مهرماه خواهد بود.
🤬43🤩27❤7👍5👎4
Signed Reza Movahed
دانشجویان رشته مهندسی کامپیوتر-گرایش هوش مصنوعی، درس رایانش عمیق را با کد ۹۴۸۵۳۰۲ ( استاد درس: دکتر شعاران ) اخذ نمایند. دانشجویان سایر گرایشها در صورت علاقه به اخذ این درس، درس را با کد ۹۴۸۴۳۲۷ (استاد درس: دکتر کوهستانی) اخذ نمایند.
❤1
Signed Reza Movahed
درس مهارت های زندگی
😁14❤1👍1
Signed Reza Movahed
سلام. از دانشجویان ورودی ۱۴۰۱ و ۱۴۰۲ کسی هست که نقشه کشی صنعتی پاس نکرده باشه؟ اگر بله، به اینجانب اعلام بفرمایید. در دانشکده خودمان به شکل یک درس ۱ واحدی ارائه بدیم. از جای دیگه اخذ نکنید.
👍4
Signed Hadi Soofi
File, posted without a caption
Signed Hadi Soofi
File, posted without a caption
Signed Hadi Soofi
سلام. دروسی که ظرفیت تمام گروه های اون تکمیل شده به شکل کامنت زیر همین پست ارسال کنید. حدود ۳.۳۰ یا ۴ برمیگردم دانشگاه ظرفیت باز میکنم. فقط دقت کنید اگر درسی نوشته شده، دوباره ننویسید. اگر ظرفیت تمام گروه ها تکمیل نشده، باز نخواهد شد. پ.ن: در همین کامنت ها، سوالات یا مسائل خود رو مطرح کنید، تا حد توان پاسخ میدم.
❤34🤬3🔥1😁1
1- در ایام انتخاب واحد نیمسال دوم، دروس افتاده در تاریخ های23-22 شهریور ماه 1405 به طور موقت به عنوان گذرانده منظور خواهد شد و متعاقبا در مورخ 25/06/1405 سیستم به وضعیت عادی بازگردانده می شود تا دانشجویان بتوانند نسبت به اخذ دروس افتاده خود اقدام نمایند. 2- در ایام حذف و اضافه نیمسال مذکور، مورخ 14/07/1405 نیز دروس افتاده به طور موقت، گذرانده تلقی شده و در تاریخ 15/07/1405 سیستم به حالت عادی باز خواهد گشت، تا دانشجو…
❤1
دروس پروژه و کارآموزی درصورت تکمیل ظرفیت در ایام حذف و اضافه، ظرفیت اضافه خواهد شد.
❤7
• دانشجویان مهندسی کامپیوتر ورودی 1402 (چارت جدید) به بعد باید درس کارآموزی 2 واحدی با کد درس 513480 را اخذ کنند. درس کار آموزی با کد 513114 مخصوص دانشجویان قبل از ورودی 1402 (چارت قدیم) است. • دانشجویان مهندسی کامپیوتر ورودی 1402 به بعد (چارت جدید) که دروس طراحی بازیهای رایانهای، برنامهسازی وب و برنامهنویسی دستگاههای سیار را خارج از چارت مصوب ۸ ترمه گروه آموزشی اخذ نمودهاند، در صورت نداشتن مجوز کتبی از مدیر گر…
🎉1👍1👎1
۶. درس علوم و معارف دفاع مقدس و مقاومت، فقط برای ۱۴۰۳ به بعد الزامی است. کد این درس متفاوت است و واحد و نمره آن در تعداد کل واحدهای گذرانده و معدل کل دخالت ندارد و لذا به هیچ وجه جایگزین دروس معارف نیست و دانشجویان ۱۴۰۲ و ماقبل آن را اخذ نکنند.
۵. دانشجویان ورودی ۱۴۰۲ و ماقبل: -به جای درس سیستم دیجیتال ۲، معماری کامپیوتر و میکروکنترلر - به جای الکترونیک ۲ دو واحدی، الکترونیک ۲ سه واحدی - به جای تحلیل سیستم های انرژی الکتریکی ۱، سیستم های انرژی الکتریکی - به جای الکترونیک ۱ دو واحدی، الکترونیک ۱ سه واحدی - به جای سیستم های دیجیتال ۱، مدارهای منطقی - به جای مدارهای الکتریکی ۲ دو واحدی، مدارهای الکتریکی ۲ سه واحدی اخذ کنند.
❤2
Showing the 12 most recent of 20 posts we hold for @ece_tabrizu. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“کانال اطلاع رسانی آموزش دانشکده مهندسی برق و کامپیوتر” (@ece_tabrizu), 3,860 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ece_tabrizu.
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.