Channel
@codecup
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,644subscribers
-8 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001073828748 |
|---|---|
| Type | Channel |
| Username | @codecup |
| Created | 31 October 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/codecup |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 12:54 | 1,644 | -3 |
| 9 Aug 2026, 11:51 | 1,647 | -2 |
| 6 Aug 2026, 21:30 | 1,649 | -3 |
| 6 Aug 2026, 07:19 | 1,652 | no change |
| 5 Aug 2026, 22:15 | 1,652 | first reading |
15 posts held, back to 17 May 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 2 pagesof 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 15 posts for this entry, the most recent from 18 August 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
149 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 44.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 66 | 44.3% | |
| 👍 | 35 | 23.5% | |
| 🔥 | 34 | 22.8% | |
| 👎 | 6 | 4.03% | |
| 👏 | 6 | 4.03% | |
| 😢 | 2 | 1.34% |
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 14 of the 15 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 149reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 17 May 2024 to 18 August 2024, 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://quera.org/r/n8ev6 ➖➖➖➖➖ #Quera #CodeCup8
🔥9👍2👏2
🏁 ویدئوی اختتامه «هشتمین دوره از مسابقات ملی برنامهنویسی کدکاپ» ➖➖➖➖➖ #Quera #CodeCup8
❤12👎1😢1
🏆#کدکاپ، مسابقهای به وسعت #ایران مسابقات لیگ #برنامه_نویسی کدکاپ ۸ بعد از ۵ ماه تموم شد! 🤩 ⭐️فینال این مسابقات با حضور ۱۴۰ دانشجو و دانشآموز برنامهنویس با تمرکز بر مهارتهای حل مسئله و #الگوریتم در دانشگاه علم و فرهنگ برگزار شد. 🎊پارسا پردلی بهروز، علیرضا کاویانی، کوشا موسوی، علی صفری و علیرضا کشاورز جایگاههای اول تا پنجم این مسابقه بودن و جوایز خودشون رو دریافت کردن. 💡دکتر دهقانی فیروزآبادی، مدیر اجرایی و م…
❤15👏4👍2
🎁 رونمایی از جوایز غیر نقدی کدکاپ۸ 🏆 کاپی پر از جایزه و هدیه 👨🏻💻 تیشرت ویژه کدکاپ، ماگ طرح کدکاپ، دفترچه و یادبودهای ریز و درشت دیگه 🏆مسابقه فینال کدکاپ۸ قراره ۱ مرداد به صورت حضوری توی تهران برگزار بشه... 🏅از سراسر ایران توی این مسابقه شرکتکننده داریم و اختتامیه این مسابقه هم با حضور ۱۴۰ نفر از راهیافتگان به مرحله نهایی همراه با اهدای جوایز نقدی انجام خواهد شد... ➖➖➖➖➖ #Quera #CodeCup8 #مسابقه_برنامه_نویسی
🔥12👍7👎3😢1
☑️ وبینار حل سؤالات مسابقه کدکاپ انتخابی ۶، شروع شد... 🔘 از لینک زیر به صورت میهمان وارد وبینار بشین: https://quera.org/r/jvb2v ➖➖➖➖➖ #Quera #CodeCup8 #مسابقه_برنامه_نویسی #کدکاپ
👍2
📣 ششمین مرحله مسابقه کدکاپ۸ شروع شده 🔔 اگه هنوز وارد نشدی از لینک زیر بیا تو مسابقه: https://quera.org/contest/ ➖➖➖➖➖ #Quera #Quera_contest #Codecup
🔥4
سلام به همراهان عزیز کدکاپ،👋🏻 ☑️ وبینار حل سؤالات مسابقه کدکاپ، امروز ساعت ۱۹:۳۰ برگزار میشه... 🎁 توی این وبینار علاوه بر حل سوالات مسابقه انتخابی ۶ کدکاپ، از هر استان به ۳ نفر از شرکتکنندگان حاضر توی وبینار به قید قرعه یک دوره مقدماتی یا پیشرفته کوئرا کالج هدیه داده میشه. 🎉 همچنین به ۱۰ نفر از شرکتکنندگان توی مسابقه، به قید قرعه تیشرت کدکاپ هدیه داده میشه... 🔘 از لینک زیر به صورت میهمان وارد وبینار بشین: h…
❤2
کدکاپیهای عزیز سلام👋 🔔 یادتون نره فردا ساعت ۱۶ ششمین مرحله از مسابقات کدکاپ۸ برگزار میشه. 💎 با ارسال یک کد علاوه بر رقابت استانی میتونین دوره آموزشی رایگان و تیشرت یادبود کدکاپ رو برنده بشین. افزودن به تقویم برای آمادگی بیشتر میتونین به مسابقه دستگرمی سر بزنین: https://quera.org/r/4hkps ➖➖➖➖➖ #Quera #CodeCup8 #مسابقه_برنامه_نویسی #کدکاپ
🔥7👍1
🎉نفرات برتر دوره پنجم مسابقه کدکاپ توی بلاگ قرار گرفته و میتونین اسامی رو مشاهده کنین... 💎مسابقه ۱۸ خرداد، آخرین مرحله مسابقه کدکاپ هست که برای رقابت استانی هنوز فرصت دارین ... 🔮اسامی نفرات برتر تا مسابقه پنجم: https://quera.org/blog/code-cup-8-finalists/ ➖➖➖➖➖ #Quera #CodeCup8 #مسابقه_برنامه_نویسی #کدکاپ
👍7
🇮🇷 برنامهنویسهای شهر #ایلام مسابقه ۱۸ خرداد رو یادتون نره.. ۱ روز مونده تا مسابقه 🏎 مسابقه انتخابی ششم: ۱۸ خرداد 🏁 مسابقه نهایی(حضوری): تیر ۱۴۰۳ 🏎️ دوستت رو به رقابت دعوت کن 🔗 https://quera.org/r/7nm0p ➖➖➖➖➖ #Quera #CodeCup8 #مسابقه_برنامه_نویسی #کدکاپ
❤14👍1
🇮🇷 برنامهنویسهای استان #گیلان مسابقه ۱۸ خرداد رو یادتون نره.. 🏎 مسابقه انتخابی ششم: ۱۸ خرداد 🏁 مسابقه نهایی(حضوری): تیر ۱۴۰۳ 🏎️ دوستت رو به رقابت دعوت کن 🔗 https://quera.org/r/7nm0p ➖➖➖➖➖ #Quera #CodeCup8 #مسابقه_برنامه_نویسی #کدکاپ
❤15🔥2👍1👎1
🌀 به شروع مسابقه نهایی کدکاپ۸ فرصت زیادی باقی نمونده… #الگوریتم 🏎 مسابقه انتخابی ششم: ۱۸ خرداد 🏁 مسابقه نهایی(حضوری): تیر ۱۴۰۳ 🎁 بیش از ۴۰۰ میلیون جایزه نقدی 🇮🇷 برنامهنویسهای استان #یزد مسابقه ۱۸ خرداد رو یادتون نره.. 🏎️ دوستت رو به رقابت دعوت کن 👇 🔗 https://quera.org/r/7nm0p ➖➖➖➖➖ #Codecup #Quera #Codecup8 #لیگ_ملی_برنامه_نویسی #کدکاپ۸ #Algorithm
❤8👍3
Showing the 12 most recent of 15 posts we hold for @codecup. 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 — 360,461 of 1,160,990entries 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.
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.
Named by 4 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“CodeCup” (@codecup), 1,644 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/codecup.
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.