Telegram RegisterThe public register of Telegram
Telegram profile photo for Kolesa Group

Channel

Kolesa Group

@kolesa_group

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

7,211subscribers

+110 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001797092219
TypeChannel
Username@kolesa_group
DescriptionКазахстанская IT-компания, на рынке с 1996 года. Строим IT-продукты №1 в Казахстане и Узбекистане. Делимся своим опытом и полезностями во всех IT-направлениях, анонсируем наши стажировки и мероприятия. Подробнее о нас тут: https://kolesa.group/
CreatedBetween 1 February 2022 and 31 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/kolesa_group

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 the other topics.

Growth

7,0817,2277,1547 August 2026 — 7,101 subscribers8 August 2026 — 7,104 subscribers11 August 2026 — 7,098 subscribers15 August 2026 — 7,094 subscribers17 August 2026 — 7,090 subscribers20 August 2026 — 7,088 subscribers24 August 2026 — 7,081 subscribers27 August 2026 — 7,115 subscribers30 August 2026 — 7,117 subscribers2 September 2026 — 7,127 subscribers6 September 2026 — 7,154 subscribers11 September 2026 — 7,157 subscribers15 September 2026 — 7,179 subscribers19 September 2026 — 7,194 subscribers28 September 2026 — 7,200 subscribers6 October 2026 — 7,183 subscribers12 October 2026 — 7,181 subscribers15 October 2026 — 7,194 subscribers18 October 2026 — 7,221 subscribers21 October 2026 — 7,227 subscribers25 October 2026 — 7,220 subscribers28 October 2026 — 7,212 subscribers31 October 2026 — 7,203 subscribers3 November 2026 — 7,204 subscribers6 November 2026 — 7,208 subscribers9 November 2026 — 7,200 subscribers13 November 2026 — 7,211 subscribers7,2117 August 202613 November 2026
27 measurements spanning 99 days, net +110. 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 7,059–7,249 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
13 Nov 2026, 21:097,211+11
9 Nov 2026, 13:557,200-8
6 Nov 2026, 08:597,208+4
3 Nov 2026, 02:077,204+1
31 Oct 2026, 03:057,203-9
28 Oct 2026, 06:477,212-8
25 Oct 2026, 00:467,220-7
21 Oct 2026, 21:157,227+6
18 Oct 2026, 10:277,221+27
15 Oct 2026, 18:077,194+13
12 Oct 2026, 16:407,181-2
6 Oct 2026, 04:387,183-17
28 Sept 2026, 16:377,200+6
19 Sept 2026, 06:597,194+15
15 Sept 2026, 02:187,179+22
11 Sept 2026, 12:387,157+3
6 Sept 2026, 22:367,154+27
2 Sept 2026, 08:347,127+10
30 Aug 2026, 13:447,117+2
27 Aug 2026, 21:167,115first reading

Engagement

36 posts held, back to 24 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 37 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.0%
avg views ÷ 7,211 subscribers
Avg views / post
1,660
20 posts measured
Reaction rate
1.25%
reactions ÷ views · ER floor
Posts in window
20
of 36 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held36 (24 July 2026 – 16 November 2026)
Views total33,202
Reactions total414
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 16:20 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈1,670
Videos
≈257
Links
≈619

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
9m 48s
Average length
49s

Measured directly from 12 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

927 reactions across 36 posts, in 26 distinct kinds. The most used accounts for 40.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤37840.8%
🔥22624.4%
😍677.23%
😁515.50%
❤‍🔥323.45%
⚡212.27%
💘212.27%
🤣192.05%
😭181.94%
🤩181.94%
💯161.73%
🆒141.51%
👍111.19%
🥰70.755%
👻50.539%
😢50.539%
👨‍💻30.324%
😎30.324%
✍20.216%
🍌20.216%
6 further kinds80.863%

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

Measured over the 36 most recent posts we hold, published 24 July 2026 to 16 November 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.

Telegram Stars

