Channel
@ICPCNews
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,074subscribers
+9 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001224339512 |
|---|---|
| Type | Channel |
| Username | @ICPCNews |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/ICPCNews |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 12:45 | 2,074 | +2 |
| 9 Aug 2026, 03:53 | 2,072 | +7 |
| 6 Aug 2026, 06:19 | 2,065 | no change |
| 6 Aug 2026, 01:44 | 2,065 | first reading |
5 posts held, back to 28 April 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 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 5 posts for this entry, the most recent from 20 June 2026. An engagement rate over an empty window would be a number about nothing.
35 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 31.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 31.4% | |
| 🔥 | 10 | 28.6% | |
| 💅 | 7 | 20.0% | |
| 👏 | 4 | 11.4% | |
| 👎 | 2 | 5.71% | |
| 🥰 | 1 | 2.86% |
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 5 of the 5 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 35reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 28 April 2026 to 20 June 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.
ICPC is honored to present to you the inaugural Europe Women's Programming Contest (EWPC)! Top 20 contestants of the online qualifier on July 4 advance to the onsite finals in Stockholm, August 21–24, with travel and accommodation provided. EWPC exists to inspire, promote, and celebrate exceptional women in algorithmic problem solving — strengthening the pipeline of women in competitive programming and supporting t…
❤9💅7
🌟 A warm thank you to Bending Spoons , ICPC Sponsor for supporting the 2025 ICPC Europe Regionals - ICPC SWERC, ICPC SEERC, and ICPC CERC . 🌟 As a company dedicated to building and improving digital platforms used by millions, we share a common passion for solving complex challenges with simplicity and engineering rigor! 👏 #ICPC #BendingSpoons #CodingCommunity #FutureLeaders #TechTalent #Gratitude
🥰1
🌟 Thank you Pinely, ICPC Sponsor for supporting the 2026 ICPC Europe Championship! 🌟 With several ICPC alumni on their team, Pinely shares a natural connection to the spirit of competitive programming. Your support added to what made this event memorable. 👏 #ICPC #Pinely #CodingCommunity #FutureLeaders #TechTalent #Gratitude
👏4👎2
🌟 A sincere thank you to Citadel and Citadel Securities, ICPC Platinum Sponsor for ICPC NAC and ICPC Gold Sponsor for ICPC EUC and ICPC Asia East Continent Finals. 🌟 We appreciate the support and delighted to have Citadel as part of the ICPC community. By tackling some of the most demanding challenges in the industry, your company is helping shape the future of high-frequency trading and security. 🔒 #ICPC #Citadel …
❤2🔥2
🌟 Thank you Alber Blanc, ICPC Gold Sponsor, for supporting the 2025 ICPC SWERC and 2025 ICPC NWERC! 🌟 With several ICPC alumni on the team, Alber Blanc’s focus on high‑performance algorithmic systems reflects a strong connection to the spirit of competitive programming. 🏆 👏 #ICPC #AlberBlanc #TechCommunity #ProblemSolvers #Gratitude
🔥8
Showing the 5 most recent of 5 posts we hold for @ICPCNews. 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 — 209,008 of 1,169,250entries 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.
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 2 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.
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.
“ICPCNews” (@ICPCNews), 2,074 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ICPCNews.
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.