Technology — 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 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
13 measurements spanning 43 days. 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 1,016–1,023 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
19 Sept 2026, 10:01
1,022
+1
15 Sept 2026, 01:58
1,021
-1
6 Sept 2026, 06:20
1,022
+1
2 Sept 2026, 04:36
1,021
-1
30 Aug 2026, 08:29
1,022
+2
27 Aug 2026, 01:47
1,020
+3
23 Aug 2026, 22:38
1,017
-2
19 Aug 2026, 21:52
1,019
+1
16 Aug 2026, 19:29
1,018
-1
13 Aug 2026, 03:07
1,019
-2
10 Aug 2026, 07:30
1,021
-1
7 Aug 2026, 09:32
1,022
no change
7 Aug 2026, 09:21
1,022
first reading
Engagement
18 posts held, back to 14 April 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 18 posts for this entry, the most recent from 30 May 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
127 reactions across 16 posts, in 8 distinct kinds. The most used accounts for 47.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
60
47.2%
👍
26
20.5%
🎉
15
11.8%
❤
10
7.87%
🏆
6
4.72%
😁
6
4.72%
❤🔥
2
1.57%
😍
2
1.57%
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 16 of the 18 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 127 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 14 April 2026 to 30 May 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.
🗻 AlmatyJS Popup #2 завершён
Спасибо всем, кто пришёл сегодня: за энергию, вопросы, кейсы и живое обсуждение.
И спасибо нашим друзьям из hy.gge за отличную площадку и кофе.
До встречи на следующих митапах!
Напоминаем, что подать тему на следующий митап вы можете через форму CFP, которая доступна постоянно — https://almatyjs.kz/cfp
@almaty_js
Чтобы оправдать название AlmatyJS и не становиться AlmatyAI на сцене AlmatyJS Popup следующий спикер Магжан Биргебайулы, который расскажет свой взгляд со стороны на web-разработку
@almaty_js
🗻 AlmatyJS Popup #2 скоро начнется
Как нас найти - инструкция в трех картинках
2gis — https://go.2gis.com/DMSOy
Собираемся в 10:30, начало - в 11:00
@almaty_js
🗻 AlmatyJS Popup #2 уже завтра
Завтра встречаемся в Hy.gge Specialty Bar, чтобы спокойно выпить кофе, познакомиться и обсудить две темы для разгона:
1. Экономим на AI с использованием локальных моделей — Саид Авхадеев
2. Взгляд со стороны на web-разработку — Магжан Биргебайулы
Сбор: 10:30 — нетворкинг и кофе
Старт: 11:00
Где: Hy.gge | Specialty Wellness Bar [2gis, instagram]
Если вы зарегистрировались — приходите…
🗻 AlmatyJS Popup #2 — AI, локальные модели и взгляд со стороны на web-разработку
Продолжаем формат небольших уютных встреч с практикой, вопросами и живым обсуждением.
В этот раз собираемся у наших друзей в Hy.gge Specialty Bar (Зенкова 17), пьём кофе, знакомимся и обсуждаем две темы для разгона:
Экономим на AI с использованием локальных моделей — Саид Авхадеев
Поговорим о том, когда локальные модели действительно …
🗻 Собираем темы на AlmatyJS Popup #2
Напомним, что AlmatyJS Popup — это новый формат в виде небольших уютных встреч с практикой, вопросами и разбором реальных подходов:
• минимум подготовки и “правил”
• без фактических ограничений по темам, формату и длительности
• раз в месяц встречаемся на разных площадках
• обсуждаем, спорим, разгоняем идеи и делимся опытом
Вторая встреча уже будет очень скоро.
Если давно х…
🎥 Видео с AlmatyJS Light #8 уже готовы
Записи докладов с последнего митапа уже на нашем YouTube. Можно пересмотреть, если пропустил, или освежить мысли после встречи.
Если хочется разобрать темы глубже или поделиться с коллегами — самое время.
⚡️ И напомним про CFP
У нас есть постоянная страница для докладов: https://almatyjs.kz/cfp
Хочешь выступить — оставляй тему, мы вернёмся к ней при сборе следующих митапов.
…
🗻 Спасибо всем за участие в нашем митапе
Спасибо спикерам за доклады и гостям за их каверзные вопросы и активное участие в панельной сессии. Обсуждение выдалось очень горячим и интересным.
Друзья, чтобы мы могли улучшаться, нам необходим ваш фидбек. Просим вас ответить в форме обратной связи.
Будем рады увидеться снова!
@almaty_js
🗻 Никита Баев начинает рассказ о скиллах
Наш первый спикер открывает AlmatyJS(AlmatyAI) x Bereke Bank #8
@almaty_js
🔥9👍4❤🔥2🏆1😁1
Showing the 12 most recent of 18 posts we hold for @almaty_js. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 18 most recent posts we hold, published 14 April 2026 to 30 May 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Dev KZ | Vacancy @devkz_jobs · 25,053 Telegram ranks this channel #33 of 86 here — alongside 85 others — read 15 September 2026
Kaspi.kz @kaspikz · 27,107 Telegram ranks this channel #58 of 89 here — alongside 88 others — read 11 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 19 September 2026 — this
entry's latest reading, not the date you are reading this.
“AlmatyJS” (@almaty_js), 1,022 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/almaty_js.
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.