Telegram RegisterThe public register of Telegram
Telegram profile photo for IT вакансии Узбекистан

Channel

IT вакансии Узбекистан

@workituzb

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

438subscribers

+144 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-1001961251611
TypeChannel
Username@workituzb
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/workituzb

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 22 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@workituzb/171 · this entry26 Jan 2026, 04:29 UTC@workITkg/17326 Jan 2026, 04:29 UTC1.00under a minute
@workituzb/173 · this entry28 Jan 2026, 04:29 UTC@workITkg/17528 Jan 2026, 04:29 UTC1.00under a minute
@workituzb/176 · this entry6 Mar 2026, 05:29 UTC@workITkg/1786 Mar 2026, 05:29 UTC1.00under a minute
@workituzb/178 · this entry30 Mar 2026, 05:29 UTC@workITkg/18030 Mar 2026, 05:29 UTC1.00under a minute
@workituzb/179 · this entry3 Apr 2026, 08:39 UTC@workITkg/1813 Apr 2026, 08:39 UTC1.00under a minute
@workITkg/1828 Apr 2026, 10:38 UTC@workituzb/180 · this entry8 Apr 2026, 10:38 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@workITkg17 (8/8 hand-verifiable sample passed)1.00under a minute@workITkg (16–1)
@workITru11 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (6–5)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 20 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 31 December 2025 to 31 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @workITkg. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

2944383667 August 2026 — 294 subscribers8 August 2026 — 296 subscribers8 August 2026 — 296 subscribers15 August 2026 — 372 subscribers23 August 2026 — 377 subscribers1 September 2026 — 380 subscribers10 September 2026 — 393 subscribers18 September 2026 — 399 subscribers2 October 2026 — 406 subscribers12 October 2026 — 412 subscribers20 October 2026 — 422 subscribers28 October 2026 — 427 subscribers5 November 2026 — 436 subscribers12 November 2026 — 438 subscribers7 August 202612 November 2026
14 measurements spanning 97 days, net +144. 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 272–460 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 10:01438+2
5 Nov 2026, 06:29436+9
28 Oct 2026, 11:06427+5
20 Oct 2026, 23:20422+10
12 Oct 2026, 20:59412+6
2 Oct 2026, 21:00406+7
18 Sept 2026, 02:37399+6
10 Sept 2026, 20:17393+13
1 Sept 2026, 00:05380+3
23 Aug 2026, 22:56377+5
15 Aug 2026, 16:45372+76
8 Aug 2026, 08:05296no change
8 Aug 2026, 06:58296+2
7 Aug 2026, 12:56294first reading

Engagement

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

Recent posts

31 Jul 2026, 10:54 UTC138 viewsread 8 August 2026

#вакансия #узбекистан #удаленка #workITkz #контент Должность: Удалённый помощник в YouTube-проект Компания: Международный YouTube-проект https://t.me/adolfwork01 Город: Узбекистан Занятость: удаленка Оплата: После обучения 25 000–35 000 ₽ в месяц при полной загрузке (примерно до 5,5 млн сум); обучение 1–2 недели — 100 ₽/час. Международный YouTube-проект по созданию и публикации коротких видео. Описание вакансии: Tel…

13 Jul 2026, 07:42 UTC240 viewsread 8 August 2026

#вакансия #астана #оффлайн #workITkz #архитектор, #java, #backend Должность: Tech Lead Компания: MDiet https://mdiet.org/ Город: Астана Занятость: оффлайн Оплата: $3000-$4000 MDiet — healthtech-стартап для рынка США. Наша AI-платформа помогает снижать повторную госпитализацию пациентов. Описание вакансии: -Языки и фреймворки: Java 21 / Spring Boot/Golang (основной бэкенд), Python / FastAPI (AI/ML-сервисы) -Архитекту…

8 Jul 2026, 10:22 UTC245 viewsread 8 August 2026

#вакансия #шымкент #гибрид #workITkz #javascript, #python Должность: Разработчик плагинов для Autodesk Revit (C# / Revit API) — опыт с ИИ Компания: Baitun Baitun.kz Город: Шымкент Занятость: гибрид Оплата: 500000 Проектная компания Описание вакансии: Мы разрабатываем набор кастомных плагинов для Autodesk Revit с целью автоматизации процессов проектирования и BIM-workflows. Ищем опытного разработчика Revit API, котор…

17 Jun 2026, 09:25 UTC295 viewsread 8 August 2026

#вакансия #астана #удаленка #workITkz #fullstack, #frontend, #backend Должность: ZIZ INC Компания: ZIZ INC ziz.kz Город: Астана Занятость: удаленка Оплата: от 222 000 - 555 000 тенге Разрабатываем цифровые продукты и имиджевые сайты, которые усиливают бренд, повышают доверие к компании и работают на задачи бизнеса. Описание вакансии: • Next.js, React, TypeScript • Python или Node.js • Умение читать и дорабатывать су…

