Telegram RegisterThe public register of Telegram
Telegram profile photo for реальная телка печатает…

Channel

реальная телка печатает…

@iamdidisha

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

450subscribers

-4 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-1001719731089
TypeChannel
Username@iamdidisha
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live21 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/iamdidisha

Growth

4504544527 August 2026 — 454 subscribers8 August 2026 — 454 subscribers15 August 2026 — 452 subscribers21 August 2026 — 450 subscribers7 August 202621 August 2026
4 measurements spanning 14 days, net -4. 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 449–455 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 21:17450-2
15 Aug 2026, 05:25452-2
8 Aug 2026, 05:00454no change
7 Aug 2026, 17:01454first reading

Engagement

11 posts held, back to 5 August 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
34.7%
avg views ÷ 450 subscribers
Avg views / post
156
11 posts measured
Reaction rate
8.55%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 held11 (5 August 20267 August 2026)
Views total1,719
Reactions total147
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05:00 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
4s
Average length
4s

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

147 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 539326892840952069112685.7%
custom 528088867386322022685.44%
custom 535719193326754965964.08%
custom 528522163014495402342.72%
custom 524258815267728263832.04%

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

Measured over the 11 most recent posts we hold, published 5 August 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.

Recent posts

7 Aug 2026, 21:04 UTC74 views6 reactionsread 8 August 2026
Photo

прогулялись с мужем по нашей гостинице. завтра переезжаем и начинается вторая часть нашего путешествия! 🤍

custom 53932689284095206916

7 Aug 2026, 16:44 UTC123 views8 reactionsread 8 August 2026
Photo

сегодня катались по Неве. ☀️

custom 53932689284095206918

7 Aug 2026, 12:17 UTC140 views10 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 539326892840952069110

7 Aug 2026, 07:21 UTC152 views16 reactionsread 8 August 2026
Photo

наше нишевое семейное увлечение - это улиты:

custom 539326892840952069113custom 52425881526772826383

6 Aug 2026, 20:06 UTC163 views18 reactionsread 8 August 2026
Photo

наш гранд отель европа. так романтично в нем жить. в честь праздника повысили категорию номера до люкса, поэтому он просторный и шикарный. завтра пойдем на историческую экскурсию по отелю. чувствуем себя очень важными, когда бросаем чангу у входа и тащим пакеты из спара в номер, проходя мимо витрин с какими-то гипер дорогими коллекциями kiton и pasquale bruni (я люблю ужинать в номере сыром бри и глазированными сырка

custom 539326892840952069118

6 Aug 2026, 19:22 UTC159 views13 reactionsread 8 August 2026
Photo

прошли 16к шагов. ужинаем.

custom 539326892840952069111custom 53571919332675496592

6 Aug 2026, 13:37 UTC172 views13 reactionsread 8 August 2026
Photo

сомневались во мне?

custom 539326892840952069112custom 53571919332675496591

6 Aug 2026, 09:09 UTC176 views11 reactionsread 8 August 2026
Video

я и моя «любовь» к белкам:

custom 53932689284095206917custom 52852216301449540234

6 Aug 2026, 08:51 UTC179 views23 reactionsread 8 August 2026
Photo

сегодня решили позавтракать в номере. какой же здесь вкусный черничный джем. думала, придется его вымаливать к сырникам, а по итогу принесли граммов двести и сметану сверху. помните, я рассказывала, как люблю сметану с вареньем. в целом, в этом кисломолочно-сладком браке сырники уже были не нужны. 😂 сегодня на могилу к Петру I, на Крестовский остров, а вечером все-таки хочется прильнуть к туристическому потоку и гля

custom 539326892840952069115custom 52808886738632202268

5 Aug 2026, 17:15 UTC190 views15 reactionsread 8 August 2026
Photo

муж балует. давно хотела попробовать. думаю, после 14к шагов - позволительно.

custom 539326892840952069114custom 53571919332675496591

5 Aug 2026, 15:04 UTC191 views14 reactionsread 8 August 2026
Photo

поехали к Петру I в Кронштадт. отдали дань. погуляли.

custom 539326892840952069112custom 53571919332675496592

Showing the 11 most recent of 11 posts we hold for @iamdidisha. 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.

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

“реальная телка печатает…” (@iamdidisha), 450 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/iamdidisha.

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.