Telegram RegisterThe public register of Telegram
Telegram profile photo for 🇫🇮 Finn IT | Работа в Финляндии

Channel

🇫🇮 Finn IT | Работа в Финляндии

@finland_it

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

738subscribers

+67 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-1003764448214
TypeChannel
Username@finland_it
CreatedBetween 1 February 2026 and 27 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/finland_it

Topic

Job listings — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

6707387047 August 2026 — 671 subscribers8 August 2026 — 671 subscribers15 August 2026 — 670 subscribers22 August 2026 — 689 subscribers29 August 2026 — 719 subscribers8 September 2026 — 733 subscribers16 September 2026 — 738 subscribers7 August 202616 September 2026
7 measurements spanning 40 days, net +67. 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 660–748 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 21:38738+5
8 Sept 2026, 20:35733+14
29 Aug 2026, 14:28719+30
22 Aug 2026, 19:53689+19
15 Aug 2026, 19:53670-1
8 Aug 2026, 02:33671no change
7 Aug 2026, 18:35671first reading

Engagement

20 posts held, back to 27 July 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

105 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 43.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4643.8%
👍2927.6%
🔥2221.0%
✍76.67%
👨‍💻10.952%

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 105 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 27 July 2026 to 7 August 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.

Recent posts

7 Aug 2026, 07:03 UTC143 views4 reactionsread 8 August 2026
Photo

Senior Frontend Engineer, Consumer Web Platform 🏢 Wolt 📍 Helsinki / Stockholm (hybrid) 💰 Зарплата: не указана 🕒 Full-time Senior Frontend Engineer в команду Consumer Web Platform, которая развивает платформу для wolt.com и других пользовательских веб-приложений Wolt. Обязанности: • Развивать frontend-платформу на TypeScript и React • Обеспечивать производительность, безопасность и надёжность приложений • Улучшать …

❤2✍1🔥1

6 Aug 2026, 19:00 UTC183 views5 reactionsread 8 August 2026
Photo

AI Solution Expert 🏢 Orion Pharma 📍 Espoo / Turku (hybrid) 💰 Зарплата: не указана 🕒 Full-time Специалист по разработке и внедрению AI-решений для бизнес-задач. Создания прототипов, запуск и поддержка решений в production. Обязанности: • Разрабатывать, внедрять и поддерживать AI-решения • Находить новые возможности для применения AI • Переводить прототипы в production-ready решения • Оценивать AI-инструменты и обла…

❤2👍2🔥1

6 Aug 2026, 17:50 UTC190 views4 reactionsread 8 August 2026
Photo

Mobile Operating System Security Engineer 🏢 Huawei Helsinki R&D Center 📍 Helsinki 💰 Зарплата: не указана 🕒 Full-time Инженер по безопасности мобильных операционных систем для разработки технологий защиты HarmonyOS. Основной фокус на безопасности ядра, санитайзерах, memory safety и аппаратных механизмах защиты. Обязанности: • Разрабатывать и поддерживать санитайзеры для подсистем ядра • Создавать аппаратные и комп…

👍2❤1🔥1

6 Aug 2026, 17:37 UTC192 views5 reactionsread 8 August 2026
Photo

Две свежие позиции фултайм разработчиков в разных департементах ICEYE: Tactical Access и Product Engineering. Senior Software Engineer (Tactical Access) Senior Software Engineer, Product Engineering #English #Senior #Fullstack #Espoo

❤2🔥2👨‍💻1

6 Aug 2026, 17:23 UTC198 views6 reactionsread 8 August 2026
Photo

Fullstack Engineer, Product Engineering 🏢 ICEYE 📍 Espoo (hybrid, 3 дня в офисе) 💰 Зарплата: не указана 🕒 Постоянный контракт Senior Fullstack Engineer для разработки продуктов на основе спутниковых данных ICEYE. Обязанности: • Разрабатывать функциональность на Python и TypeScript/React • Превращать требования в готовые к production решения • Поддерживать надёжность систем и участвовать в on-call • Улучшать монитор…

👍3🔥2✍1

3 Aug 2026, 19:05 UTC270 views7 reactionsread 8 August 2026
Photo

