Telegram RegisterThe public register of Telegram
Telegram profile photo for inoi post

Channel

inoi post

@inoipost

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

375subscribers

+3 since we began measuring on 20 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001886736232
TypeChannel
Username@inoipost
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live12 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/inoipost

Growth

37137537320 August 2026 — 372 subscribers20 August 2026 — 372 subscribers29 August 2026 — 371 subscribers4 September 2026 — 372 subscribers12 September 2026 — 375 subscribers20 August 202612 September 2026
5 measurements spanning 23 days, net +3. 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 370–376 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 06:20375+3
4 Sept 2026, 20:58372+1
29 Aug 2026, 03:34371-1
20 Aug 2026, 12:00372no change
20 Aug 2026, 11:45372first reading

Engagement

20 posts held, back to 24 June 2024the 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 20 posts for this entry, the most recent from 27 November 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
31s
Average length
31s

Measured directly from 1 video 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.

Reaction mix

631 reactions across 20 posts, in 24 distinct kinds. The most used accounts for 32.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥20532.5%
10116.0%
🤣7612.0%
🥰619.67%
💔477.45%
👍406.34%
🦄193.01%
👎142.22%
🤝121.90%
😢111.74%
🤡111.74%
💩81.27%
🗿81.27%
🤨50.792%
🍌40.634%
10.158%
🆒10.158%
🐳10.158%
💅10.158%
💯10.158%
4 further kinds40.634%

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 20 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 631 reactions 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 24 June 2024 to 27 November 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.

Recent posts

27 Nov 2024, 19:28 UTC≈2,900 views22 reactionsread 20 August 2026
Forwarded from @pargar_math_magazinePhoto

💠 امضای نامه جمعی از مدال آوران المپیادهای کشوری و جهانی پیرامون مشکلات مصوبه امتحانات نهایی به دبیر محترم شورای عالی انقلاب فرهنگی 💠 💠 لطفا به دست تمامی مدال آوران برسانید تا با همراهی هم مشکلات مصوبه را از دریچه نگاه المپیادی‌ ها به شورای عالی منتقل کنیم 💠 لینک امضا : https://forms.gle/ecrTAGWWP9iL5bHv6

🤝12🗿62👎1💯1

2 Oct 2024, 17:06 UTC≈3,290 views24 reactionsread 20 August 2026

https://docs.google.com/spreadsheets/d/1-IcqcbfvJyrv4ONRGCanDQ-13q_65Ikl6z4Pvk7EFvc/edit?gid=2119322658#gid=2119322658

🔥19💩5

2 Oct 2024, 16:01 UTC≈3,260 views37 reactionsread 20 August 2026

🔴 نتایج پس از اعمال اعتراض های المپیاد کامپیوتر. مدال طلا 🏅 1 76.23 رضائی 2 74.77 زارع 3 68.44 گلستانی 4 66.71 غفاری 5 65.36 یوسف نژاد 6 55.82 عاشوری 7 54.92 رحمانی 8 53.33 شایان مدال نقره 🥈 9 52.47 خلجی 10 52.29 امینی 11 50.98 استاد شریف 12 50.77 بختیاری 13 49.01 اصلاحی 14 48.78 رضوی 15 46.63 مسجدیان 16 46.07 نوری 17 45.83 جوکار 18 45.54 امیررضا فخری 19 45.00 پروین 20 44

🥰19🔥6👍3👎3💩31🥱1🆒1

17 Sept 2024, 08:13 UTC≈7,380 views43 reactionsread 20 August 2026

🔴 نتایج اولیه المپیاد کامپیوتر دقت کنید این نتایج مربوط به زمان قبل از اعتراض‌ها است و نمی‌تواند ملاک دقیقی باشد. مدال طلا 🥇 مانی زارع کیارش رضایی حامد غفاری آرش یوسف نژاد پارسا گلستانی محمدرضا عاشوری رادین رحمانی علی شایان مدال نقره 🥈 ایلیا خلجی پویان امینی آرش استاد شریف ایلیا اصلاحی شایان رضوی علی نظری فهرودی امیررضا فخری محمدپارسا پروین کیان نوری پارسا جوکار علیرضا فخری حمید شفیع زاده امیرمحمد نامدار سیدحمید حی

💔2310👍4🍌3👎2🔥1

5 Sept 2024, 14:50 UTC≈2,620 views77 reactionsread 20 August 2026

🔴 نتایج تیم ملی المپیاد کامپیوتر: 1. امیرعلی عسگری رتبه 19 مدال طلا 🥇 2. امیرحسین فرخنده فر رتبه 59 مدال نقره 🥈 3. امیررضا درستی رتبه 71 مدال نقره 🥈 4. پارسا فرجپور رتبه 127 مدال برنز 🥉 تبریک به همشون که افتخار آفریدن 🔥. #Yogi

61🔥8😢7😁1

29 Aug 2024, 12:25 UTC≈2,870 views34 reactionsread 20 August 2026

ویزا رو که نشد بگیرن ، ایشالا مدال

👍24🤡721

29 Aug 2024, 12:23 UTC≈3,450 views26 reactionsread 20 August 2026
Photo

پست کانال اعضای تیم المپیاد کامپیوتر. نظر به اینکه تاکنون ویزای ایشان نیامده، به نظر می‌رسد شرکت به صورت حضوری تقریباً منتفی است.

💔23👎3

23 Aug 2024, 13:20 UTC≈2,950 views59 reactionsread 20 August 2026
Photo

🔴 طبق توییت دکتر شریفی، تیم اسرائیل از حضور در المپیاد جهانی 2024 کامپیوتر مصر منع شده است

🔥40🤣8👍4👎42💔1

21 Aug 2024, 08:25 UTC≈2,600 views40 reactionsread 20 August 2026
Photo

هم اکنون حضور زنده دو نفر از اعضای تیم هوش مصنوعی در شبکه آموزش

🤣306🔥3💅1

14 Aug 2024, 16:12 UTC≈2,440 views17 reactionsread 20 August 2026
Video

بخشی از اختتامیه و ویدیوی کپشن همان پست.

14🔥3

14 Aug 2024, 16:06 UTC≈2,350 views34 reactionsread 20 August 2026
Photo

توئیت دکتر شریفی از برگزار کنندگان این المپیاد. به داشتن چنین دانش آموزانی افتخار می‌کنیم.

🔥322

14 Aug 2024, 16:02 UTC≈2,070 views34 reactionsread 20 August 2026

🔴💻 تیم المپیاد هوش مصنوعی ایران توانست به مدال برنز دست یابد 🥉

🔥34

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

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.

Codeforces Official
@codeforces_official · 72,950
Telegram ranks this channel #37 of 78 here — alongside 77 others — read 20 August 2026
Quera
@quera_ir · 25,560
Telegram ranks this channel #47 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 12 September 2026 — this entry's latest reading, not the date you are reading this.

“inoi post” (@inoipost), 375 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/inoipost.

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.