Telegram RegisterThe public register of Telegram
Telegram profile photo for Algorithm Arena

Channel

Algorithm Arena

@algorithm_arena

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,008subscribers

+129 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001930679766
TypeChannel
Username@algorithm_arena
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live24 September 2026
Measurements held7
Confirmed unchanged2 times, most recently 24 September 2026
On Telegramt.me/algorithm_arena

Topic

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.

Growth

8681,0089387 August 2026 — 879 subscribers7 August 2026 — 879 subscribers15 August 2026 — 878 subscribers23 August 2026 — 873 subscribers30 August 2026 — 868 subscribers8 September 2026 — 983 subscribers16 September 2026 — 1,008 subscribers7 August 202616 September 2026
7 measurements spanning 41 days, net +129. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 847–1,029 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 22:011,008+25
8 Sept 2026, 21:01983+115
30 Aug 2026, 05:14868-5
23 Aug 2026, 11:27873-5
15 Aug 2026, 01:58878-1
7 Aug 2026, 22:03879no change
7 Aug 2026, 02:45879first reading

Engagement

14 posts held, back to 28 October 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 page of 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 14 posts for this entry, the most recent from 5 November 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

21 reactions across 5 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
⚡21100.0%

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 14 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 21 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 28 October 2025 to 5 November 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.

Recent posts

5 Nov 2025, 13:25 UTC808 viewsread 7 August 2026

▶️هم‌اکنون کارگاه حل سوالات سال گذشته ACPC در حال شروع شدن است. 🔗لینک شرکت در جلسه

5 Nov 2025, 10:01 UTC848 views6 reactionsread 7 August 2026

🔔یادآوری: کارگاه حل سوالات سال گذشته ACPC ساعت ۱۷ با حضور آرمین حامد عظیمی برگزار می‌شه. ▶️ارائه به صورت مجازی و در اسکای‌روم برگزار و لینک اون دقایقی پیش از آغاز در اینجا فرستاده می‌شه. 👽شرکت در این کارگاه رایگان و برای عموم علاقه‌مندان آزاد است. 🌐 Telegram 🌐 Instagram

⚡6

3 Nov 2025, 20:18 UTC739 views4 reactionsread 7 August 2026
Forwarded from @AUTICPCPhoto

🧓یه خبر خوب داریم براتون 🤖 قراره یه کارگاه حل سوال داشته باشیم تا برای مسابقه روز جمعه بیش از پیش آماده بشید. 👩‍🚀 تو این کارگاه قراره سوال‌های دوره گذشته حل بشه که با سطح مسابقه و روش‌های حل مسائل اون آشنا بشید. 👽 شرکت در این کارگاه برای عموم علاقه‌مندان آزاد و رایگان است. ⏱زمان: چهارشنبه ساعت ۱۷ 🎙با حضور آرمین حامد عظیمی دارنده ۳ مدال نقره icpc و مدال برنز المپیاد دانشجویی و دانش‌آموزی🥈🥉 ▶️این کارگاه حل مسئله …

⚡4

2 Nov 2025, 13:27 UTC677 viewsread 7 August 2026
Forwarded from @AUTICPCPhoto

📣زمان ارائه‌های «الگوریتمیک ترید» و «چگونه "منطق بلمن" بازی آربیتراژ را در DeFi هک می‌کند؟» تغییر پیدا کرد. 🗓تاریخ: دوشنبه ۱۲ آبان 💱ارائه: «الگوریتمیک ترید» ⏰ساعت ۱۶:۳۰ تا ۱۸ 🗓تاریخ: سه‌شنبه ۱۳ آبان 🎮ارائه: «چگونه "منطق بلمن" بازی آربیتراژ را در DeFi هک می‌کند؟» ⏰ساعت ۱۶:۳۰ تا ۱۸ 📍آمفی‌تئاتر دانشکده مهندسی کامپیوتر دانشگاه امیرکبیر

30 Oct 2025, 20:17 UTC826 viewsread 7 August 2026

🤔کد زده شده در کارگاه امروز: https://codeforces.com/problemset/submission/320/346580250

30 Oct 2025, 05:40 UTC871 viewsread 7 August 2026

🧑‍💻👩‍💻 لینک سوالات کارگاه امروز که قرار هست بررسی شوند: Dfs and Bfs: https://codeforces.com/problemset/problem/320/B https://codeforces.com/problemset/problem/862/B Number theory: https://codeforces.com/problemset/problem/1855/B https://codeforces.com/problemset/problem/1838/C

29 Oct 2025, 15:36 UTC770 viewsread 7 August 2026

⚠️یادآوری: کارگاه سوم (و آخر) فردا ساعت ۹ صبح تا ۱۲ ظهر برگزار می‌شود. 🙂برای ورود به دانشگاه از درهای حافظ، سعید و رشت دانشگاه امیرکبیر می‌توانید اقدام کنید و اسم شما به حراست از قبل اعلام خواهد شد و نگرانی‌ای از این بابت نداشته باشید.

28 Oct 2025, 20:36 UTC885 views2 reactionsread 7 August 2026

🤔مسائلی که استاد انوری برای تمرین بیشتر ارسال کردن: https://codeforces.com/problemsets/acmsguru/problem/99999/275 https://codeforces.com/contest/472/problem/F https://codeforces.com/problemset/problem/1411/G 💻منبع برای مطالعه: https://cp-algorithms.com/linear_algebra/linear-system-gauss.html ✔️برای نظریه اعداد هم پیشنهاد دادن تگ number theory رو توی سایت codeforces سرچ کنید و سوال حل کنید. سایت projecteuler هم سوالا…

⚡2

Showing the 12 most recent of 14 posts we hold for @algorithm_arena. 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.

Forward network

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.

Mentions

Named by 7 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.

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.

Appears in Telegram’s recommendations for other channels

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.

امیرکبیری‌ها
@amirkabiriha · 35,528
Telegram ranks this channel #39 of 93 here — alongside 92 others — read 2 September 2026
Quera
@quera_ir · 25,521
Telegram ranks this channel #43 of 93 here — alongside 92 others — read 14 September 2026

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.

Cite this entry

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“Algorithm Arena” (@algorithm_arena), 1,008 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/algorithm_arena.

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.