Telegram RegisterThe public register of Telegram
Telegram profile photo for Frontend (JS,CSS,HTML) вакансии и работа

Channel

Frontend (JS,CSS,HTML) вакансии и работа

@YotolabFrontend

Not marked by Telegram, checked 19 August 2026

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

2,140subscribers

-4 since we began measuring on 18 August 2026

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

Register entry

Telegram ID-1002244696568
TypeChannel
Username@YotolabFrontend
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 August 2026
Last confirmed live25 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/YotolabFrontend

Growth

2,1402,1442,14218 August 2026 — 2,144 subscribers19 August 2026 — 2,141 subscribers23 August 2026 — 2,144 subscribers25 August 2026 — 2,140 subscribers18 August 202625 August 2026
4 measurements spanning 7 days, net -4. 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 2,139–2,145 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 18:582,140-4
23 Aug 2026, 00:132,144+3
19 Aug 2026, 18:322,141-3
18 Aug 2026, 19:312,144first reading

Engagement

20 posts held, back to 21 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
30.5%
avg views ÷ 2,140 subscribers
Avg views / post
653
4 posts measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
4
of 20 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 14 August 2026
Posts held20 (21 April 202614 August 2026)
Views total2,610
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 19:31 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

90 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 73.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎6673.3%
1213.3%
👍88.89%
🔥44.44%

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

Measured over the 20 most recent posts we hold, published 21 April 2026 to 14 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

14 Aug 2026, 17:06 UTC400 views14 reactionsread 18 August 2026

Стажер Frontend Developer (React/Next) в компанию MISE MISE - динамично развивающаяся компания в сегменте HoReCa. Создаёт современные цифровые решения для ресторанов и лаунджей. 📝 Обязанности • Использование хуков и компонентного подхода • Верстка с применением CSS/SCSS • Разработка и поддержка UI на React • Участие в командных обсуждениях и планировании задач • Исправление багов и оптимизация кода • Изучение новых

👎10🔥4

3 Aug 2026, 16:06 UTC697 views3 reactionsread 18 August 2026

