Telegram RegisterThe public register of Telegram
Telegram profile photo for Ховрино 📍 Головинский 📍 Левобережный

Channel

Ховрино 📍 Головинский 📍 Левобережный

@hovrino_golovinka

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

12,659subscribers

+3,586 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001759955431
TypeChannel
Username@hovrino_golovinka
Description📍Официальный паблик районов Ховрино, Головинский и Левобережный в САО, г. Москва. instagram.com/hovrino_golovinka/ 📍Соседи: @degunino_dmitrovka 🇷🇺 Подписывайтесь! 👨‍👩‍👧‍👦 👉🏻 Реклама: @weblabel
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held47
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/hovrino_golovinka

Topic

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 11 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@hovrino_golovinka/2077 · this entry15 Aug 2026, 08:15 UTC@golovinsky/2658619 Aug 2026, 16:19 UTC1.004 days
@hovrino_golovinka/2081 · this entry20 Aug 2026, 18:33 UTC@golovinsky/2659921 Aug 2026, 05:18 UTC1.0011 hours
@hovrino_golovinka/2082 · this entry22 Aug 2026, 10:25 UTC@golovinsky/2660724 Aug 2026, 11:47 UTC1.002 days
@hovrino_golovinka/2080 · this entry19 Aug 2026, 14:34 UTC@golovinsky/2659020 Aug 2026, 07:03 UTC0.9716 hours
@hovrino_golovinka/2073 · this entry10 Aug 2026, 05:21 UTC@golovinsky/2656412 Aug 2026, 12:01 UTC0.952 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@golovinsky5 (5/5 hand-verifiable sample passed)0.982 daysthis entry (5–0)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 33 comparable posts for this entry, running 14 July 2026 to 17 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 4 channels, the one whose matching posts we hold earliest is @koptevo_ryadom. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 18 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.

Channels linked by matching posts

This channel is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

8,99813,09811,0487 August 2026 — 9,073 subscribers8 August 2026 — 9,063 subscribers10 August 2026 — 9,012 subscribers13 August 2026 — 9,471 subscribers17 August 2026 — 9,381 subscribers20 August 2026 — 9,089 subscribers23 August 2026 — 9,046 subscribers26 August 2026 — 8,998 subscribers28 August 2026 — 9,488 subscribers31 August 2026 — 9,435 subscribers4 September 2026 — 9,876 subscribers10 September 2026 — 9,713 subscribers13 September 2026 — 9,855 subscribers18 September 2026 — 9,771 subscribers27 September 2026 — 10,683 subscribers4 October 2026 — 10,367 subscribers9 October 2026 — 10,314 subscribers13 October 2026 — 10,628 subscribers14 October 2026 — 10,600 subscribers15 October 2026 — 10,570 subscribers16 October 2026 — 10,550 subscribers17 October 2026 — 10,529 subscribers18 October 2026 — 10,524 subscribers19 October 2026 — 10,504 subscribers20 October 2026 — 10,480 subscribers22 October 2026 — 10,767 subscribers23 October 2026 — 11,016 subscribers24 October 2026 — 10,939 subscribers25 October 2026 — 10,874 subscribers26 October 2026 — 10,823 subscribers26 October 2026 — 10,760 subscribers28 October 2026 — 10,696 subscribers29 October 2026 — 10,608 subscribers30 October 2026 — 10,559 subscribers31 October 2026 — 10,511 subscribers1 November 2026 — 10,468 subscribers2 November 2026 — 10,436 subscribers3 November 2026 — 13,098 subscribers4 November 2026 — 13,040 subscribers5 November 2026 — 12,993 subscribers6 November 2026 — 12,965 subscribers7 November 2026 — 12,933 subscribers8 November 2026 — 12,871 subscribers10 November 2026 — 12,741 subscribers11 November 2026 — 12,698 subscribers14 November 2026 — 12,764 subscribers17 November 2026 — 12,659 subscribers12,6597 August 202617 November 2026
47 measurements spanning 103 days, net +3,586. 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 8,383–13,713 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
17 Nov 2026, 22:5512,659-105
14 Nov 2026, 20:4712,764+66
11 Nov 2026, 22:4512,698-43
10 Nov 2026, 01:4012,741-130
8 Nov 2026, 19:3112,871-62
7 Nov 2026, 09:0012,933-32
6 Nov 2026, 11:3612,965-28
5 Nov 2026, 11:3512,993-47
4 Nov 2026, 08:0613,040-58
3 Nov 2026, 10:4913,098+2,662
2 Nov 2026, 11:1910,436-32
1 Nov 2026, 10:4610,468-43
31 Oct 2026, 08:0610,511-48
30 Oct 2026, 05:3810,559-49
29 Oct 2026, 03:3910,608-88
28 Oct 2026, 02:1910,696-64
26 Oct 2026, 22:4710,760-63
26 Oct 2026, 01:2710,823-51
25 Oct 2026, 00:5910,874-65
24 Oct 2026, 00:1110,939first reading

Engagement

61 posts held, back to 13 July 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 64 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
69.4%
avg views ÷ 12,659 subscribers
Avg views / post
8,790
15 posts measured
Reaction rate
4.15%
reactions ÷ views · ER floor
Posts in window
15
of 61 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 17 November 2026
Posts held61 (13 July 2026 – 17 November 2026)
Views total131,800
Reactions total5,476
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 10:38 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
≈1,730
Videos
≈256
Links
≈356

Lifetime counters from Telegram’s own channel header, read 18 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.

Video runtime
3m 02s
Average length
15s

Measured directly from 12 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

