Карта Гугл goo.gl/maps/4eum5C9giNDebgXf7
Хронологическая карта www.creamy-caprice.net/
Чат подписчиков https://t.me/+vfT24tj5ZH0yYzMy
Прислать геопривязку и связь с админом через "Сообщения каналу"
Created
17 February 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
National news — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 52% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
33 measurements spanning 53 days, net +822. 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 52,382–53,450 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
27 Sept 2026, 22:58
53,327
+73
15 Sept 2026, 12:56
53,254
-13
13 Sept 2026, 19:36
53,267
+15
12 Sept 2026, 00:01
53,252
+67
9 Sept 2026, 17:19
53,185
+184
6 Sept 2026, 07:19
53,001
+4
3 Sept 2026, 23:20
52,997
+31
2 Sept 2026, 12:35
52,966
+24
1 Sept 2026, 10:05
52,942
+12
31 Aug 2026, 11:47
52,930
+3
30 Aug 2026, 10:16
52,927
+30
29 Aug 2026, 09:47
52,897
+23
28 Aug 2026, 07:42
52,874
-7
27 Aug 2026, 07:54
52,881
-29
26 Aug 2026, 05:32
52,910
+3
25 Aug 2026, 03:27
52,907
-34
22 Aug 2026, 07:38
52,941
+18
20 Aug 2026, 20:54
52,923
+6
19 Aug 2026, 22:21
52,917
+23
18 Aug 2026, 20:26
52,894
first reading
Engagement
312 posts held, back to 4 August 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 112 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
34.0%
avg views ÷ 53,327 subscribers
Avg views / post
18,100
168 posts measured
Reaction rate
1.63%
reactions ÷ views · ER floor
Posts in window
168
of 312 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 September 2026
Posts held
312 (4 August 2026 – 30 September 2026)
Views total
3,045,300
Reactions total
49,605
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
30 Sept 2026, 17:47 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
≈8,780
Videos
≈4,010
Links
≈8,010
Lifetime counters from Telegram’s own channel header, read 30 September 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
2h 48m
Average length
1m 19s
Measured directly from 127 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
93,004 reactions across 300 posts, in 65 distinct kinds. The most used accounts for 41.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🙏
38,739
41.7%
👍
12,944
13.9%
🔥
9,157
9.85%
🤬
8,136
8.75%
❤
7,253
7.80%
🤡
4,585
4.93%
🤔
2,922
3.14%
😁
1,515
1.63%
🫡
1,203
1.29%
🤣
928
0.998%
🤯
705
0.758%
👎
613
0.659%
😢
469
0.504%
✍
440
0.473%
😡
387
0.416%
❤🔥
272
0.292%
💩
272
0.292%
👏
271
0.291%
🖕
254
0.273%
🤮
202
0.217%
45 further kinds
1,737
1.87%
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 312 of the 312 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 96,425 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 312 most recent posts we hold, published 4 August 2026 to 30 September 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
22
across the posts below
Posts paid on
18
of 312 we hold a reading for · 6%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @creamy_caprice. 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 312 most recent posts we hold for this entry, published 4 August 2026 to 30 September 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.
30.09.26 Великий Бурлук - Ольховатка
Активные боевые действия в Харьковской зоне безопасности.
Механизированная атака ВСУ в составе двух единиц бронетехники в направлении Ольховатки. Огневой налёт на позиции ВС РФ в жилой застройке. Отход бронетехники с позиции. Боевые действия на глубине до 1,5 км в зоне контроля ВС РФ.
50.18764,37.50805 На карте
Источник 21+
Геопривязка
Геопривязка
#ua #add
Помощь СВО. Краснолиманский фронт.
Друзья, информация по сбору для бойцов-краснолиманцев.
Общими усилиями нам удалось собрать большую часть суммы, и мы уже начали оформлять заказ оборудования. На Ozon заказаны 3 зарядные станции (оплата будет при получении). Также пытаемся забронировать усилитель сигнала для дронов «Инкубатор 2.0» с получением на месте в Ростове.
Мы искренне благодарим всех, кто уже поддержал наши…
29.09.26 Сумы - Малая Корчаковка
Позиционные боевые действия в Сумской зоне безопасности.
Применение реактивной системы залпового огня для нанесения огневого поражения по позициям ВСУ в окрестностях Малой Корчаковки. Уточнение зоны контроля ВСУ.
Сектор обстрела:
51.09883,34.87669 На карте
Источник
Геопривязка
#ua #add
30.09.26 Орехов - Егоровка
Последствия боевых действий в районе Орехова.
Военнослужащие ВС РФ подняли флаги России в Егоровке, заявляя контроль населённого пункта. Уточнение зоны контроля ВС РФ на северном охвате Орехова.
47.62172,35.94841 На карте
47.62349,35.94392 На карте
47.62268,35.94556 На карте
Источник
Геопривязка
#ru #add
29.09.26 Великая Новосёлка - Шевченко
Активные боевые действия в районе Великой Новосёлки.
Военнослужащий ВСУ попал под обстрел ВС РФ на окраине Шевченко. Инфильтрационная активность ВСУ на глубине около 6 км в зоне контроля ВС РФ.
47.90266,36.66823 На карте
Источник
Геопривязка
#ua #add
29.09.26 Красный Лиман - Новое - Катериновка
Последствия боевых действий в районе Красного Лимана.
Военнослужащие ВСУ поднимают флаги Украины в Новом и Катериновке, заявляя контроль населённых пунктов. Продвижение ВСУ до 2 км, контроль жилой застройки в Новом.
49.16059,37.82740 На карте
49.18252,37.86163 На карте
Источник 21+
#ua
29.09.26 Красный Лиман - Редкодуб
Последствия боевых действий в районе Красного Лимана.
Военнослужащие ВФУ поднимают флаги Украины в Редкодубе. Увеличение зоны контроля ВФУ до 500 метров в северной части населённого пункта.
49.18915,37.79549 На карте
Источник 21+
Геопривязка
#ua
28.09.26 Красный Лиман - Карповка
Последствия боевых действий в районе Красного Лимана.
Военнослужащие ВФУ разворачивают флаг Украины в западной части Карповки, заявляя контроль населённого пункта силами Украины. Событие на удалении до 2 км от зоны контроля ВС РФ.
49.16776,37.71951 На карте
Источник 21+
Геопривязка
#ua #add
Помощь СВО. Краснолиманский фронт.
Друзья, наш сбор для подразделения с Краснолиманского направления в самом разгаре. Уже собрана значительная часть необходимых средств, и мы начали обсуждать детали закупки оборудования, поставщиков и прочие нюансы. Постараемся подловить момент с хорошими ценами на зарядные станции, чтобы не тратить деньги впустую. Может быть, что-то закупим уже в ближайшее время.
Осталось собрать …
28.09.26 Глухов - Уланово
Последствия боевых действий в Сумской зоне безопасности.
Флаги России развёрнуты в населённом пункте Уланово.
51.75378,34.30846 На карте
51.75552,34.30736 На карте
Источник
#ru #add
28.09.26 Золочев - Токаревка
Позиционные боевые действия в Харьковской зоне безопасности.
Передовая позиция ВС РФ в жилой застройке Токаревки обстреляна ВСУ. ВС РФ продвинулись более 1 км и заняли новые позиции в восточной части населённого пункта.
50.28113,36.23940 На карте
Источник 21+
Геопривязка
#ru
🙏227❤43👍26🤡4😁4🖕3🤣2💩1
Showing the 12 most recent of 312 posts we hold for @creamy_caprice. 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.
Posts edited after publishing
@creamy_caprice edited 7 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
8 August 2026
Most recent edit
26 September 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 64 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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 27 September 2026 — this
entry's latest reading, not the date you are reading this.
“Сливочный каприз” (@creamy_caprice), 53,327 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/creamy_caprice.
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.