Ведущий iOS-разработчик (Messaging / Matrix) в команду разработки мессенджера на базе Matrix Команда развивает мессенджер на базе протокола Matrix (элемент Element, первая итерация продукта с личными/групповыми переписками и каналами). 📝 Обязанности - Разработка и доработка UI мессенджера на SwiftUI и UIKit; - Работа с Matrix-событиями (sync/timeline/room_tags); - Обеспечение E2EE (Megolm, key backup, восстановлени

👎3

3 Aug 2026, 08:06 UTC687 views12 reactionsread 18 August 2026

Frontend-разработчик (React / TypeScript) в технологическую компанию 📝 Обязанности - Разрабатывать новые возможности продукта на React и TypeScript. - Участвовать в проектировании архитектуры вместе с командой разработки. - Обсуждать решения с дизайнерами и backend-разработчиками ещё до начала реализации. - Улучшать производительность, качество интерфейсов и пользовательский опыт. - Участвовать в code review и предл

👎12

29 Jul 2026, 08:06 UTC826 views1 reactionsread 18 August 2026

Ведущий мобильный разработчик (Kotlin Multiplatform) в проект Лемана ПРО Проект Лемана ПРО — развитие логистических и клиентских мобильных решений с использованием современных технологий. 📝 Обязанности - Разработка новых функций мобильного приложения для клиента кроссплатформенно для Android и iOS. - Создание UI на Compose и SwiftUI с адаптацией под дизайн-систему компании. - Оценка трудоёмкости и сроков выполнения

👎1

14 Jul 2026, 19:30 UTC≈1,130 views3 reactionsread 18 August 2026
Photo

👨‍💻 Frontend-разработчики, нужен ваш профессиональный взгляд! Мы только запустили Racing Rodeo — автомобильную карточную игру внутри Telegram Mini App. Сейчас хотим проверить игру на реальных пользователях, найти ошибки и получить честную обратную связь. Особенно интересно мнение frontend-разработчиков по таким пунктам: 📱 адаптивность на разных устройствах; ⚡️ скорость загрузки и производительность; 🎨 интерфейс, а

2👎1

13 Jul 2026, 07:06 UTC≈1,010 viewsread 18 August 2026

Frontend Developer в компанию Eshe 📝 Обязанности - Адаптивная и кросс-браузерная вёрстка - Работа с макетами в Figma - Написание тестов - Работа с API 🔍 Требования - Опыт работы с JavaScript от 6 лет - Опыт работы с TypeScript от 5 лет - Опыт работы с Vue.js от 3 лет в продуктовых компаниях - Ссылки на опубликованные продукты - Гражданство РФ или РБ - Опыт не на фрилансе и не на менеджерских позициях 🕹 Условия - У

28 Jun 2026, 10:46 UTC≈1,320 views7 reactionsread 18 August 2026

Junior-Middle Fullstack Developer (JS/Python) - удалённо Компания: Present & Simple - российский бренд одежды и товаров для дома, который делает ставку на качество, минимализм и удобный клиентский опыт. Мы продолжаем развивать цифровую часть бизнеса и ищем Fullstack-разработчика, который поможет создавать новые решения для сайта и внутренних сервисов компании. Обязанности: - Разрабатывать и улучшать функционал сайт

👎6👍1

28 May 2026, 08:06 UTC≈1,540 views0 reactionsread 18 August 2026

Middle+/Senior React Native Developer в компанию Омега Солюшнс Омега Солюшнс — участие в международном проекте по разработке и поддержке мобильного приложения для заказчика из США и ЕС. 📝 Обязанности - Разработка и поддержка мобильного приложения на React Native - Создание переиспользуемых и безопасных компонентов - Интеграция мобильного приложения с REST API - Работа с компонентной архитектурой и управлением состо

27 May 2026, 13:06 UTC≈1,130 viewsread 18 August 2026

Middle+/Senior React Native Developer в международный аутсорс-проект Международный проект для заказчиков из США и ЕС, сфокусированный на разработке и поддержке мобильного приложения. 📝 Обязанности • Разработка и поддержка мобильного приложения на React Native • Создание переиспользуемых и типобезопасных компонентов • Интеграция мобильного приложения с REST API • Работа с компонентной архитектурой и управлением сост

27 May 2026, 09:06 UTC≈1,010 views4 reactionsread 18 August 2026

Frontend-разработчик (Junior / Junior+) в Модульбанк Модульбанк — digital-банк для предпринимателей и малого бизнеса с развитой продуктовой экосистемой. 📝 Обязанности - Разработка живых интерфейсов: работа с API, состоянием приложения, логикой, формами, таблицами и внутренними сервисами. - Участие в создании web-продуктов для клиентов банка. - Вовлечённость в улучшение пользовательского опыта и решение реальных биз

👎4

25 May 2026, 17:06 UTC946 views1 reactionsread 18 August 2026

Backend Python и Frontend React (senior) в компанию КА Холикод (аутстафф) AI Conversational BI Platform — Maturity Assessment for Visa. 📝 Обязанности - Backend: сервис-дизайн, API-контракты и схемы; интеграционная архитектура (Postgres, NAS, MCP, message bus); принятие решений по производительности и масштабируемости; ревью кода результата Claude и diff - Frontend: UX-дизайн (split-screen, diff overlay, conversatio

1

19 May 2026, 12:06 UTC≈1,120 viewsread 18 August 2026

Android-разработчик в маркетплейс товаров для красоты Проект — маркетплейс товаров для красоты с полным циклом покупки, бонусами, акциями, доставкой, реферальной системой и поддержкой 8 языков. 📝 Обязанности - Реализовывать сложные UI-компоненты (карточки сущностей с 4–6 вкладками, динамические формы) - Интегрироваться с backend через GraphQL - Участвовать в архитектуре фронта, оптимизировать производительность - В

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

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.

BUXORODA ISH BOR
@Buxoroda_ish_bor_Buxoroda_ish · 100,648
Telegram ranks this channel #45 of 53 here — alongside 52 others — read 18 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“Frontend (JS,CSS,HTML) вакансии и работа” (@YotolabFrontend), 2,140 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/YotolabFrontend.

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.