Telegram RegisterThe public register of Telegram

Channel

🧑‍💻 Уютное сообщество тестировщиков

@cozyqa

On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Cite this entry

7,932subscribers

-22 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001234861171
TypeChannel
Username@cozyqa
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/cozyqa

Growth

7,9327,9547,9436 August 2026 — 7,954 subscribers6 August 2026 — 7,954 subscribers7 August 2026 — 7,946 subscribers9 August 2026 — 7,940 subscribers12 August 2026 — 7,932 subscribers6 August 202612 August 2026
5 measurements spanning 7 days, net -22. 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,929–7,957 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:547,932-8
9 Aug 2026, 17:227,940-6
7 Aug 2026, 03:117,946-8
6 Aug 2026, 04:017,954no change
6 Aug 2026, 03:527,954first reading

Engagement

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

ERR · 30 days
8.51%
avg views ÷ 7,932 subscribers
Avg views / post
675
9 posts measured
Reaction rate
0.437%
reactions ÷ views · ER floor
Posts in window
9
of 24 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 5 of 9 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 12 August 2026
Posts held24 (13 May 202612 August 2026)
Views total6,077
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 16:57 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
46s
Average length
46s

Measured directly from 1 video 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

41 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 29.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1229.3%
👍1126.8%
👎717.1%
💩614.6%
🔥49.76%
12.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 24 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 48reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 13 May 2026 to 12 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.

Advertising

Ad load
4.17%
1 of 24 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
451
over 1 measured post
Median views · rest
967
over 23 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFJfmVAh110 August 202610 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 24 most recent posts we hold, published 13 May 2026 to 12 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

12 Aug 2026, 10:20 UTC257 viewsread 12 August 2026

Чат с вашими резюме. Присылайте резюме, чтобы HR вас увидела и ей(ему) было удобно с вами связаться. QA Резюме P.S сейчас там можно бесплатно «прожарить» свое резюме на предмет ошибок и обхода ATS

10 Aug 2026, 13:50 UTC421 viewsread 12 August 2026
Photo

Тестируем яблоко: смартфоны, планшеты и часы Автор: М. А. Осина Год издания: 2023 Скачать книгу

10 Aug 2026, 07:40 UTC451 views7 reactionsread 12 August 2026
Advertisementerid 2W5zFJfmVAhVideo

✅ SaveTest — новая TMS для управления тест-кейсами, прогонами и отчетностью. Современный подход: тест-кейсы можно вести как код, хранить их в YAML, python, gherkin-файлах в Git. Сценарий простой: 1. Создаете тест-кейсы в VS Code или Cursor. 2. Загружаете их в репозиторий, например в GitHub или Gitlab. 3. SaveTest синхронизирует изменения и подтягивает их в интерфейс. * Но можно вести и классические проекты Переход

3👍2🔥2

10 Aug 2026, 05:35 UTC440 views2 reactionsread 12 August 2026
Photo

💥 Материалы о работе с Playwright 🚩 Global Cache, или как выполнить BeforeAll в Playwright один раз для всех воркеров. BeforeAll в Playwright запускается в каждом воркере, а не один раз на все тесты — и это часто ломает ожидания тестировщиков. В статье разбирается, почему так происходит и какие есть стандартные обходные пути. 🚩 Ожидания и таймауты в Playwright. Тестируя основные пользовательские потоки сайта с помо

1👍1

6 Aug 2026, 12:18 UTC634 views2 reactionsread 12 August 2026

❓ Что происходит с баг-репортом, если ему ставят статус «Не баг»? Когда баг-репорт получает статус Rejected, As Designed или Not a Bug, это означает, что система работает именно так, как было задумано, либо ошибка произошла на этапе тестирования. ✅ Основные причины такого статуса: 🎌 Спецификация: поведение системы соответствует требованиям, даже если оно кажется странным или неудобным. Это «фича», а не ошибка. 🎌

1👍1

31 Jul 2026, 13:36 UTC808 viewsread 12 August 2026
Photo

Agile-тестирование Автор: Джанет Грегори Год издания: 2019 Скачать книгу

23 Jul 2026, 11:59 UTC≈1,160 viewsread 12 August 2026
Photo

📌 Статьи о метриках в тестировании 🎌 Важные метрики тестирования программного обеспечения. В статье на примерах и графиках рассмотрены метрики, используемые в тестировании программного обеспечения, и их правильное применение. 🎌 QA-метрики: что на самом деле важно измерять и как в этом помогает TMS. Когда интуитивного тестирования уже недостаточно и качество ведет себя непредсказуемо, метрики перестают быть формальн

20 Jul 2026, 14:06 UTC967 views2 reactionsread 12 August 2026
Photo

Оффер редко приходит сам. Обычно между «без работы» и «оффер получен» стоят десятки откликов, доработок резюме и часов поиска. Talanto.work помогает пройти этот путь быстрее: 🟠 50 000+ IT-вакансий с разных сайтов 🟠 Telegram-бот с уведомлениями по вашим фильтрам 🟠 Проверка резюме и рекомендации по улучшению 🟠 Проверка соответствия резюме конкретной вакансии 🟠 Генератор персональных сопроводительных писем Ищите р

1👍1

15 Jul 2026, 12:10 UTC939 views2 reactionsread 12 August 2026

❓ Что делать, если нужно пройти регресс, а времени нет? Когда на полную регрессию не хватает времени, главная задача — минимизировать риски и защитить критически важный функционал. Вот 5 практических стратегий для такой ситуации: 1️⃣ Фокус на критическом пути (Smoke-тестирование) Если времени катастрофически мало, проведите базовый smoke-тест. Убедитесь, что приложение запускается, основные бизнес-цели пользовател

👍2

7 Jul 2026, 08:32 UTC≈1,010 views2 reactionsread 12 August 2026
Photo

Тестирование видеоигр Автор: Торговкин Александр Год издания: 2024 Скачать книгу

2

1 Jul 2026, 08:22 UTC≈1,170 viewsread 12 August 2026
Photo

💥 Полезные статьи о работе с Selenium 6️⃣ Пройди собеседование на QA: 15 популярных вопросов и ответов (Python + Selenium + API). Готовитесь к собеседованию по тестированию? В этом материале собраны основные вопросы по работе с Python, Selenium и API, которые помогут вам подготовиться к интервью и повысить шансы на успешное трудоустройство. 2️⃣ Начало работы с Selenium IDE. Из этой статьи вы узнаете, как пользовать

27 Jun 2026, 13:56 UTC≈1,050 viewsread 12 August 2026

@rabotadlaqa - чат для поиска работы тестировщиков. HR менеджеры - welcome

Showing the 12 most recent of 24 posts we hold for @cozyqa. 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 — 238,215 of 1,183,361entries 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 4 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“🧑‍💻 Уютное сообщество тестировщиков” (@cozyqa), 7,932 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/cozyqa.

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.