3 measurements spanning 4 days, net -1. 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 1,030–1,031 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Aug 2026, 10:48
1,030
-1
8 Aug 2026, 00:21
1,031
no change
7 Aug 2026, 22:31
1,031
first reading
Engagement
18 posts held, back to 1 April 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
48.4%
avg views ÷ 1,030 subscribers
Avg views / post
499
4 posts measured
Reaction rate
5.02%
reactions ÷ views · ER floor
Posts in window
4
of 18 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
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
18 (1 April 2026 – 6 August 2026)
Views total
1,994
Reactions total
100
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 00:21 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
528 reactions across 18 posts, in 12 distinct kinds. The most used accounts for 47.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
250
47.3%
❤
125
23.7%
👍
63
11.9%
🕊
52
9.85%
👏
14
2.65%
💯
6
1.14%
🤔
6
1.14%
😁
5
0.947%
👌
3
0.568%
👀
2
0.379%
😡
1
0.189%
🤝
1
0.189%
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 18 of the 18 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 528reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 1 April 2026 to 6 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.
Telegram Stars
Stars received
1
across the posts below
Posts paid on
1
of 18 we hold a reading for · 6%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @parawriter. 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 18 most recent posts we hold for this entry, published 1 April 2026 to 6 August 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.56%
1 of 18 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,370
over 1 measured post
Median views · rest
915
over 17 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
erid
Posts
First seen
Last seen
2Vtzqvqqegw
1
20 April 2026
20 April 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 18 most recent posts we hold, published 1 April 2026 to 6 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.
Привет! Как проходит лето?
Если вы хотели встряхнуться и срочно решить какую-нибудь интересную задачку, у меня есть для вас кое-что.
10 августа заканчивается приём заявок на TechWriter Days 4!
Да-да, IV Международная конференция для технических писателей пройдёт в Москве 19–20 марта 2027 года, но задуматься о докладе можно и нужно уже сейчас!
Если вы хотите поделиться своими знаниями или опытом с профессиональным…
Осторожно! Этот пост душный на пять закрытых форточек из пяти
Недавно я придумывал определения для глоссария. Запнулся на термине «команда»:
Команда — это функциональная единица [название подразделения], которая занимается разработкой, сопровождением и поддержкой сервисов.
С содержанием всё ок, а вот выбранная форма мне никак не давала покоя. Смотрел я на неё и так, и эдак, и не мог понять: что же именно не так?
О…
Месяцы подготовки, планирования, согласований, прогонов и вычиток.
Два часа прямого эфира из прекрасной студии в центре Москвы. Профессиональная команда за спиной, которая обеспечивает красивую картинку, хороший звук и надёжную трансляцию.
Четыре человека в кадре, готовые поделиться своим опытом.
И всё это — первый TechDocs митап от RWB!
Я очень рад, что мы сделали это! 🦾
Спасибо всем причастным, а особенно моим…
Свершилось!
Уже совсем скоро, в четверг 16 июля мы проведём онлайн-митап по технической документации!
Наверняка кто-то сейчас спросил в недоумении: а кто это «мы»?
Отвечаю: мы — это RWB, и мы проводим TechDocs митап!
Впервые на арене! Вас ждут непревзойдённые мастера пера и акулы инструкций! Аксакалы документации поделятся своими практическими кейсами — спешите, спешите, спешите!
Билет всего 4 сольдо Совершенно …
Ежедневно я ревьюю много технической документации. Иногда мне попадаются тексты, которые подозрительно похожи на сгенерированные искусственным интеллектом. Доказать свои подозрения я не могу, но могу поделиться признаками, по которым я определяю AI-контент.
1. Длииинные тире
Сами по себе длинные тире ничего не значат — я активно их использую даже в повседневной смартфонной жизни, не говоря уже о доке. Тут дело не в…
О чём мечтает каждый писатель? Выспаться? Создать шедевр? Получить пулитцеровскую или хотя бы квартальную премию?
И то, и то, и это. Но главная мечта любого порядочного писателя — опубликовать свою книжку.
Пост чисто похвастаться если что, так что будьте готовы)
Этот пункт теперь я считаю выполненным.
Вы наверное помните, что я не только технический писатель, но ещё и немного хоровой композитор. Мы с моими друзья…
Привет!
На работе я занимаюсь сопровождением внутренней документации инфраструктурных команд: кубернетисы, ансиблы, виртуальные машины, кластеры, поды, ноды, прокси, неймспейсы… Очень много разных сложных слов, которые по-разному взаимодействуют друг с другом и с читателями.
По ходу пьесы я начал разбираться с тем, что это вообще такое и для чего оно нужно, стал постепенно погружаться в этот лор и со временем уже м…
Material for MkDocs — это популярный фреймворк для разработки документационных систем, который я активно использую в рабочих, домашних и парарайтерских проектах.
Сейчас при сборке проектов на MkDocs Material выскакивает страшное предупреждение:
⚠️ Warning from the Material for MkDocs team
MkDocs 2.0, the underlying framework of Material for MkDocs, will introduce backward-incompatible changes, including:
× All plug…
Ура!
Спустя почти год наконец-то выходит второй пост рубрики #вопрос_ответ
Какой формат работы с git выбрать для ведения документации в парадигме docs as code?
На мой взгляд, самый подходящий формат работы в гите для документационных проектов небольших команд — github flow
Этот процесс подразумевает наличие одной основной ветки master и нескольких фиче-веток для каждой отдельной задачи.
Когда вам нужно что-то изм…
Друзья, прошу прощения — забыл уточнить важный момент:
Стажировка подходит только тем, кто учится на очной форме в любом учебном заведении. Так что, если вы студент, смело подавайте заявку! 🧑🎓
А если нет, приходите в комментарии, посочувствуем друг другу 🤗
Привет!
Отличная новость для всех, кто хочет начать карьеру технического писателя (и не только) : YADRO приглашает на стажировку по более чем 30 направлениям, в числе которых есть и разработка технической документации!
YADRO Импульс — это программа оплачиваемой стажировки в офисе или удалённо (что особенно круто). Вас ждут два с половиной месяца активной работы: погружение в реальные продукты компании и решение нас…
👍5
Showing the 12 most recent of 18 posts we hold for @parawriter. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank
Citation-graph rank — 911,368 of 1,189,255entries 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 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.
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 11 August 2026 — this
entry's latest reading, not the date you are reading this.
“Parawriter” (@parawriter), 1,030 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/parawriter.
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.