Telegram RegisterThe public register of Telegram
Telegram profile photo for Серьезный тестировщик 🐞

Channel

Серьезный тестировщик 🐞

@serious_tester

On this record: Topic · Growth · Engagement · What this channel posts · Stars · Advertising · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

29,759subscribers

-647 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001127737843
TypeChannel
Username@serious_tester
Created20 October 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live6 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/serious_tester

Topic

Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 67% 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.

Growth

29,75930,40630,082.56 August 20266 November 2026
62 measurements spanning 92 days, net -647. 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 29,662–30,503 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
6 Nov 2026, 07:5029,759-3
5 Nov 2026, 08:3529,762-5
4 Nov 2026, 10:2529,767-6
3 Nov 2026, 11:3629,773-8
2 Nov 2026, 12:2829,781-14
1 Nov 2026, 08:5929,795-13
31 Oct 2026, 10:1629,808-4
30 Oct 2026, 07:4629,812-16
29 Oct 2026, 05:0029,828-28
28 Oct 2026, 06:0729,856-2
27 Oct 2026, 03:5029,858-4
26 Oct 2026, 03:5829,862-8
25 Oct 2026, 04:2529,870-9
24 Oct 2026, 06:1729,879-6
23 Oct 2026, 08:5629,885-2
22 Oct 2026, 12:1729,887-8
21 Oct 2026, 06:2129,895-10
20 Oct 2026, 06:3629,905-4
19 Oct 2026, 03:4729,909-13
18 Oct 2026, 02:4129,922first reading

Engagement

56 posts held, back to 11 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 156 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.7%
avg views ÷ 29,759 subscribers
Avg views / post
5,570
11 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
11
of 56 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 3 November 2026
Posts held56 (11 July 2026 – 3 November 2026)
Views total61,230
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 00:27 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
25s
Average length
25s

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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 56 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @serious_tester. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 56 most recent posts we hold for this entry, published 11 July 2026 to 3 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
5.36%
3 of 56 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
5,840
over 3 measured posts
Median views · rest
7,090
over 53 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
2VtzqvEBijV14 September 20264 September 2026
2VtzqwrrRJr123 July 202623 July 2026
2VtzqxXfpqx114 July 202614 July 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 56 most recent posts we hold, published 11 July 2026 to 3 November 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

Telegram’s own ‘edited’ marker: 0 of 11 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

3 Nov 2026, 08:28 UTC≈2,580 viewsread 6 November 2026

Топ-10 бесплатных (в основном) ресурсов для перехода QA → AI/ML Читать...

1 Nov 2026, 08:35 UTC≈3,510 viewsread 6 November 2026

Как тестировать API: 20 проверок, которые должен уметь делать QA Читать...

28 Oct 2026, 08:31 UTC≈5,850 viewsread 6 November 2026

Инженеры хотят расти, но не обязательно руководить Читать...

24 Oct 2026, 07:51 UTC≈7,090 viewsread 6 November 2026

Где заканчивается самостоятельность ИИ-агента? Я дала ему банковскую карту, телефон, браузер и 200+ MCP: итоги теста Читать...

22 Oct 2026, 07:02 UTC≈6,030 viewsread 6 November 2026
Photo

QA митап: про агентов, деньги и эволюцию QA Как оценивать ИИ-агентов, не разориться на токенах и понять, куда движется профессия тестировщика? Соберемся без пафоса, на практике разберем будущее. В программе: 🔘Eval будущего для агентов Как Eval'ы работают сейчас, какие у них проблемы и что будет завтра. 🔘Token FinOps: как инженеры перестают быть расходной статьей Откуда берутся расходы на LLM и как их срезать в три …

20 Oct 2026, 11:37 UTC≈5,000 viewsread 6 November 2026

Что полезно знать про процедуру увольнения по соглашению сторон Читать...

18 Oct 2026, 07:39 UTC≈5,400 viewsread 6 November 2026

Fetch для QA: как тестировать API прямо в DevTools, не открывая Postman Читать...

15 Oct 2026, 10:57 UTC≈6,800 viewsread 6 November 2026
Photo

Конец привычного уютного айти. Что делать дальше Читать...

13 Oct 2026, 08:22 UTC≈6,850 viewsread 6 November 2026
Photo

🌐 ИИ в управлении рисками: Предиктивная аналитика для тестировщика Приглашаем на открытый урок. 🗓 15 октября в 20:00 МСК 🆓 Бесплатно. Урок в рамках старта курса «ИИ в тестировании: ускорение процессов и проверка ИИ-функций». На вебинаре рассмотрим: ✔️Чем проактивное тестирование отличается от привычного подхода, при котором ошибки обнаруживаются уже после их появления. ✔️Какие данные можно использовать для прогноз…

