Channel
@gurovplus
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,232subscribers
+37 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001696139587 |
|---|---|
| Type | Channel |
| Username | @gurovplus |
| Created | 17 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 2 times, most recently 14 September 2026 |
| On Telegram | t.me/gurovplus |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 13:20 | 2,232 | +4 |
| 5 Sept 2026, 05:17 | 2,228 | +3 |
| 1 Sept 2026, 04:45 | 2,225 | -2 |
| 29 Aug 2026, 05:05 | 2,227 | +3 |
| 26 Aug 2026, 02:16 | 2,224 | +2 |
| 23 Aug 2026, 03:05 | 2,222 | +7 |
| 19 Aug 2026, 11:58 | 2,215 | +4 |
| 16 Aug 2026, 02:13 | 2,211 | +14 |
| 12 Aug 2026, 12:04 | 2,197 | -1 |
| 9 Aug 2026, 15:11 | 2,198 | +2 |
| 7 Aug 2026, 00:46 | 2,196 | +1 |
| 6 Aug 2026, 06:05 | 2,195 | first reading |
14 posts held, back to 26 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 2 pages 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 14 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 6 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.
211 reactions across 14 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🕊 | 211 | 100.0% |
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 14 of the 14 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 211 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 26 July 2026 to 5 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.
https://osnova-workshop.vercel.app В качестве приглашения в менторские группы, собрал небольшой текстовый лонгрид с описанием. Получилось и приглашение и пример вайбкодинга. На сайте вам доступен инструмент кастомизации страницы. Так что если вы настроите интересный вариант композиции - пришлите в комменты – я добавлю в оригинал!
🕊24
Signed Сергей
вечерний вайбкодинг
🕊20
Signed Сергей
Photo, posted without a caption
🕊16
Signed Сергей
Photo, posted without a caption
🕊7
Signed Сергей
Мы тут с Мишей подготовили небольшой отчет по процессу вайбкодинга, который может помочь ускорить ваш процесс работы. Можно сказать что все сводиться к трем вещам: 1. Собирать макет как стенд а потом накладывать макет из Фигмы 2. Используйте параметрическую панель 3. Учитесь дизайн мышлению. Гарантия хорошего вайб кодинга – это прежде всего способность задумать и обьяснить макет в деталях. А это уже в менторских груп…
🕊11
Signed Сергей
https://mdl-gr2.vercel.app Я не отдаю макет на вайб-кодинг. Сначала собираю в браузере тестовый стенд и проектирую на нём механику сайта — из формальных элементов: прямоугольники, рыбный текст. Типографика и цвет не важны — важно, как макет работает: архитектура, конструкция, механизм и его элементы: связи, размер, скорость, манера движения, ритм, темп. Готовый макет из Figma ложится на стенд потом — вопросов у ней…
🕊17
Signed Сергей
https://mdl-gr2.vercel.app Выложил новый стенд. Главное, что хочу сказать про него: движение само по себе алгоритмично. И это не потрогаешь на макете, когда работаешь исключительно с Figma. О своем подходе к вайб кодингу я расскажу в следующем сообщении👉 Этот макет я собрал за четыре часа. Три с половиной из них ушли на адаптивность и анимацию. Полчаса — просто на то, чтобы перенести макет в браузер. Хотя, вру: н…
🕊14
Signed Сергей
Признаюсь, тяжело постить сюда абсолютно все идеи и размышления, ибо у меня есть внутренний фильтр, который тормозит выкладывать любые raw-идеи. Кажется, что в чём-то я не на 100% уверен. А если не уверен и не проверил научно, на опыте — то нечего и делиться, ведь я же профи. Сегодня сказал одно, а завтра уже поменял мнение. Но по факту это неверно. Думаю, что людям будет всё же интересно видеть даже сырые мысли. Хо…
🕊23
Signed Сергей
Вайб-код дает возможность делать такой панк, который раньше никто бы не сделал. — Не потому что нельзя, а потому что дорого, и панк столько стоить не может. Дорогой панк — это имитация.
🕊18
Signed Сергей
Photo, posted without a caption
🕊11
Signed Сергей
Признаюсь, что я очень люблю фотогалереи. Почему? Потому что это предельная форма дизайна, где содержание имеет меньший интерес, чем сама форма. В идеальной галерее вообще не должно быть текста. Всё может быть понятно из самого её построения и из движения внутри неё. Другое дело, что наше представление о фотогалереях довольно узкое. Оно держится на функциональных ограничениях, которые мы сами приписали этому формату…
🕊13
Signed Сергей
Video, posted without a caption
🕊21
Signed Сергей
Showing the 12 most recent of 14 posts we hold for @gurovplus. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Gurov+” (@gurovplus), 2,232 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/gurovplus.
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.