Звёздное небо над Донецком Калининский | Предложить новость
❤23🤩2😁1

Channel
@Kalininskiytyt
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
20,159subscribers
+635 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001797850853 |
|---|---|
| Type | Channel |
| Username | @Kalininskiytyt |
| Description | Новости, события Калининского района Предложить новость @Kalininskiyrayon_bot Размещение рекламы @reklama_donrayon_bot Ссылка на вступление 👉 https://t.me/joinchat/pQVOn49yeaBhNzRi |
| Created | Between 1 February 2022 and 31 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/Kalininskiytyt |
Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 11 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @Voroshilovskiytyt/3596918 Aug 2026, 12:01 UTC | @Kalininskiytyt/32553 · this entry18 Aug 2026, 12:05 UTC | 1.00 | 4 minutes |
| @Voroshilovskiytyt/3606522 Aug 2026, 11:03 UTC | @Kalininskiytyt/32654 · this entry22 Aug 2026, 12:02 UTC | 1.00 | 59 minutes |
| @Voroshilovskiytyt/3615926 Aug 2026, 09:56 UTC | @Kalininskiytyt/32754 · this entry26 Aug 2026, 09:56 UTC | 1.00 | under a minute |
| @Voroshilovskiytyt/379695 Nov 2026, 10:02 UTC | @Kalininskiytyt/34330 · this entry6 Nov 2026, 08:00 UTC | 1.00 | 22 hours |
| @Kalininskiytyt/34423 · this entry9 Nov 2026, 17:18 UTC | @Voroshilovskiytyt/381189 Nov 2026, 17:18 UTC | 1.00 | under a minute |
| @Kalininskiytyt/32682 · this entry23 Aug 2026, 13:29 UTC | @Proletarskiytyt/2674923 Aug 2026, 13:29 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Voroshilovskiytyt | 41 (8/8 hand-verifiable sample passed) | 0.99 | under a minute | @Voroshilovskiytyt (29–12) |
| @Proletarskiytyt | 33 (8/8 hand-verifiable sample passed) | 0.97 | under a minute | this entry (26–7) |
| @Kiyevskiytyt | 30 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @Kiyevskiytyt (21–9) |
| @Kuybyshevskiy | 27 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @Kuybyshevskiy (22–5) |
| @Budonnovskiy | 28 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @Budonnovskiy (21–7) |
| @Leninskiytyt | 26 (8/8 hand-verifiable sample passed) | 0.98 | under a minute | this entry (15–11) |
| @Kirovskiytyt | 22 (8/8 hand-verifiable sample passed) | 0.97 | under a minute | @Kirovskiytyt (14–8) |
| @Petrovskiytyt | 17 (8/8 hand-verifiable sample passed) | 0.97 | under a minute | @Petrovskiytyt (14–3) |
| @itsdonetsk | 16 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @itsdonetsk (15–1) |
| @itssdonetsk | 7 (7/7 hand-verifiable sample passed) | 0.99 | 80 minutes | this entry (6–1) |
| @chpdn | 5 (5/5 hand-verifiable sample passed) | 0.95 | 4.6 hours | this entry (3–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 142 of the 142 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 397 comparable posts for this entry, running 6 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 07:14 | 20,159 | +4 |
| 12 Nov 2026, 01:08 | 20,155 | +53 |
| 10 Nov 2026, 02:00 | 20,102 | +12 |
| 8 Nov 2026, 16:39 | 20,090 | +8 |
| 7 Nov 2026, 13:25 | 20,082 | +11 |
| 6 Nov 2026, 16:50 | 20,071 | +17 |
| 5 Nov 2026, 17:44 | 20,054 | +25 |
| 4 Nov 2026, 15:09 | 20,029 | +8 |
| 3 Nov 2026, 12:16 | 20,021 | +5 |
| 2 Nov 2026, 12:19 | 20,016 | +7 |
| 1 Nov 2026, 08:46 | 20,009 | -2 |
| 31 Oct 2026, 07:31 | 20,011 | +4 |
| 30 Oct 2026, 04:20 | 20,007 | +1 |
| 29 Oct 2026, 06:01 | 20,006 | +1 |
| 28 Oct 2026, 05:57 | 20,005 | +13 |
| 27 Oct 2026, 06:55 | 19,992 | +1 |
| 26 Oct 2026, 03:16 | 19,991 | +11 |
| 24 Oct 2026, 04:20 | 19,980 | -2 |
| 23 Oct 2026, 07:10 | 19,982 | +1 |
| 22 Oct 2026, 03:51 | 19,981 | first reading |
661 posts held, back to 6 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 85 pages 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. It is computed over the 258 of 268 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 661 (6 August 2026 – 16 November 2026) |
| Views total | 745,500 |
| Reactions total | 3,612 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 04:30 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.
Lifetime counters from Telegram’s own channel header, read 17 November 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.
Measured directly from 102 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.
9,469 reactions across 623 posts, in 59 distinct kinds. The most used accounts for 16.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,576 | 16.6% | |
| 🤬 | 1,553 | 16.4% | |
| 👎 | 1,114 | 11.8% | |
| 👍 | 1,044 | 11.0% | |
| 🙏 | 525 | 5.54% | |
| 🤡 | 519 | 5.48% | |
| 😱 | 517 | 5.46% | |
| 😢 | 474 | 5.01% | |
| 😁 | 348 | 3.68% | |
| 💯 | 229 | 2.42% | |
| 🤣 | 220 | 2.32% | |
| 🤮 | 220 | 2.32% | |
| 🤯 | 151 | 1.59% | |
| 💩 | 141 | 1.49% | |
| 🥰 | 96 | 1.01% | |
| 😡 | 71 | 0.75% | |
| 🖕 | 68 | 0.718% | |
| 🔥 | 63 | 0.665% | |
| 😭 | 61 | 0.644% | |
| 😨 | 41 | 0.433% | |
| 39 further kinds | 438 | 4.63% |
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 634 of the 661 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 9,469 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 661 most recent posts we hold, published 6 August 2026 to 16 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: 32 of 268 posts held from the last 30 days (11.9%) 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).
Звёздное небо над Донецком Калининский | Предложить новость
❤23🤩2😁1
Нам пишут: "Состояние окон в подъезде по адресу ул. Антипова, 4 (2-й подъезд)." Калининский | Предложить новость
❤4🤯1
Нам пишут: "У входа в подъезд ул. Нижнеудинская, 14 провалился канализационный люк, что является травмаопасным и грозит засором." Калининский | Предложить новость
🤬4❤1😱1
Директор "Донецкэнерго" Павляк рассказал о ситуации с электроснабжением в ДНР "По текущей ситуации 428 000 абонентов обесточено, из них аварийно связано с остановкой блока 284 000 абонентов. Помимо того, что имеется ещё дефицит мощности, введено у нас график ГВО на 95 МВт. Под эти 95 МВт попадает 144 000 бытовых абонентов. Ожидаем пуск блока к 00:00 и готовы будем запитывать потребителей Донецка, Мариуполя, Новоазо…
🤡19👎2
Нам пишут: "Ул. Краснофлотская, 88 с начала отопительного сезона, отопление было три дня. Зато платёжка пришла как положено." Калининский | Предложить новость
💯2❤1🤬1😁1
❗️АНГЛИЙСКИЙ ЯЗЫК Для начальной школы: ✅Научим читать в сжатые сроки ✅в играх отрабатываем грамматику и изучаемые слова Для ребят постарше: ✅доходчиво объясняем грамматику, ✅каждый урок учим новые слова, ✅тренируем навыки чтения, говорения, аудирования. ✅По запросу -подготовка к ОГЭ,ЕГЭ 80-90% занятия ведется на английском ❗️РЕПЕТИТОР ПО МАТЕМАТИКЕ И ФИЗИКЕ 5-11 классы, подготовка к ОГЭ и ЕГЭ ❗️ЛОГОПЕД…
❤3
Люди жалуются, что на бульваре Шахтостроителей водитель перекрывает тротуар и ездит по газону во время выгрузки товара в ПВЗ Калининский | Предложить новость
🤬13
Момент ДТП на пр. Красногвардейском Калининский | Предложить новость
🙈3🤬1
Момент ДТП с участием машины скорой помощи на пр. Мира Калининский | Предложить новость
🙈6😱3👎2💊1
Ещё видео с места ДТП с участием трёх машин на пр. Красногвардейском Калининский | Предложить новость
❤1💊1🤬1
ДТП с участием трёх машин на пр. Красногвардейском Калининский | Предложить новость
💊1🤬1
В "Фениксе" рассказали о ситуации со связью в ДНР "В ДНР продолжаются восстановительные работы на энергосистеме, повреждённой атаками. Узловые объекты связи переведены на резервные источники питания – это позволяет обеспечивать абонентов базовыми услугами. Сейчас частично обесточены Макеевка, Донецк, Горловка, Докучаевск, Дебальцево, Мариуполь, Снежное, Енакиево, Шахтёрск и Ясиноватая. Оператор подвозит топливо к г…
🙏4🤷♀1
Showing the 12 most recent of 661 posts we hold for @Kalininskiytyt. 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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 29 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 18 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“Калининский Тут | Донецк” (@Kalininskiytyt), 20,159 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/Kalininskiytyt.
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.