26 May 2026, 10:02 UTC341 viewsread 8 August 2026

#вакансия #алматы #оффлайн #workITkz #архитектор, #dsml, #python Должность: Al Architect/Архитектор ИИ-ассистентов Компания: Кадровый Холдинг Elite https://elite.kz/ Город: Алматы Занятость: оффлайн Оплата: 3 500 000 Elite — кадровый холдинг в Казахстане, специализирующийся на подборе персонала, executive search, аутсорсинге и HR-консалтинге. Компания работает с локальными и международными работодателями в различных…

13 May 2026, 04:31 UTC354 viewsread 8 August 2026

"#вакансия #шымкент #гибрид #workITkz #python Должность: Программист для Revit плагинов с использованием AI Компания: Baitun baitun.kz Город: Шымкент Занятость: гибрид Оплата: От 800$ и выше Архитектурно-проектная организация Описание вакансии: Python; C#(.net); Revit API; WPF/WinForms; Visual Studio; RestAPI/HTTP; FastAPI; SQLite; LangChain; RAG Требуется программист для написаний плагинов для ПО Revit, с использов…

21 Apr 2026, 07:06 UTC322 viewsread 8 August 2026

#вакансия #астана #оффлайн #workITkz #helpdesk, #аналитик Должность: Customer Solutions Engineer (Junior) Компания: ТОО Documentolog documentolog.com Город: Астана Занятость: оффлайн Оплата: 250 000 - 400 000 тг на руки Описание вакансии: - Внедрение системы Documentolog у Заказчиков (настройка бизнес-процессов); - Выявление и устранение конфигурационных ошибок в системе Documentolog; - Создание бизнес-процессов и …

8 Apr 2026, 10:38 UTC259 viewsread 8 August 2026

"#вакансия #бишкек, кыргызстан #оффлайн #workITkz #infosec, #архитектор, #teamlead Должность: Head of SOC (Руководитель Центра мониторинга кибербезопасности) Компания: O!Bank https://obank.kg/ru/career Город: Бишкек, Кыргызстан Занятость: оффлайн Оплата: от 450000 сом (2 370 000 тенге) О!Bank — это современный банк, который строит экосистему для удобной и безопасной жизни граждан. Мы развиваем инновационные сервисы,…

3 Apr 2026, 08:39 UTC210 viewsread 8 August 2026

"#вакансия #казахстан #удаленка #workITkz #php, #backend Должность: BackEnd PHP developers (Laravel) Компания: ТОО Office Expert.kz https://oe.kz/ Город: Казахстан Занятость: удаленка Оплата: от 1,5 млн тг “Office-Expert.kz” — первый в Казахстане интернет-магазин, обеспечивающий офисы всем необходимым для полноценной работы. Мы — лидеры в сегменте B2B e-commerce, предоставляющие широкий спектр товаров и услуг через …

30 Mar 2026, 05:29 UTC215 viewsread 8 August 2026

#вакансия #сша #удаленка #workITkz #javascript, #fullstack Должность: Junior JavaScript (Salesforce) Developer Компания: CloudBudget, LLC cloudbudget.com Город: США Занятость: удаленка Оплата: 500 000 - 700 000 тг SaaS-компания, разрабатывающая инструменты для бюджетирования и финансового планирования на платформе Salesforce Описание вакансии: JavaScript, Apex, LWC, Salesforce Уверенное знание JavaScript. Хороший ан…

10 Mar 2026, 05:29 UTC272 viewsread 8 August 2026

#вакансия #казахстан #удаленка #workITkz #computervision, #python, #backend Должность: ML Engineer (Видеонаблюдение + AI) Компания: Smart Head Kazakhstan https:\\hosti.kz Город: Казахстан Занятость: удаленка Оплата: 500-1000$ Мы команда Smart Head из Казахстана специализируемся на создании современных веб-решений, поэтому у тебя будет возможность работать над интересными и инновационными проектами Описание вакансии:…

6 Mar 2026, 05:29 UTC252 viewsread 8 August 2026

#вакансия #ташкент #удаленка #workITkz #аналитик Должность: Client Analyst (Клиентский Аналитик) Компания: METER https://meter.geomotive.io/ru Город: Ташкент Занятость: удаленка Оплата: $500 - $900 IT-компания, которая измеряет аудиторию наружной рекламы и строит аналитику на основе геоданных в Центральной Азии и странах Ближнего Востока. Описание вакансии: - Готовить регулярные отчёты и презентации для клиентов. -…

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

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

Named by

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

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

“IT вакансии Узбекистан” (@workituzb), 438 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/workituzb.

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.