Channel
@krukovoo
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
917subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001576173629 |
|---|---|
| Type | Channel |
| Username | @krukovoo |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/krukovoo |
Local community — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
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 word for word on 3 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 |
|---|---|---|---|
| @krukovoo/17981 · this entry7 Aug 2026, 06:58 UTC | @matushkinor/82147 Aug 2026, 06:58 UTC | 1.00 | under a minute |
| @matushkinor/82167 Aug 2026, 06:58 UTC | @krukovoo/17983 · this entry7 Aug 2026, 06:58 UTC | 1.00 | under a minute |
| @matushkinor/82177 Aug 2026, 06:58 UTC | @krukovoo/17984 · this entry7 Aug 2026, 06:58 UTC | 1.00 | under a minute |
| @krukovoo/17988 · this entry7 Aug 2026, 06:59 UTC | @matushkinor/82217 Aug 2026, 06:59 UTC | 1.00 | under a minute |
| @matushkinor/82227 Aug 2026, 06:59 UTC | @krukovoo/17989 · this entry7 Aug 2026, 06:59 UTC | 1.00 | under a minute |
| @krukovoo/17981 · this entry7 Aug 2026, 06:58 UTC | @silinoo/91377 Aug 2026, 06:58 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @matushkinor | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (5–0) |
| @silinoo | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4–1) |
| @savelkii | 5 (5/5 hand-verifiable sample passed) | 1.00 | under a minute | @savelkii (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. 4 of the 4 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 13 comparable posts for this entry, running 6 August 2026 to 7 August 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.
Across the whole group of 4, the earliest publisher we hold is @savelkii. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 18:40 | 917 | -1 |
| 6 Sept 2026, 02:15 | 918 | +4 |
| 20 Aug 2026, 13:35 | 914 | -1 |
| 14 Aug 2026, 08:16 | 915 | +1 |
| 7 Aug 2026, 10:02 | 914 | no change |
| 7 Aug 2026, 08:48 | 914 | first reading |
16 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Сегодня ожидается такой же жаркий день, как и вчера. Будьте осторожны, пейте много воды и носите легкую одежду. Даже если вы в тенечке, может случиться тепловой удар. Чтобы хоть немножко остудить день, добавим в ленту водоёмов 😁 #любимый_зеленоград #Тг @krukovoo
Обвиняемого в убийстве в Андреевке отправили в СИЗО 49-летнего местного жителя заключили под стражу до 3 октября. Его обвиняют в убийстве знакомого и покушении на убийство второго человека у дома на Староандреевской улице. По данным следствия, мужчина признал вину и раскаялся. | #ЗелАО, #мoс #Тг #мcк
Москва завтра уйдёт под воду На 1 кв. м. ожидается до 18 литров дождевой воды, сообщили в Гидрометцентре. #ЗелАО, #мoс #Тг #мcк
5 минут назад в 15 районе. Задержали наркомана . Зеленоград #Тг #мcк
Вчера вечером произошло ДТП на парке Победы: столкнулись рейсовый автобус и легковой автомобиль. В результате у одной пассажирки перелом плеча Присылайте новости — | | #ЗелАО, #мoс #Тг #мcк
Строительство первых жилых домов в городе-спутнике, 1961 год. Фото из архива Музея Зеленограда Инфопортал Зеленограда в соцсетях Зеленоград #Тг #мcк
Узнали себя? | #ЗелАО, #мoс #Тг #мcк
Вот так вот люди переходят перебегают дорогу в 15-м районе у поликлиники До перехода два шага… Присылайте новости — | | #ЗелАО, #мoс #Тг #мcк
Что с погодой в Крюково? Одевайтесь по погоде, берегите себя! Запоминающегося дня, соседи! #погоданарайоне #Тг @krukovoo
Зима на площади Юности #нашаистория_Зеленоград #Тг @krukovoo
Дождливый денек возле станции «Крюково». Фото сделано в 2008-м. Ставьте лайк, если помните времена, когда электрички были еще зелеными 😎 #Тг @krukovoo
Любители вкусно поесть, внимание! Регулярное употребление бургеров, пиццы, газировки и другой ультрапереработанной еды может негативно влиять не только на физическое здоровье, но и на эмоциональное состояние, предупреждают эксперты. Исследования показывают, что у людей, которые часто питаются такой пищей, чаще возникают тревожность, апатия и симптомы депрессии. Так что уж лучше навернуть салатик. #Тг @krukovoo
Showing the 12 most recent of 16 posts we hold for @krukovoo. 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.
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 3 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Крюково” (@krukovoo), 917 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/krukovoo.
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.