Stars received
21
across the posts below
Posts paid on
9
of 36 we hold a reading for · 25%
Most on one post
6
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kolesa_group. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 36 most recent posts we hold for this entry, published 24 July 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 20 posts held from the last 30 days (15.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 10:45 UTC695 views5 reactionsread 16 November 2026

🔍 А ты уже поделился своим опытом работы? Напоминаем, что Kolesa Group проводит ежегодное исследование рынка project- и product-менеджеров в Казахстане. Пройти опрос могут: Product Manager, Product Owner, Head of Product, Project Manager, Business Analyst, Scrum Master и Business Development Manager. Опрос анонимный и займёт не больше 5 минут. Среди участников, которые полностью заполнят анкету, разыграем пару нау…

❤2🫡2🔥1

16 Nov 2026, 07:35 UTC947 views9 reactions4 Starsread 16 November 2026
Photo

⚡️ Полезные материалы для product- и project-менеджеров Собрали подборку курсов, книг, статей и Telegram-каналов, которые помогут прокачать профессиональные навыки, разобраться в новых инструментах и найти идеи для работы. 📌 Для product-менеджеров Курсы и обучение • Профессия: Продакт-менеджер — GoPractice — базовый курс по продуктовой работе. • Advanced JTBD — Иван Замесин — тренинг по Jobs To Be Done. • Техническ…

❤7✍1🆒1

13 Nov 2026, 07:16 UTC≈1,940 views14 reactionsread 16 November 2026
Photo

📊 У всех ли аналитиков одинаковые условия работы? Зарплаты, задачи, инструменты и возможности для карьерного роста могут отличаться в зависимости от компании и направления. Мы проводим ежегодное исследование рынка аналитиков в Казахстане. Хотим узнать, сколько зарабатывают специалисты и какие условия работы предлагают компании. ❗️Пройти опрос могут: системные аналитики, бизнес-аналитики, продуктовые аналитики, дат…

🔥10❤4

13 Nov 2026, 04:00 UTC≈1,470 views4 reactionsread 16 November 2026
Photo

💙 Вакансии в Kolesa Group Откликайся и стань частью Kolesa Team! Разработка: Fullstack Web QA в Krisha.kz Middle PHP Backend-разработчик Krisha.kz Администрирование: Администратор сетей и инфраструктуры Data science: Machine Learning Engineer Продажи: Менеджер по продажам (Ташкент) Менеджер по продажам B2B (Астана) Менеджемент: Senior Product manager в Kolesa.kz (Core) Product manager в Krisha.kz Product manager…

❤4

12 Nov 2026, 12:52 UTC≈1,530 views7 reactions2 Starsread 16 November 2026
Photo

Проведи вечер за просмотром докладов с Kolesa AI Meetup 🫂 🔗 Ссылка на доклады

❤7

12 Nov 2026, 05:35 UTC≈1,560 views49 reactions1 Starread 16 November 2026
Video

😮‍💨 Целая очередь к тимлиду Оставляй реакцию, если знакомо 👇

😁25💯12❤‍🔥7😎3😭2

11 Nov 2026, 12:42 UTC≈1,470 views7 reactionsread 16 November 2026
Forwarded from @sergeknewsPhoto

🤖 ИИ меняет правила, но решают люди: итоги митапов ко Дню цифровизации в Алматы и Астане В День цифровизации казахстанское IT-сообщество синхронно встретилось на двух площадках — Kolesa AI Meetup в Алматы и TalkIT в Astana Hub. Говорили о двух сторонах индустрии: как нейросети перекраивают разработку и как реальные специалисты пробивают путь к руководящим позициям. Алматы: как ИИ меняет разработку • Код подешевел, …

❤7

9 Nov 2026, 12:29 UTC≈1,490 views17 reactionsread 16 November 2026
Video

⚡ Как прошёл Kolesa Marketing Communications Meetup Провели митап для специалистов по маркетингу и коммуникациям с докладами от экспертов Kolesa Group и панельной дискуссией с участием CMO Hero’s Journey, KazChess и Ryadom.kz. Говорили о том, как маркетинг помогает растить лояльность пользователей, решать бизнес-задачи и достигать стратегических целей. Спасибо всем, кто пришёл, задавал вопросы, делился опытом и сде…

🔥8❤‍🔥4🆒3❤2

5 Nov 2026, 13:33 UTC≈1,910 views55 reactions1 Starread 16 November 2026
Photo

🏆 Kolesa Group получили награду Great Place to Work по версии Kazakhstan HR Forum 2026 Победителей оценивали по четырём критериям: устойчивость бизнеса, опыт сотрудников, инновационность и репутация на рынке. В Kolesa Group создаём условия для профессионального роста: — 90% мидл-менеджеров выросли внутри компании благодаря менторству и возможностям для развития — Проводим Kolesa Talks, развиваем Kolesa Upgrade, орг…

❤32🔥16❤‍🔥7

5 Nov 2026, 06:22 UTC≈1,740 views10 reactionsread 16 November 2026
Photo

⚡ Kolesa Marketing Communications Meetup Встречаемся сегодня на митапе! Для тех, кто зарегистрировался офлайн — начало в 18:00, онлайн-трансляция стартует в 18:30. 🔗 Ссылка на трансляцию

❤10

5 Nov 2026, 06:05 UTC≈1,730 views18 reactionsread 16 November 2026
Photo

🔍 Kolesa Group запускает ежегодное исследование рынка project- и product-менеджеров в Казахстане Хотим узнать, сколько зарабатывают специалисты, какие условия работы предлагают компании и какие возможности для карьерного роста есть на рынке. ❗️Пройти опрос могут: Product Manager, Product Owner, Head of Product, Project Manager, Business Analyst, Scrum Master и Business Development Manager. Опрос займёт не больше 5…

❤8🤩6💘4

4 Nov 2026, 12:07 UTC≈1,720 views32 reactionsread 16 November 2026
Photo

✨ Могни всех и стань частью Kolesa Team Оставляй резюме на подходящую вакансию. Если знаешь классного специалиста, порекомендуй его нам через реферальную программу и получи вознаграждение за успешный найм. Рекомендовать может каждый, даже если ты не работаешь в Kolesa Group. Разработка: Fullstack Web QA в Krisha.kz Middle PHP Backend-разработчик Krisha.kz Администрирование: DevOps-инженер Администратор сетей и ин…

😁22❤4👍2🤣2🍌1😭1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

Dev KZ | Vacancy
@devkz_jobs · 25,817
Telegram ranks this channel #7 of 86 here — alongside 85 others — read 15 September 2026
The Tech
@thetechkz · 27,364
Telegram ranks this channel #13 of 95 here — alongside 94 others — read 11 September 2026
bluescreen.kz
@bluescreenkz · 24,584
Telegram ranks this channel #14 of 95 here — alongside 94 others — read 17 September 2026
JobKZ: вакансии / работа в Казахстане
@jobkz_1 · 38,556
Telegram ranks this channel #29 of 88 here — alongside 87 others — read 1 September 2026
Kaspi.kz
@kaspikz · 26,669
Telegram ranks this channel #31 of 89 here — alongside 88 others — read 11 September 2026
IT Вакансии Казахстан
@workitkz · 37,089
Telegram ranks this channel #32 of 85 here — alongside 84 others — read 2 September 2026
Давай Сходим! Алматы
@sxodim · 24,994
Telegram ranks this channel #43 of 90 here — alongside 89 others — read 14 September 2026
Авиабилеты из Казахстана
@aviatickets_kz · 37,065
Telegram ranks this channel #44 of 72 here — alongside 71 others — read 1 September 2026
Турагентство GOTOUR.KZ
@gotour_kz · 19,545
Telegram ranks this channel #48 of 56 here — alongside 55 others — read 29 September 2026
Горящие туры FUN&SUN
@fstravel_kz · 28,960
Telegram ranks this channel #56 of 65 here — alongside 64 others — read 29 September 2026

This channel appears in 10 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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“Kolesa Group” (@kolesa_group), 7,211 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/kolesa_group.

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.