12 Oct 2026, 08:26 UTC≈5,490 viewsread 6 November 2026
Photo

155 000 вакансий: полный анализ IT-рынка России. Как описание вакансии влияет на зарплату Читать...

9 Oct 2026, 08:47 UTC≈6,630 viewsread 6 November 2026
Photo

Рутину — в скилл, ошибку — в правило. Как я сделал QA-конвейер из скиллов Читать...

6 Oct 2026, 10:03 UTC≈7,570 viewsread 6 November 2026

Не ИИ заменит людей, а люди заменят ИИ. И это уже происходит Читать...

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

Posts recorded as deleted after publishing

We recorded 4 posts on @serious_tester as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
1 September 2026
Most recent seen missing
31 October 2026
Median time before seen missing
34 days
Seen missing in the last 30 days
2

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Тестировщик от бога
@godoftesting · 29,204
#1
Tester of QA
@testerofqa · 7,600
#2
QApedia | Тестирование
@qa_wiki · 12,974
#3
Artsiom Rusau QA Life - Тестировщик с нуля
@qachanell · 30,163
#4
Тестировщики нужны
@qa_chillout · 10,591
#5
QA Юмор | Тестирование
@memes_qa · 4,221
#6
QA Юмор
@qahumor · 6,171
#7
QA собес | Тестирование
@qa_sobes · 9,070
#8
Тестировщик | Вопросы собесов
@easy_qa_ru · 12,067
#9
Тестирование и жизнь • про работу для живых людей
@testing_and_life · 4,022
#10
Автоматизация тестирования
@automatedqa · 8,856
#11
QA Memes
@qa_memes · 4,018
#12
QA Sklad - Склад тестировщика
@qa_sklad · 23,109
#13
Automation QA | IT
@qa_automation_it · 5,010
#14
📚 ProTestingInfo 🔷 Канал по тестированию 📚
@protestinginfo · 14,855
#15
QARocks. Тестировщик Рулит 🐞
@qarocks · 17,873
#16
Библиотека тестировщика. QaRocks
@libqa · 11,958
#17
🧑‍💻 Уютное сообщество тестировщиков
@cozyqa · 7,870
#18
Alfa QA Talks
@AlfaQATalks · 3,180
#19
Short QA ideas
@short_QA · 4,586
#20
SQL для тестировщика
@sql_for_qa · 6,198
#21
Становимся тестировщиком (QA)
@to_be_qa · 6,884
#22
IT Юмор
@ithumor · 60,097
#23
Библиотека тестировщика | QA, тестирование, quality assurance, manual testing, autotesting, ручное тестирование, автотесты
@testerlib · 8,931
#24
🐞Библиотека QA
@qa_lib · 5,945
#25
QA❤️4Life | Testing | Тестирование ПО
@QA4Life · 7,828
#26
QA Jobs | Работа для тестировщика
@qa_work · 11,260
#27
Programmer & IT Memes
@itmemes · 121,992
#28
Yet another QA
@yetanotherqa · 6,528
#29
Тестировщик | IT
@testirovanie_ru · 4,830
#30
Тестировщик со вкусом
@testinglib · 4,684
#31
Ужасно медленная QA
@QA_with_a_spoon · 2,373
#32
Книги для тестировщика 📚 Библиотека тестировщика
@qabackup · 5,113
#33
🇺🇦 automation-remarks.com
@automation_remarks_ua · 7,613
#34
Собеседование тестировщика. QaRocks
@qasobes · 7,133
#35
Работа для тестировщиков. QA
@qajoboffer · 20,762
#36
QA Вакансии & Работа для тестировщиков
@YotolabQA · 8,793
#37
QA Studio | Тестирование
@qa_studio · 9,060
#38
Rozetked
@rozetked · 648,779
#39
QA Live 🚩 Тестирование ПО
@qa_Iive · 3,301
#40
QA.GURU — школа автоматизации тестирования
@qa_guru · 2,536
#41
QA Вакансии. Работа для тестировщиков. QaRocks
@jobforqa · 15,313
#42
QA Family by Alexey
@dev_qa · 1,810
#43
Заметки тестировщика | QA Notes
@qanote · 5,095
#44
Горящий Тестер 🐞 Антон Дуенин
@burning_tester · 5,683
#45
Тестирование | TestGrow
@QAtestgrow · 5,231
#46
Ещё один канал про QA
@irina_sh_qa · 2,811
#47
Test IT TMS
@testit_tms · 1,563
#48
MobileApps - мобильное тестирование | Mobile QA
@QAMobileApps · 3,837
#49
Заметки о QA
@notes_about_QA · 3,663
#50
QAtoDev | Тестирование
@QAtoDev · 3,603
#51
Testing | QA
@qa_and_it · 2,906
#52
Русова о QA
@rusovaqa · 1,593
#53
ProQuality Community
@ProQuality_Community · 2,814
#54
Джуны [Live]
@juniors_qa · 4,930
#55
Реальное тестирование | О работе тестировщика для новичков
@testinginreality · 2,590
#56
Горящий Собес 📈 Собеседование QA
@burning_sobes · 3,443
#57
Хабр
@habr_com · 134,148
#58
NoBugs
@nobugs_me · 2,683
#59
Lena and QA
@qabuggage · 2,359
#60
SmartQA
@smart_qa · 2,494
#61
Типичный программист
@tproger · 78,006
#62
QA Dojo | Про управление качеством
@qadojo_ru · 828
#63
Типичный QA
@typical_qa · 2,139
#64
Геннадий Чурсов | QA++
@chursovQA · 4,197
#65
Алексей | AQA PROKA4
@qa_proka4 · 3,383
#66
iOS Automation Testing
@ios_automation_testing · 1,997
#67
QA_Road_channel
@qa_road_channel · 7,121
#68
QA Community
@QAcommunityNEWS · 4,713
#69
Heisenbug — канал конференции
@heisenbug_channel · 1,339
#70
Вакансии по QA — тестирование, manual testing, autotests
@testerrjob · 8,189
#71
Java Memes → АйТи мемес
@java_memes · 6,129
#72
Тестировщик | Вакансии
@qa_testirovshchik_vakansii · 12,396 (as read 7 September 2026)
#73
Job for QA
@forallqa · 22,905
#74
Раньше всех. Ну почти.
@bbbreaking · 1,975,928
#75
r/ретранслятор
@retra · 165,780
#76
ВИЛСАКОМ РЕД / WYLSACOM RED
@wylsared · 1,091,275
#77
Очень интересно, только плакать хочется
@interesting_but_wanna_cry · 3,613
#78
Бэкдор
@whackdoor · 1,544,021
#79
Минцифры России
@mintsifry · 232,667
#80
Пекарня
@pekagame · 1,120,586
#81
Кинопоиск | Фильмы и сериалы
@kinopoisk · 794,814
#82
Двач
@dvachannel · 970,189
#83
Медуза — LIVE
@meduzalive · 1,118,113
#84
Varlamov News
@varlamov_news · 1,059,560
#85
КОНТЕКСТ
@kontext_channel · 865,612
#86
Эксплойт
@exploitex · 2,028,945
#87
Лентач
@lentachold · 391,777
#88
🌚Пятисотые на проде😱
@code500 · 10,781
#89
Дудь
@yurydud · 851,224
#90
Лентач
@oldlentach · 262,745
#91
Пикабу
@pikabu · 254,979
#92