Brand Design Trainee 🏢 ICEYE 📍 Espoo (hybrid, 3 дня в офисе) 💰 Зарплата: оплачиваемая стажировка 🕒 Стажировка, 6 месяцев Стажировка в команде Brand & Design. Основной фокус - графический и бренд-дизайн для статичных и анимированных материалов в сфере космических технологий. Обязанности: • Создавать материалы для мероприятий, рекламы, презентаций и внутренних коммуникаций • Помогать с анимацией и видеоматериалами в…

❤4👍2🔥1

3 Aug 2026, 18:33 UTC256 views4 reactionsread 8 August 2026
Photo

Java Developer in Asset Finance Solutions II 🏢 Nordea 📍 Helsinki (hybrid, регулярное присутствие в офисе) 💰 Зарплата: не указана 🕒 Full-time Backend-разработчик в команду Asset Finance Solutions, которая создаёт цифровые решения для клиентов Nordea Finance в странах Северной Европы. Обязанности: • Разрабатывать REST API на Spring Boot • Создавать серверные и клиентские приложения • Проектировать решения вместе с р…

❤2👍1🔥1

3 Aug 2026, 18:12 UTC246 views4 reactionsread 8 August 2026
Photo

Data Engineer 🏢 Oura 📍 Helsinki / Oulu (hybrid) 💰 Зарплата: не указана 🕒 Full-time Data Engineer в команде Research Operations. Специалист будет развивать инфраструктуру данных для исследований и разработки алгоритмов. Обязанности: • Разрабатывать и поддерживать пайплайны, базы данных и дашборды • Собирать, очищать и предоставлять данные для разработки алгоритмов • Контролировать текущие исследования и устранять т…

❤2👍1🔥1

3 Aug 2026, 17:59 UTC233 views4 reactionsread 8 August 2026
Photo

Senior Backend Engineer, Cloud 🏢 Verda 📍 Helsinki (hybrid) 💰 Зарплата: не указана 🕒 Full-time Verda ищет Senior Backend Engineer для разработки ключевых сервисов своей AI Cloud-платформы. Вы будете создавать backend-системы для управления облачной инфраструктурой, API, аутентификацией, биллингом и аналитикой, работая вместе с командами Platform Engineering и SRE. Обязанности: • разрабатывать и развивать backend-се…

❤2👍1🔥1

1 Aug 2026, 08:33 UTC268 views6 reactionsread 8 August 2026
Photo

Senior Software Engineer (Networking) 🏢 ICEYE 📍 Espoo (hybrid) 💰 Зарплата: не указана 🕒 Full-time ICEYE ищет Senior Software Engineer (Networking) для развития сетевой платформы связи со спутниками. Вы будете разрабатывать системы, обеспечивающие надежную связь между спутниковой группировкой и наземной инфраструктурой. Обязанности: • разрабатывать и развивать TT&C Gateway для связи со спутниками • повышать надежно…

❤3👍2🔥1

1 Aug 2026, 07:34 UTC250 views6 reactionsread 8 August 2026
Photo

Senior Network Automation Engineer 🏢 Verda 📍 Helsinki (hybrid) 💰 Зарплата: не указана 🕒 Full-time Verda ищет Senior Network Automation Engineer для разработки платформы автоматизации сетевой инфраструктуры AI-дата-центров. Вы будете создавать инструменты, которые автоматизируют развертывание, управление и мониторинг сетей. Обязанности: • разрабатывать платформу автоматизации сетевой инфраструктуры • создавать моде…

❤3👍2🔥1

1 Aug 2026, 07:03 UTC247 views4 reactionsread 8 August 2026
Photo

Network Implementation Engineer 🏢 Verda 📍 Helsinki (hybrid) 💰 Зарплата: не указана 🕒 Full-time Verda ищет Network Implementation Engineer для развертывания сетевой инфраструктуры дата-центров под AI-нагрузки. Вы будете отвечать за ввод в эксплуатацию, проверку и передачу в production современных сетевых решений. Обязанности: • готовить планы развертывания сетевой инфраструктуры • выполнять ввод в эксплуатацию обор…

❤2✍1👍1

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

Named by 1 registered channel — 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.

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

“🇫🇮 Finn IT | Работа в Финляндии” (@finland_it), 738 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/finland_it.

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.