Telegram RegisterThe public register of Telegram
Telegram profile photo for Работа — вёрстка и фронтенд

Channel

Работа — вёрстка и фронтенд

@job_webdev

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

7,216subscribers

+3 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-1001850985741
TypeChannel
Username@job_webdev
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live21 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/job_webdev

Growth

7,2047,2167,2107 August 2026 — 7,213 subscribers8 August 2026 — 7,214 subscribers11 August 2026 — 7,210 subscribers14 August 2026 — 7,214 subscribers18 August 2026 — 7,204 subscribers21 August 2026 — 7,216 subscribers7 August 202621 August 2026
6 measurements spanning 14 days, net +3. 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,202–7,218 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 09:467,216+12
18 Aug 2026, 00:567,204-10
14 Aug 2026, 14:367,214+4
11 Aug 2026, 12:227,210-4
8 Aug 2026, 04:287,214+1
7 Aug 2026, 09:337,213first reading

Engagement

40 posts held, back to 23 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
12.5%
avg views ÷ 7,216 subscribers
Avg views / post
904
39 posts measured
Reaction rate
0.152%
reactions ÷ views · ER floor
Posts in window
39
of 40 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. It is computed over the 23 of 39 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 20 August 2026
Posts held40 (23 July 202620 August 2026)
Views total35,274
Reactions total31
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 14:52 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.

Reaction mix

34 reactions across 21 posts, in 5 distinct kinds. The most used accounts for 47.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎1647.1%
926.5%
🌭514.7%
👏38.82%
🔥12.94%

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

Measured over the 40 most recent posts we hold, published 23 July 2026 to 20 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

20 Aug 2026, 07:05 UTC436 views0 reactionsread 20 August 2026
Photo

frontend разработчик ai-продуктов Компания: Сбер Регион: Москва Опыт работы: #senior Формат работы: #гибрид задачи • Создавать пользовательские интерфейсы AI-продуктов; • Отвечать за клиентскую логику, взаимодействие с AI-API и удобство работы с LLM-чатами и агентами. требования • Опыт работы с TS от 6 лет; • Опыт работы с одним или несколькими современными фреймворками: React, Vue.js или аналоги; • Знание алгорит

19 Aug 2026, 17:03 UTC520 views2 reactionsread 20 August 2026
Photo

Верстка сайта Что нужно сделать? Необходимо сверстать готовый дизайн двух страниц (десктоп и мобильная версия) с картинок сгенерированных нейросетью и внести небольшие правки. Итоговый вариант подготовить для передачи программисту Цена: до 7500 руб. Перейти к заявке 👨‍💻 #верстка #фриланс

👎2

19 Aug 2026, 07:03 UTC566 viewsread 20 August 2026
Photo

Постановка сайта Что нужно сделать? Сайт уже стоит на сервере,сайт был приобритен ,есть полная инструкция по его настройке ,нужно в редиме реального времени помочь настроить/объяснить. Ссылку на инструкцию предоставлю Цена: до 9000 руб. Перейти к заявке 👨‍💻 #верстка #фриланс

18 Aug 2026, 07:05 UTC675 views0 reactionsread 20 August 2026
Photo

Frontend-разработчик Компания: mtsbank.ru Регион: Москва Ты будешь: Разрабатывать и поддерживать веб-приложения на React.js и Next.js Применять стейт-менеджеры Redux и Saga/Thunk для управления состоянием приложения Писать юнит-тесты с использованием Jest Работать с библиотекой styled-components для стилизации компонентов Взаимодействовать с командой и другими отделами для решения технических задач и улучшения прод

17 Aug 2026, 07:05 UTC761 viewsread 20 August 2026
Photo

vue.js разработчик Компания: MISE Опыт работы: #junior Формат работы: #удаленка Зарплата: 80000-110000 задачи • Разрабатывать и поддерживать UI на Vue.js; • Писать чистый, масштабируемый TypeScript-код; • Интегрироваться с REST API и работать с данными в реальном времени; • Выносить логику в composables и следить за структурой проекта; • Участвовать в код-ревью и улучшать архитектуру фронтенда; • Плотно работать с

16 Aug 2026, 07:05 UTC739 viewsread 20 August 2026
Photo

Подборка лучших постов за прошлую неделю Лучшие статьи @free_html_lessons: 1. 3D анимация волны 2. Создание голосовых интерфейсов с помощью Web Speech API 3. JS Задача: Объедините два массива по ID Лучшие фронтенд вакансии @job_webdev: 1. frontend разработчик медиаконтента 2. Vue разработчик 3. HTML-верстальщик Лучшие дизайн вакансии @job_webdesign: 1. ux/ui дизайнер банковских продуктов 2. Web-дизайнер 3. ux/ui д

15 Aug 2026, 15:17 UTC746 viewsread 20 August 2026
Photo

Frontend сайта Что нужно сделать? Необходимо реализовать frontend по готовым макетам Figma. Стек: React + Next.js + TypeScript. Что нужно: Сверстать все экраны по Figma. Адаптив под desktop/mobile. Максимально точно повторить дизайн. Компонентная архитектура. Код должен быть чистым и понятным. Без хардкода там, где можно использовать переиспользуемые компоненты. Подготовить проект для дальнейшего подключения API. Fi

15 Aug 2026, 10:04 UTC714 views1 reactionsread 20 August 2026
Forwarded from @proitfestPhoto

🔥Мы начинаем серию Hiring Dating! 🫩Не можете никак пробиться на собеседования и получить свой долгожданный оффер? Пора обратиться к силе комьюнити! В данном событии могут участвовать Middle и Senior уровень любой экспертизы. Hiring Dating будет повторятся каждый месяц в Питере и в Москве. 🧩Для каждого участника мы собираем пул проверенных карьерных консультантов, менторов/тех интервьюеров и пул компаний, которым и

🔥1

15 Aug 2026, 07:33 UTC803 views3 reactionsread 20 August 2026
Photo

HTML-верстальщик Компания: СИНЕРГИЯ Регион: Москва Опыт работы: 1–3 года Формат работы: #удаленка В ПРОЦЕССЕ РАБОТЫ НЕОБХОДИМО Взаимодействовать с командой разработки и смежными отделами; участвовать в оценке и декомпозиции задач Создавать визуальные компоненты: таблицы, фильтры, формы; модальные окна, уведомления, панели с метриками и графиками Верстать одностраничные лендинги и небольшие сайты Обеспечивать высоко

👎3

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

Citation-graph rank

Citation-graph rank — 206,562 of 1,581,209entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“Работа — вёрстка и фронтенд” (@job_webdev), 7,216 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/job_webdev.

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.