Read from Telegram’s recommendation API, most recently 7 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Тестировщик от бога
@godoftesting · 29,204
Telegram ranks this channel #1 of 90 here — alongside 89 others — read 8 September 2026
QA Sklad - Склад тестировщика
@qa_sklad · 23,109
Telegram ranks this channel #4 of 94 here — alongside 93 others — read 18 September 2026
Artsiom Rusau QA Life - Тестировщик с нуля
@qachanell · 30,163
Telegram ranks this channel #5 of 92 here — alongside 91 others — read 7 September 2026
Работа для тестировщиков. QA
@qajoboffer · 20,762
Telegram ranks this channel #16 of 92 here — alongside 91 others — read 27 September 2026
IT Events 📆 АйТи События
@itevents · 17,317
Telegram ranks this channel #24 of 94 here — alongside 93 others — read 30 September 2026
Job for QA
@forallqa · 22,905
Telegram ranks this channel #24 of 95 here — alongside 94 others — read 20 September 2026
IT - стажировки и обучение
@it_interns · 31,669
Telegram ranks this channel #69 of 97 here — alongside 96 others — read 6 September 2026

This channel appears in 7 seed channels' Telegram-generated recommendation lists 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“Серьезный тестировщик 🐞” (@serious_tester), 29,759 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/serious_tester.

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.