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 10 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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
28 measurements spanning 34 days, net +1,622. 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 27,814–29,922 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)
Subscribers
Change
9 Sept 2026, 17:38
29,679
+16
6 Sept 2026, 12:21
29,663
+111
4 Sept 2026, 01:39
29,552
+651
2 Sept 2026, 13:04
28,901
+20
1 Sept 2026, 11:02
28,881
+28
31 Aug 2026, 13:42
28,853
+27
30 Aug 2026, 12:53
28,826
+11
29 Aug 2026, 14:37
28,815
+12
28 Aug 2026, 17:18
28,803
+5
27 Aug 2026, 19:43
28,798
+12
26 Aug 2026, 19:24
28,786
+29
25 Aug 2026, 16:33
28,757
+38
24 Aug 2026, 17:05
28,719
+43
23 Aug 2026, 02:53
28,676
+41
21 Aug 2026, 15:17
28,635
+76
20 Aug 2026, 11:44
28,559
+23
19 Aug 2026, 14:16
28,536
+12
18 Aug 2026, 12:26
28,524
+33
17 Aug 2026, 12:34
28,491
+17
16 Aug 2026, 04:35
28,474
first reading
Engagement
36 posts held, back to 16 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 61 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
25.3%
avg views ÷ 29,679 subscribers
Avg views / post
7,500
20 posts measured
Reaction rate
0.702%
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
Window
Rolling 30 days · latest post in window 5 September 2026
Posts held
36 (16 July 2026 – 5 September 2026)
Views total
149,950
Reactions total
1,053
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Sept 2026, 01:34 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
Video runtime
8s
Average length
4s
Measured directly from 2 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
1,620 reactions across 34 posts, in 23 distinct kinds. The most used accounts for 16.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
270
16.7%
👍
249
15.4%
🔥
229
14.1%
😁
153
9.44%
⚡
126
7.78%
🤣
114
7.04%
custom 5244837190827014574
61
3.77%
custom 5321169488505250695
59
3.64%
custom 5244702084040793820
52
3.21%
✍
44
2.72%
❤🔥
42
2.59%
custom 5323533485749610968
35
2.16%
custom 5235495628368289754
31
1.91%
💯
31
1.91%
👨💻
26
1.60%
custom 5247071780706744881
18
1.11%
custom 5255811300419730777
18
1.11%
custom 5474369911096646059
17
1.05%
👏
15
0.926%
🤔
13
0.802%
3 further kinds
17
1.05%
Custom emoji. 8 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 35 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 1,657 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 16 July 2026 to 5 September 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
1
across the posts below
Posts paid on
1
of 36 we hold a reading for · 3%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ozon_tech. 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 16 July 2026 to 5 September 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.
Go опционален, AI желателен: ищем бэкэнд-разработчиков уровня Senior, чтобы строить новый продукт ⏺️
Сейчас формируем новую команду в направлении PaaS, будем создавать внутреннюю платформу для агентской разработки.
У нас уже есть собственный LLM-шлюз и базовая платформа. В ближайших планах SDK, Tool Hub, визуальная оркестрация, observability и инструменты оценки качества AI-решений.
А пока собираем команду разрабо…
От 12 часов к 30 минутам: как мы join’им миллиарды товарных движений в ClickHouse🔷
Привет, это Муса Мусаев, ведущий разработчик витрин данных. Каждый день мы обеспечиваем доставку ∼10 млрд записей в разных форматах. Это данные, связанные с товарными запасами и движениями.
❓Наша задача — 5 раз в день обогащать многомиллионные датасеты миллиардами атрибутов. И делать это быстро. Но как мы все знаем, ClickHouse читает…
Когда нам стало недоставать стандартных инструментов Go-тестирования для больших end-to-end-сценариев, мы написали свой фреймворк🔷
Привет! Это Вадим Збаращенко, разработчик QA-платформы и автор Open Source фреймворка для гибкого тестирования на Go — Testo.
Инструмент помогает автоматизировать и структурировать тесты, сохраняя их привычный вид. У нас на Testo уже успешно крутится 90 000+ уникальных тестов для 700 се…
💙💙💙💙💙
Маленькое напоминание о большой дате: где стоит провести День программиста⬆️
Арка — результат нашей коллаборации с художником Вовой Перкиным. Её можно увидеть в креативном пространстве Дизайн завода (ex-Флакон) до 4 сентября.
Кстати, 4 сентября мы закрываем регистрацию на ecode.ozon.tech. Успевайте!
До встречи💙
#ecode #ecode2026
Ускорили расчёт кандидатов для рекомендательной системы с 30 часов до нескольких минут
Наша рекомендательная система не просто находит подходящие товары среди сотен миллионов кандидатов. Она учитывает наличие, историю просмотров, разнообразие рекомендаций… Множество условий.
Раньше мы использовали двухэтапный подход: 1) ANN-поиск находил ближайших кандидатов; 2) отдельные Spark-задачи применяли к ним фильтры и бизн…
Осталось 4 дня, чтобы принять участие в ML-соревновании E-CUP.
Вы ещё успеваете выбрать трек и предложить лучшее решение:
🔵модель для идентификации дублей товаров,
🔵классификатор для проверки соответствия требованиям,
🔵предсказатель поведения пользователя на площадке.
Регистрируйтесь на e-cup-ozon.ru, и пусть вас настигнут гениальные идеи. Удачи! 🎓
#ecup #ecup_students
Проанализровали рутину релизного процесса, нашли моменты, в которых теряем время, и оптимизировали их. Еженедельное релизное тестирование ускорилось на 45%.
Привет, это Богдан Бурков, старший инженер по тестированию в мобильном приложении Ozon Seller.
У нас в направлении есть роль Release-owner (RO). Это QA-специалист, назначаемый каждую неделю из разных команд. Он отвечает за контроль проведения релизного тестиров…
У нас тут Коля Гущарин, тимлид разработки инструментов ВЭД для поставок Global, рассказал, как взялся за код после менеджерских задач. Читайте и пишите в комментариях, было?
🔥10⚡3👏1
Showing the 12 most recent of 36 posts we hold for @ozon_tech. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 14 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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
МТС Банк | Карьера @mtsbankcareer · 30,770 Telegram ranks this channel #2 of 99 here — alongside 98 others — read 7 September 2026
Код Желтый @kod_zheltyi · 32,901 Telegram ranks this channel #3 of 96 here — alongside 95 others — read 4 September 2026
Ozon HQ @ozonhq · 28,586 Telegram ranks this channel #4 of 88 here — alongside 87 others — read 9 September 2026
T-Crew @t_crew · 42,953 Telegram ranks this channel #4 of 95 here — alongside 94 others — read 29 August 2026
Avito Career @avito_career · 65,777 Telegram ranks this channel #4 of 98 here — alongside 97 others — read 21 August 2026
Школа 21 @school21sber · 69,254 Telegram ranks this channel #6 of 94 here — alongside 93 others — read 19 August 2026
Yandex for Developers @Yandex4Developers · 28,528 Telegram ranks this channel #7 of 94 here — alongside 93 others — read 9 September 2026
Alfa Digital @alfadigital_jobs · 54,270 Telegram ranks this channel #7 of 99 here — alongside 98 others — read 24 August 2026
Яндекс нанимает | Вакансии для разработчиков @ya_jobs · 32,693 Telegram ranks this channel #8 of 96 here — alongside 95 others — read 5 September 2026
Злой коллега @zloy_kollega · 44,870 Telegram ranks this channel #9 of 98 here — alongside 97 others — read 28 August 2026
Young&&Yandex @Young_and_Yandex · 110,734 Telegram ranks this channel #11 of 92 here — alongside 91 others — read 14 August 2026
Т-Образование @tbank_education · 112,760 Telegram ranks this channel #11 of 91 here — alongside 90 others — read 14 August 2026
Поступашки - ШАД, Стажировки и Магистратура @postypashki_old · 44,751 Telegram ranks this channel #14 of 90 here — alongside 89 others — read 28 August 2026
Selectel @Selectel · 63,417 Telegram ranks this channel #17 of 96 here — alongside 95 others — read 21 August 2026
Карьера в Сбере! @careersber · 137,124 Telegram ranks this channel #17 of 96 here — alongside 95 others — read 13 August 2026
Журнал «Код» @thecodemedia · 49,278 Telegram ranks this channel #18 of 97 here — alongside 96 others — read 25 August 2026
Ozon и партнёры ПВЗ @ozonapvz · 67,367 Telegram ranks this channel #19 of 72 here — alongside 71 others — read 20 August 2026
Яндекс Образование @Education_Yandex · 37,895 Telegram ranks this channel #23 of 96 here — alongside 95 others — read 31 August 2026
Карьера в ВТБ @vtb_career · 93,556 Telegram ranks this channel #26 of 93 here — alongside 92 others — read 23 August 2026
Хабр Карьера @habr_career · 33,076 Telegram ranks this channel #33 of 97 here — alongside 96 others — read 4 September 2026
IT - стажировки и обучение @it_interns · 31,282 Telegram ranks this channel #34 of 97 here — alongside 96 others — read 6 September 2026
Профсоюз работников IT @ruitunion · 35,780 Telegram ranks this channel #35 of 94 here — alongside 93 others — read 2 September 2026
2ГИС Команда @team2gis · 45,003 Telegram ranks this channel #43 of 90 here — alongside 89 others — read 27 August 2026
Альфа-Будущее @alfafuture · 48,669 Telegram ranks this channel #48 of 99 here — alongside 98 others — read 26 August 2026
This channel appears in 29 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 9 September 2026 — this
entry's latest reading, not the date you are reading this.
“Ozon Tech” (@ozon_tech), 29,679 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/ozon_tech.
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.