23,335 reactions across 61 posts, in 23 distinct kinds. The most used accounts for 26.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎6,28126.9%
❤5,14522.0%
👍4,60619.7%
🔥1,4136.06%
🤬1,1024.72%
🎉7783.33%
😢4081.75%
💯4051.74%
😁4001.71%
🤩3791.62%
🥰3671.57%
👏3591.54%
❤‍🔥3551.52%
😡2891.24%
😍2851.22%
🍌1760.754%
🥱1660.711%
💔1650.707%
😈1580.677%
😱900.386%
3 further kinds80.034%

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

Measured over the 61 most recent posts we hold, published 13 July 2026 to 17 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.

Recent posts

Telegram’s own ‘edited’ marker: 6 of 15 posts held from the last 30 days (40.0%) 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).

17 Nov 2026, 05:49 UTC≈3,350 views338 reactionsread 18 November 2026
Video

Три человека пострадали в аварии с рейсовым автобусом, который въехал в столб на Коровинском шоссе. Вчера водитель автобуса не справился с управлением и въехал в столб на Коровинском шоссе. ДТП произошло с рейсовым автобусом, следовавшим по маршруту "Речной вокзал - Грачевская".

👎232😢78🤬26😱2

15 Nov 2026, 06:31 UTC≈6,820 views305 reactionsread 18 November 2026
Photo

Полиция задержала курьера мошенников у пенсионерки из Левобережного района. Более 6,7 млн рублей ушли к аферистам. Около месяца с ней общались мошенники, внушая, что её счета под блокировкой; деньги она вручила у дома на Фестивальной улице. Одного из курьеров задержали: ему 32 года, живёт в Ногинске. По данным издания, именно он получил 930 тысяч рублей и отдал их сообщнице. Уголовное дело уже возбуждено. #левобер…

👎238😱46🤬19❤1🤯1

11 Nov 2026, 18:17 UTC≈7,220 views424 reactionsread 18 November 2026
Video

Сегодня была проверка безбилетников на конечной автобусов у метро «Ховрино», рассказывают соседи. #ховрино

👍197🔥65❤‍🔥49🥰46👎21😢17❤11😁10

9 Nov 2026, 12:32 UTC≈8,060 views393 reactionsread 18 November 2026
Photo

🍂 Усадьба Михалково — живописный уголок старой Москвы.

❤245👍34💯32🥰24🎉21🤩20🔥9😁8

7 Nov 2026, 07:20 UTC≈6,970 views416 reactionsread 18 November 2026
Video

Рассвет в Ховрино❤️ Автор видео: Sk Anton

❤219🥰41🔥34👍30🎉29🤩29😍20😁12

5 Nov 2026, 05:40 UTC≈8,860 views388 reactionsread 18 November 2026
Photo

Актуальное фото преображения усадьбы Грачёвка. Работы ведутся с особым вниманием к сохранению исторического облика, чтобы вернуть памятнику его былое великолепие #ховрино #головинский

👍218❤90💯67🔥7😁6

3 Nov 2026, 10:05 UTC≈9,850 views301 reactionsread 18 November 2026
Photo

🚋 Движение электричек Ленинградского направления изменилось со 2 ноября. Модернизация участка Останкино — Зеленоград-Крюково пройдёт до 26 ноября. Часть поездов до Клина отменят полностью, часть пойдёт укороченным маршрутом. Поезда №6792 и №6791 на участке Тверь — Лихославль — Тверь курсировать не будут. #ховрино

👎214🤬34😡28😢25

31 Oct 2026, 05:57 UTC≈10,200 views323 reactionsread 18 November 2026
Photo

Октябрь в Грачёвском парке 😍 #ховрино

❤200🔥35👍26🤩25👏18🎉11😍8

29 Oct 2026, 08:23 UTC≈9,280 views353 reactionsread 18 November 2026
Photo

Минутка ностальгии. Автобус 65 маршрута пробирается по бульвару, 1968 год. #ховрино

❤229🎉22👍20🔥19👏14🤩14💯12❤‍🔥9

28 Oct 2026, 05:58 UTC≈11,800 views353 reactionsread 18 November 2026
Photo

⚠️ Соседи, напоминаем, что электробус 403 переименовался в м43. Сам маршрут остался тем же. Только электробусы теперь должны начать ходить чаще. #ховрино #головинский

👍216❤38🔥28👏17🎉13😍10💯9❤‍🔥8

26 Oct 2026, 19:20 UTC≈9,870 views358 reactionsread 18 November 2026
Photo

Северный речной вокзал внутри ❤️ Во время грандиозной реставрации, которая завершилась в 2020 году, реставраторы работали с историческими эскизами и архивными фотографиями. Теперь можно оценить всё великолепие оригинальных интерьеров Северного речного вокзала. Для их отделки использовали разные виды мрамора, естественный камень и бронзу. Центральный вестибюль. Просторное помещение украшают массивные колонны с капит…

❤214🔥31👍26👏22🎉18🥰10💯9❤‍🔥8

25 Oct 2026, 15:57 UTC≈10,300 views331 reactionsread 18 November 2026
Video

От соседей: Вот такое санитарное состояние перехода через жд-пути на станцию Ховрино. #ховрино #сао

👎230🤬53😢25😡23

Showing the 12 most recent of 61 posts we hold for @hovrino_golovinka. 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

@hovrino_golovinka edited 1 post 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
12 November 2026
Most recent edit
12 November 2026

Mentions

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.

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

“Ховрино 📍 Головинский 📍 Левобережный” (@hovrino_golovinka), 12,659 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/hovrino_golovinka.

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.