Telegram RegisterThe public register of Telegram

Channel

читанинский дневник

@chitaninsky

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

928subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002118523672
TypeChannel
Username@chitaninsky
Descriptionменя зовут Таня, но ты можешь звать меня шароебиться в книжный @tpolosova
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/chitaninsky

Growth

9287 Aug 2026, 13:39 — 928 subscribers8 Aug 2026, 00:51 — 928 subscribers7 Aug 2026, 13:398 Aug 2026, 00:51
2 measurements taken within a single day. 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 927–929 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 00:51928no change
7 Aug 2026, 13:39928first reading

Engagement

7 posts held, back to 25 July 2026the 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
35.3%
avg views ÷ 928 subscribers
Avg views / post
328
7 posts measured
Reaction rate
21.1%
reactions ÷ views · ER floor
Posts in window
7
of 7 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 7 August 2026
Posts held7 (25 July 20267 August 2026)
Views total2,294
Reactions total483
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:51 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

Photos
1,050
Videos
49
Links
132

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2m 06s
Average length
1m 03s

Measured directly from 2 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.

Reaction mix

483 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 41.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 524243622679914904920141.6%
custom 531653152941594638515832.7%
custom 539537786472603854812425.7%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 7 of the 7 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 483reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 25 July 2026 to 7 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 7 we hold a reading for · 14%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @chitaninsky. 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 7 most recent posts we hold for this entry, published 25 July 2026 to 7 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.

Recent posts

7 Aug 2026, 17:36 UTC80 views52 reactionsread 8 August 2026
Photo

💚🍏🦎 хотела просто красивенько снять вам новую книжку, но получилось шедеврально (упс). никогда не рано начать прививать человеку хороший вкус

custom 524243622679914904919custom 531653152941594638518custom 539537786472603854815

4 Aug 2026, 09:09 UTC193 views51 reactionsread 8 August 2026
Forwarded from @vaticancamePhoto

🌸 начинаю горячо любимую всеми рубрику, да да столько подарков мне надарили, на целую рубрику — скажи что ты любишь зеленый цвет, не говоря ничего 🤎 у меня теперь есть видео свет, а это значит больше видео формата, БОЛЬШЕ! все остальное не нуждается в комментариях, как говорит один из моих любимых исполнителей - это любоооооооовь … а вообще внимательные заметили комментарии моей дарительницы в видео. вы же заметили

custom 524243622679914904923custom 531653152941594638515custom 539537786472603854813

31 Jul 2026, 18:06 UTC288 views95 reactionsread 8 August 2026
Photo

🌟🌟вот это все я уже давно раздарила, но хочу, чтобы вы тоже полюбовались 🥰 p.s. моя друллега просила называть их прямоугольными изделиями для книг, потому что я уж слишком часто произносила, что делаю закладки 😁

custom 524243622679914904942custom 531653152941594638530custom 539537786472603854823

29 Jul 2026, 18:57 UTC315 views35 reactionsread 8 August 2026

🍂🍂 в кружочках выше болтаю про Хогвартс Легаси и угрожаю всем, что скоро начну писать фанфики с Себастьяном Селлоу и Оминисом Мраксом 😀

custom 531653152941594638519custom 524243622679914904916

29 Jul 2026, 18:00 UTC313 views43 reactions1 Starread 8 August 2026
Video message

Video message, posted without a caption

custom 524243622679914904924custom 531653152941594638519

27 Jul 2026, 19:16 UTC487 views94 reactionsread 8 August 2026

🌟🌟🖤🐦запланировать свидание? нет, спасибо, я лучше буду планировать вторжение в самый охраняемый дворец вместе с бандой травмированных подростков, которые станут мне семьей

custom 524243622679914904941custom 531653152941594638531custom 539537786472603854822

25 Jul 2026, 15:14 UTC618 views113 reactionsread 8 August 2026
Photo

🌟🌟🌟 дамы и господа, 🌟🌟 вашему вниманию самая лютая вечеринка, которую я устраивала несколько месяцев назад подарила нам с Наташей по такому вот мини-блокнотику для коллажей, наконец-то до них дошли руки! мне нравится сидеть за оформлением, но делать это с подругой — совсем другое удовольствие. как будто бы все мои залежи канцелярии окупились в момент, когда другой человек ошемленно перебирал эти сокровища в нев

custom 539537786472603854851custom 524243622679914904936custom 531653152941594638526

Showing the 7 most recent of 7 posts we hold for @chitaninsky. 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 — 753,493 of 1,160,990entries 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 2 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.

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.

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“читанинский дневник” (@chitaninsky), 928 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/chitaninsky.

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.