Channel
@AlmatyCodeCup
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
572subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001897545640 |
|---|---|
| Type | Channel |
| Username | @AlmatyCodeCup |
| Created | Between 1 November 2022 and 31 July 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 | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/AlmatyCodeCup |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 16:26 | 572 | -1 |
| 7 Aug 2026, 03:00 | 573 | first reading |
17 posts held, back to 22 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 9 August 2025. An engagement rate over an empty window would be a number about nothing.
149 reactions across 14 posts, in 7 distinct kinds. The most used accounts for 52.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 78 | 52.3% | |
| ❤ | 51 | 34.2% | |
| 😱 | 7 | 4.70% | |
| 🤯 | 6 | 4.03% | |
| 🥰 | 3 | 2.01% | |
| 👍 | 2 | 1.34% | |
| 😍 | 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 17 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 17 most recent posts we hold, published 22 July 2024 to 9 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
📢 ACC x QPC — Important Notice We have sent messages to all qualified teams via WhatsApp. If you do not confirm your participation by 10:00 UTC, your team will be disqualified and your slot will be given to another team. Please reply as soon as possible to keep your spot!
❤6
🗓 ACC x QPC — Event Schedule August 23 Arrival at any time to NPhMS dormitory (Almaty, Bukhar Zhyrau Blvd. 36) 13:00 — Lunch 18:00 — Dinner August 24 09:00 — Breakfast (boarding school participants) 09:30 — Transfer to PhysTech 11:00 — Opening Ceremony 12:00 — Contest Start 17:00 — Contest End 17:00–18:00 — 🍽 Lunch / Snack Break 18:00 — Award Ceremony 19:00 — Transportation to dormitory 19:30 — Dinner (boarding sc…
🔥13
🔖 Mirror of the Qualifier is available! Want to try the problems from the ACC x QPC 2025 online round? You can now participate in the official mirror contest on Codeforces: 👉 https://codeforces.com/contestInvitation/a1053f565b314672d21a77fd37c954301c522350
📊 ACC x QPC Qualifier — Registration Stats 🔥Teams: 181 total — 127 from Kazakhstan — 54 international 🏙 Geography: — 79 unique cities (32 in Kazakhstan, 47 abroad) — 15 countries in total (14 foreign + Kazakhstan)
🔥8😱4
📩 Check Your Inbox! — Login Details Sent All registered teams for ACC x QPC 2025 should have received their login credentials for the qualifier via email. Make sure to check the inbox and spam folder of the email address used during registration. ✉️ The email contains: • Your Codeforces login and password • A reminder of the contest time and proctoring requirements 🚨 Didn’t receive it? Contact us immediately via t…
🥰3
File, posted without a caption
❤1
📢 Reminder: The Qualifier is tomorrow! The online round of ACC x QPC 2025 will take place on August 6 (5:00–10:00 UTC) — on Codeforces, with full proctoring. Make sure you’re ready: 🔖 Read the Qualifier Regulations 📸 Prepare your camera + mic 🌐 Stable internet is a must ✏️ All important documents are below:
🔖 Prepare for ACC x QPC 2025! 💎 Want to know what kind of problems you’ll face? You can now try out last year’s final round here: https://codeforces.com/gym/105271 📌 This archive contains all the tasks from the 2024 onsite finals in Almaty — with full statements, test data, and the original setup. 🔥 ACC x QPC is coming.
❤8
🏆 Prize Pool Revealed — ACC x QPC 2025! Ready to turn code into cash? 😀 Here’s what the top 6 teams will earn after battling it out in the finals: 🥇 1st place — 1000 USDT 🥈 2nd place — 700 USDT 🥉 3rd place — 500 USDT 💻4th place — 400 USDT 💻 5th place — 250 USDT 💻 6th place — 150 USDT 💰 Total prize pool: 3000+ USDT You bring the logic, the teamwork, and the grind — we’ll bring the challenge and the rewards. 💥 This is …
❤15🤯2😱2
🎉 Dates Announced for ACC x QPC 2025! 😀 The Qualifier will take place on August 6 (5:00-10:00 UTC) — online with proctoring on Codeforces. 👑 The Final Round will be held on-site in Almaty on August 23–24, featuring the top 32 teams! (Check-in will be on the 23rd, final on the 24th) ‼️ Registration has been extended until August 4 (inclusive) — don’t miss your chance! 📌 Registration form: https://forms.gle/d7Gyg3FL…
🔥6❤1
Got questions❓ Looking for teammates❓ Want to chat with other participants? We’ve got you covered — join our official Telegram group! It’s the place to: • 💭Ask anything about ACC x QPC — rules, rounds, registration; • 👥Find a team or teammate before the deadline; • 👀Talk with other contestants and organizers; • 📢Stay updated on all announcements. But more than that — it’s a community. 🌱A space for everyone who’s t…
❤4
Channel photo updated
Showing the 12 most recent of 17 posts we hold for @AlmatyCodeCup. 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 — 832,039 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.
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.
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.
“Almaty Code Cup” (@AlmatyCodeCup), 572 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/AlmatyCodeCup.
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.