Telegram RegisterThe public register of Telegram
Telegram profile photo for Форум ИнПарк

Channel

Форум ИнПарк

@forum_inpark

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

370subscribers

-2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001969785894
TypeChannel
Username@forum_inpark
Created28 August 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/forum_inpark

Growth

369372370.57 August 2026 — 372 subscribers8 August 2026 — 372 subscribers16 August 2026 — 369 subscribers24 August 2026 — 370 subscribers30 August 2026 — 372 subscribers17 September 2026 — 370 subscribers3707 August 202617 September 2026
6 measurements spanning 41 days, net -2. 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 369–372 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 09:18370-2
30 Aug 2026, 16:46372+2
24 Aug 2026, 02:08370+1
16 Aug 2026, 19:38369-3
8 Aug 2026, 06:19372no change
7 Aug 2026, 19:50372first reading

Engagement

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

What this channel posts

Video runtime
8m 43s
Average length
1m 45s

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

Reaction mix

152 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 37.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5737.5%
👍4026.3%
👏2516.4%
95.92%
🍓63.95%
🤗42.63%
🤩42.63%
👨‍💻31.97%
🤝31.97%
10.658%

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

Measured over the 10 most recent posts we hold, published 14 November 2025 to 25 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

25 Nov 2025, 02:43 UTC353 views12 reactionsread 8 August 2026
Video

Каждый участник форума что-то берёт для себя и что-то привносит в общую копилку знаний. Лев Решетников, генеральный директор ООО «Дорхан Восток Девелопмент», поделился своим опытом.

👍6👏3🔥3

24 Nov 2025, 06:24 UTC390 views12 reactionsread 8 August 2026

Как создать новый технологичный индустриальный парк? Смотрим подкаст Романа Исайкина! Гости — Денис Журавский, Леонид Данилов и Александр Нам. 📺 https://rutube.ru/video/1d81b0f9fb1b9591f70c38f64ccc3ae3/

🔥7👍3👏2

24 Nov 2025, 03:59 UTC326 views10 reactionsread 8 August 2026
Video

Егор Казанцев, управляющий, индустриальный парк «Город Мастеров», делится впечатлениями об ИнПарке. Благодарим!

👍4👏3🔥3

21 Nov 2025, 05:51 UTC929 views14 reactionsread 8 August 2026
Video

Приятно, что на площадке «ИнПарка» рождаются классные идеи, которые воплощаются в реальные проекты! Роман Исайкин, управляющий партнер индустриального парка «НОВА», — о форуме.

🔥7👍4👏3

20 Nov 2025, 05:47 UTC759 views19 reactionsread 8 August 2026
Video

Благодарим Дмитрия Шохонова, корпоративного директора Ассоциации индустриальных парков России, модератора и спикера нашего форума, за отзыв!

👍9👏4🔥411

19 Nov 2025, 06:34 UTC400 views15 reactionsread 8 August 2026
Video

Своими впечатлениями от форума «ИнПарк» делится Рафаэль Хусяиншин, исполнительный директор Национальной Ассоциации агентств инвестиций и развития. Благодарим!

🔥7👏43👍1

18 Nov 2025, 05:38 UTC418 views6 reactionsread 8 August 2026

Коллеги, традиционно после форума мы формируем итоговую резолюцию Ключевые предложения будут направлены в Минпромторг России. Пишите свои предложения в комментариях или присылайте на [email protected]. В названии письма укажите «Предложения в резолюцию «ИнПарк», чтобы мы точно увидели. Благодарим!

👍3🤝3

17 Nov 2025, 05:05 UTC415 views18 reactionsread 8 August 2026
Photo

А мы уже пересматриваем снимки от нашего фотографа! 🔥 С удовольствием делимся и с вами: https://disk.360.yandex.ru/d/C7ZQ-aGQmqargg

🔥8🍓6🤩4

14 Nov 2025, 08:51 UTC596 views22 reactionsread 8 August 2026

Коллеги, по ссылке — презентации спикеров🤝 https://disk.360.yandex.ru/d/C7ZQ-aGQmqargg

🔥8👏6🤗4👨‍💻3👍1

14 Nov 2025, 03:13 UTC452 views24 reactionsread 8 August 2026
Photo

Участник ИнПарка Фарзин Бурхониддинович поделился своими снимками с форума! Благодарим! 📸Смотрим здесь

🔥10👍95

Showing the 10 most recent of 10 posts we hold for @forum_inpark. 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.

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.

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

“Форум ИнПарк” (@forum_inpark), 370 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/forum_inpark.

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.