Channel
@diakupova
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,756subscribers
-3 since we began measuring on 3 November 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001945020588 |
|---|---|
| Type | Channel |
| Username | @diakupova |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 November 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/diakupova |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 16:11 | 1,756 | -3 |
| 3 Nov 2026, 05:22 | 1,759 | first reading |
8 posts held, back to 29 October 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 page of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 1 November 2026 |
|---|---|
| Posts held | 8 (29 October 2026 – 1 November 2026) |
| Views total | 7,038 |
| Reactions total | 806 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 05:22 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.
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.
806 reactions across 8 posts, in 11 distinct kinds. The most used accounts for 35.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5467794973296452899 | 287 | 35.6% | |
| custom 5237776436391070695 | 115 | 14.3% | |
| custom 5433670921258820831 | 106 | 13.2% | |
| custom 5400313589602994898 | 76 | 9.43% | |
| custom 5433789462356185984 | 71 | 8.81% | |
| custom 5377665982238061373 | 47 | 5.83% | |
| custom 5238201492124488039 | 40 | 4.96% | |
| custom 5316771738346869204 | 26 | 3.23% | |
| custom 5422732726182628418 | 20 | 2.48% | |
| custom 5210670262130866535 | 16 | 1.99% | |
| custom 5224197523622616238 | 2 | 0.248% |
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 are Telegram’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 8 of the 8 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 806 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 29 October 2026 to 1 November 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’s own ‘edited’ marker: 3 of 8 posts held from the last 30 days (37.5%) 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).
завершение дня 🧘♀️ села в машину, напротив мечеть, залюбовалась… думаю вот бы сейчас азан начался! и вот, как будто слышат💗
custom 543367092125882083142custom 531677173834686920412custom 54337894623561859849custom 54677949732964528997custom 53776659822380613733custom 54227327261826284181
моя бэсти стоит, ждет🚘 помыть уже надо.. пыль и песок так быстро налетают :( а грязными ездить нельзя, дают штраф💔
custom 543367092125882083153custom 523777643639107069523custom 537766598223806137310custom 54227327261826284187custom 54677949732964528992
как же мне хорошо💓💭
custom 540031358960299489852custom 542273272618262841812custom 543367092125882083111custom 54337894623561859848custom 54677949732964528997
я снова с утра на пляже 🌴🐚 сделала дома кофе с собой, без пробок доехала в 7 утра!☕️ вечером хочу на йогу еще! всем хорошего воскресенья🤍
custom 546779497329645289971custom 540031358960299489822custom 53167717383468692048custom 53776659822380613736
эх красота такая 🌟🌴 после массажа выпила чай с медом ✨ встретила закат, посидела чуть чуть и сейчас иду спать; рано вставать, а я уже больше чем сутки не сплю
custom 523777643639107069550custom 546779497329645289928custom 543378946235618598422custom 53167717383468692045custom 52382014921244880393
долетела!😴 посплю часок, потом схожу на массаж💇♀️🧖♂️ и вечером в отеле тут какая-то йога будет, тоже схожу🧎♀️
custom 546779497329645289954custom 543378946235618598427custom 523820149212448803912custom 53776659822380613735custom 53167717383468692041
ну что, вызвали меня на рейс✈️🤎 лечу в командировку в Индию хихи но так классно вышло, я после пляжа устала, и завалилась спать прям до вечера! так что чувствую себя прекрасно!💭
custom 546779497329645289986custom 523820149212448803925custom 53776659822380613737custom 54337894623561859845custom 54003135896029948982
🪸⭐️🌊
custom 523777643639107069542custom 546779497329645289932custom 521067026213086653516custom 537766598223806137316custom 52241975236226162382
Showing the 8 most recent of 8 posts we hold for @diakupova. 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.
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.
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“стюардесса по имени Ди” (@diakupova), 1,756 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/diakupova.
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.