Channel
@BP_EE_2024
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
326subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002188576479 |
|---|---|
| Type | Channel |
| Username | @BP_EE_2024 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/BP_EE_2024 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 13:17 | 326 | -1 |
| 8 Aug 2026, 07:19 | 327 | no change |
| 7 Aug 2026, 14:30 | 327 | first reading |
20 posts held, back to 4 January 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 17 February 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
281 reactions across 17 posts, in 15 distinct kinds. The most used accounts for 31.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 87 | 31.0% | |
| 👎 | 59 | 21.0% | |
| ❤ | 46 | 16.4% | |
| 😭 | 44 | 15.7% | |
| 💔 | 23 | 8.19% | |
| 🌚 | 5 | 1.78% | |
| 🤓 | 4 | 1.42% | |
| 😁 | 3 | 1.07% | |
| 🤷♀ | 3 | 1.07% | |
| 🕊 | 2 | 0.712% | |
| ⚡ | 1 | 0.356% | |
| 👍 | 1 | 0.356% | |
| 👾 | 1 | 0.356% | |
| 🥰 | 1 | 0.356% | |
| 🫡 | 1 | 0.356% |
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 281reactions 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 4 January 2025 to 17 February 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.
📝 دستیاری آموزشی مبانی برنامه سازی ▫️دانشجویان محترمی که تمایل دارند در درس مبانی برنامه سازی ۰۵-۱۴۰۴ دستیار آموزشی دکتر وثوقی وحدت باشند، نسبت به تکمیل فرم زیر تا حداکثر ۲ اسفند اقدام نمایند. 🔗 https://docs.google.com/forms/d/1lj99QFXlGIjf3-h-sBLtDI0VHIJTr-KkDm0sMqsWf5o/edit?usp=sharing_eip_se_dm&ts=699496b9 🆔 @FoP_EE_2025
👎6
📝 دستیاری آموزشی برنامهنویسی شیء گرا ▫️دانشجویان محترمی که تمایل دارند در درس برنامه نویسی شی گرا ۰۵-۱۴۰۴ ، دستیار آموزشی دکتر آراسته باشند، نسبت به تکمیل فرم زیر تا حداکثر ۲ اسفند اقدام نمایند. 🔗 https://docs.google.com/forms/d/1SQHlWbpBqM6IA8jtk9-0KYRSgFqGyG4ZVOdgPgYHbN0/edit?usp=sharing_eip_se_dm&ts=69949618 🆔 @FoP_EE_2025
👎7🫡1
📝 دستیاری آموزشی مبانی برنامهنویسی ▫️دانشجویان محترمی که تمایل دارند در نیمسال اول ۰۵-۱۴۰۴ دستیار آموزشی درس مبانی برنامهنویسی، گروه دکتر وثوقی وحدت- دکتر آراسته باشند، نسبت به تکمیل فرم زیر تا حداکثر ۳۱ شهریور اقدام نمایند. 🔗 https://docs.google.com/forms/d/e/1FAIpQLSfnMTP3S781zD2AIThttBCDpuZMli_7RBpqJ2nVdoqzcbvI7A/viewform?usp=dialog 🆔 @OOP_EE_2025
👎29❤1🤓1
🏆 گروه ۶۴ مهیار صابریفر - حنانه حق پرست 🆔 @BP_EE_2024
🔥25
🏆 گروه ۴۴ روزبه اسمعیلپور - رادین حیدر 🆔 @BP_EE_2024
🔥12
🏆 گروه ۱۰۱ پارسا صفری تورج - شایان حاجی محمدی 🆔 @BP_EE_2024
🔥23😁2❤1
« حسن ختام » چند روزی از شروع ترم جدید و پایان ترم یک و درس مبانی برنامه نویسی میگذره اما طبق قراری که گذاشته بودیم، سه تا از پروژه های برتر رو معرفی میکنیم. 🏆 گروه ۴۴ روزبه اسمعیلپور - رادین حیدر 🏆 گروه ۶۴ مهیار صابریفر - حنانه حق پرست 🏆 گروه ۱۰۱ پارسا صفری تورج - شایان حاجی محمدی فیلم های پروژه این گروه ها هم زیر این پیام ارسال میشوند. و در آخر امیدواریم ترم پیشروی خوبی رو بگذرونید. 🆔 @BP_EE_2024
🔥26👎6❤1💔1😁1
« نمرات نهایی درس » نمرات نهایی درس به زودی در بات قرار خواهند گرفت. همچنین نمرات به اساتید هم ارسال شده و به زودی در سامانه ایدیو قرار داده میشوند. اگر اعتراضی به این نمرات دارید، نهایت تا ساعت 20 به @Mostafa_P_A پیام دهید. با ارزوی موفقیت در درس های آتی🌹 🆔 @BP_EE_2024
❤5🌚4👎1
برای اعتراض به سالن برکشلی مراجعه کنید.
🗞 «نتایج پایانترم» 🔸 هم اکنون نمرات پایانترم در بات قابل مشاهده است. 🔹 چنانچه درخواست بازبینی نسبت به برگه پایانترم خود دارید، روز یکشنبه ۲۱ بهمن بعد از کلاس OOP به مکانی که متعاقبا اعلام میشود مراجعه کنید . 🔸 اعتراض بیجا میتواند موجب کسر نمره گردد! 🔹 به این دو پیام ( ۱ و ۲ ) پیرامون اعتراض تمرین و .. توجه شود. #پایانترم 🆔 @BP_EE_2024
« محل ارائهها ۲ » خانم میرعابدینی، برق ۷ آقای فیروزی، برق ۸ آقای یوسفی نیا، برق ۹ آقای مهرانی کیا، آزمایشگاه مخلوقات مصنوعی، طبقه دوم ( برق جدید ) 🆔 @BP_EE_2024
❤1🔥1
« محل ارائهها » خانم میرعابدینی، برق ۳۰۱ آقای فیروزی، برق ۳۱۶ آقای یوسفی نیا، برق ۹ 🆔 @BP_EE_2024
💔3❤2🕊2🤓2
Showing the 12 most recent of 20 posts we hold for @BP_EE_2024. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
“Basic Programming EE 2024” (@BP_EE_2024), 326 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/BP_EE_2024.
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.