4 measurements spanning 7 days, net -2. 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 4,882–4,888 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 17:54
4,885
+2
11 Aug 2026, 03:04
4,883
-4
8 Aug 2026, 05:05
4,887
no change
7 Aug 2026, 11:46
4,887
first reading
Engagement
4 posts held, back to 23 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 8 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
14.5%
avg views ÷ 4,885 subscribers
Avg views / post
707
1 post measured
Reaction rate
1.84%
reactions ÷ views · ER floor
Posts in window
1
of 4 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 30 July 2026
Posts held
4 (23 April 2026 – 30 July 2026)
Views total
707
Reactions total
13
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 05:10 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
98 reactions across 4 posts, in 7 distinct kinds. The most used accounts for 37.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
37
37.8%
❤🔥
21
21.4%
🥴
16
16.3%
💅
9
9.18%
😍
8
8.16%
🔥
5
5.10%
🍓
2
2.04%
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 4 of the 4 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 98reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 23 April 2026 to 30 July 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.
На носу август, за окном дождь – настроение: читать взахлеб книги с запахом библиотеки или погрузиться в очередное обучение
Вовремя наткнулась на интенсив от Тани Аристовой «ВИЗУАЛЬНЫЙ КОД»
Таню я знаю давно, она автор потрясающего канала ОЙ, КАК КРАСИВО и создатель блокнота authenticity, поработав с которым я за 3 месяца увеличила число подписчиков в своей инсте с 700 человек до 7’700 😮💨
Я человек простой: вижу …
«А как на счет того, чтобы каждый выходной этого лета делать что-то новенькое?», – подумала я в середине июня. И вот к концу месяца в моей корзине йога со щенками, рыбалка и забег по музеям
Делюсь незаслуженно непопулярным музеем декоративного искусства, во дворе которого можно послушать интереснейшие лекции. Например, про сарафан, как честь русского костюма, про русский кокошник, про ивановские ситцы и многое друго…
Если цвет сезона варьируется где-то между бирюзовым и тиффани, то принт сезона – безусловно милитари
Говорят, в турбулентные времена мода всегда обращается к комуфляжному принту, не удивительно, что в 2026 мы видим его повсюду
Брюки, кепки, куртки, КАПРИ (!) – да всё, что угодно. Я подумываю об огромных брюках, но можно начать и с чего-то менее грандиозного, например, сегодня видела шопер в бифрульке
Как вам тренд…
Совершенно случайно обнаружила секретный ТГ-канал от поставщиков OSKELLY
Много винтажных старушек в очень хорошем состоянии. За аутентификацию ребята ручаются головой, а сотрудничество с OSKELLY говорит само за себя
Мне приглянулись редкие экземпляры от Coach, винтажные Gucci, а также поглядываю в сторону совершенно новых Tabi
Проблема одна – все лакомые кусочки довольно быстро улетают, поэтому это один из немноги…
❤11💅5😍5
Signed Anastasia
Showing the 4 most recent of 4 posts we hold for @pinkfiction. 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.
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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“Pink Fiction” (@pinkfiction), 4,885 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/pinkfiction.
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.
