Telegram RegisterThe public register of Telegram
Telegram profile photo for HABnews27

Channel

HABnews27

@HABnews27

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

4,332subscribers

-5,097 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002582541526
TypeChannel
Username@HABnews27
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/HABnews27

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@khabarray/2752727 Aug 2026, 04:05 UTC@HABnews27/2321 · this entry28 Aug 2026, 11:17 UTC0.9331 hours
@khabarray/2703610 Aug 2026, 02:30 UTC@HABnews27/2245 · this entry11 Aug 2026, 11:14 UTC0.9333 hours
@khabarray/2745625 Aug 2026, 01:15 UTC@HABnews27/2312 · this entry26 Aug 2026, 07:06 UTC0.9230 hours
@khabarray/269707 Aug 2026, 04:04 UTC@HABnews27/2229 · this entry8 Aug 2026, 10:51 UTC0.9231 hours
@khabarray/269366 Aug 2026, 01:19 UTC@HABnews27/2225 · this entry7 Aug 2026, 10:52 UTC0.9134 hours
@khabarray/270108 Aug 2026, 23:04 UTC@HABnews27/2239 · this entry10 Aug 2026, 02:32 UTC0.9127 hours
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
@khabarray8 (8/8 hand-verifiable sample passed)0.9132 hours@khabarray (8–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. 8 of the 8 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 105 comparable posts for this entry, running 1 August 2026 to 28 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.

  • 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).

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

Growth

4,3329,4296,880.56 August 2026 — 9,429 subscribers6 August 2026 — 9,428 subscribers9 August 2026 — 9,357 subscribers12 August 2026 — 9,316 subscribers16 August 2026 — 9,280 subscribers19 August 2026 — 8,838 subscribers23 August 2026 — 8,831 subscribers26 August 2026 — 8,653 subscribers28 August 2026 — 7,410 subscribers1 September 2026 — 7,060 subscribers4 September 2026 — 6,954 subscribers9 September 2026 — 6,767 subscribers13 September 2026 — 6,590 subscribers17 September 2026 — 6,431 subscribers26 September 2026 — 5,652 subscribers5 October 2026 — 5,608 subscribers11 October 2026 — 8,670 subscribers14 October 2026 — 8,650 subscribers17 October 2026 — 8,646 subscribers21 October 2026 — 8,643 subscribers23 October 2026 — 6,036 subscribers26 October 2026 — 6,030 subscribers29 October 2026 — 5,452 subscribers1 November 2026 — 5,238 subscribers4 November 2026 — 5,173 subscribers7 November 2026 — 4,636 subscribers10 November 2026 — 4,430 subscribers15 November 2026 — 4,332 subscribers6 August 202615 November 2026
28 measurements spanning 101 days, net -5,097. 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 3,567–10,194 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
15 Nov 2026, 09:104,332-98
10 Nov 2026, 12:004,430-206
7 Nov 2026, 09:404,636-537
4 Nov 2026, 12:505,173-65
1 Nov 2026, 12:585,238-214
29 Oct 2026, 06:095,452-578
26 Oct 2026, 13:576,030-6
23 Oct 2026, 23:406,036-2,607
21 Oct 2026, 01:068,643-3
17 Oct 2026, 22:008,646-4
14 Oct 2026, 22:508,650-20
11 Oct 2026, 18:428,670+3,062
5 Oct 2026, 01:395,608-44
26 Sept 2026, 09:575,652-779
17 Sept 2026, 14:016,431-159
13 Sept 2026, 12:376,590-177
9 Sept 2026, 09:006,767-187
4 Sept 2026, 10:176,954-106
1 Sept 2026, 06:297,060-350
28 Aug 2026, 20:437,410first reading

Engagement

112 posts held, back to 1 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 29 pages 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 112 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
24m 45s
Average length
40s

Measured directly from 37 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.

Recent posts

28 Aug 2026, 11:17 UTC1 viewsread 28 August 2026
Video

История с неисправными лифтами продолжается на Павла Морозова, 113 в Хабаровске. Пишет наш подписчик: "По-прежнему лифты регулярно не работают, просто стоят на каком-то одном этаже и не реагируют на вызов. Но и когда они условно работают, вызвать лифт на своем этаже невозможно: они проезжают мимо без остановки. И подняться с первого этажа на свой тоже проблема: лифты едут по другим этажам, иногда поднимаются на посл…

28 Aug 2026, 07:00 UTC1 viewsread 28 August 2026
Photo

Восточное шоссе в Хабаровске по-прежнему полностью перекрыто с 25 августа до воскресенья, 30 августа, из-за размыва моста через Гнилую падь. Сейчас там идут работы, в том числе, по данным мэрии, по углублению и зачистке русла.

28 Aug 2026, 03:01 UTC1 viewsread 28 August 2026
Photo

Утонули два рыбака Вчера в 7 км от села Солонцы (Ульчский район) во время рыбалки выпал из катера и утонул 43-летний мужчина. Тело не найдено, ведутся поиски. Ещё один смертельный случай во время рыбалки произошёл накануне в Николаевске-на-Амуре. В Амуре у ТЭЦ утонул 38-летний рыбак. По данным МЧС, ведутся его поиски.

27 Aug 2026, 22:39 UTC2 viewsread 28 August 2026
Video

🚒🔥📣 Сильный пожар произошел вчера вечером в Хабаровске в частном доме на Краснореченской в районе поворота на Флегонтова. Предварительно есть пострадавшие. Обновление. По информации МЧС, на улице Докучаева горело одноэтажное нежилое деревянное строение на площади 30 квадратных метров. Пострадавших нет, причины пожара выясняются.

27 Aug 2026, 11:04 UTC2 viewsread 28 August 2026
Video

Стоят дольше, чем едут В Хабаровске, городе заборов и светофоров, которые установлены на каждом перекрестке, жители отмечают, что еще и стоять на них приходится дольше, чем ехать. Например, на Краснореченской в районе МЖК зеленый свет горит 45 секунд, зато красный – 64. В итоге из-за настройки светофоров (и не только в районе МЖК) в городе стоят пробки.

27 Aug 2026, 06:52 UTC2 viewsread 28 August 2026
Photo

В лобовом ДТП получили травмы 5 человек Вчера в 23 часа в Вяземском районе на 154 км автодороги А-370 "Уссури" 33-летняя водитель Nissan Presage выехала на встречную полосу для обгона и врезалась в Toyota Carina. По данным Госавтоинспекции, травмы получили пять человек, включая 2-летнего ребенка. Все доставлены скорой помощью в больницу.

27 Aug 2026, 03:09 UTC2 viewsread 28 August 2026
Video

Из-за ливневки, которая не справляется со своей задачей, топит пересечение улицы Шкотова и проспекта 60 лет Октября в Хабаровске.

26 Aug 2026, 22:38 UTC2 viewsread 28 August 2026
Video

На ужасное состояние железнодорожных переездов на Суворова в Хабаровске жалуются горожане. "Адская дорога в город", говорит очевидец.

26 Aug 2026, 10:54 UTC3 viewsread 28 August 2026
Photo

Рыбак сорвался со склона и сломал ногу Вчера у поселка Пивань (Комсомольский район) на правый берег Амура на рыбалку отправились пятеро приятелей. Несмотря на то, что берег затоплен, планы дойти до излюбленного места менять не стали и двинулись по крутому скалистому склону. В результате 73-летний пенсионер сорвался и сломал ногу. Его друзья обратились в МЧС, спасатели забрали пострадавшего, перенесли на носилках к …

26 Aug 2026, 07:06 UTC2 viewsread 28 August 2026
Photo

От лица умершего "продала" себе три "Мерседеса" на 35 миллионов В Хабаровске 43-летняя горожанка переоформила на себя автопарк умершего сожителя. На три автомобиля, которые должны были перейти его шести наследникам, она составила договоры купли-продажи. Продавцом в них выступил уже умерший владелец, за которого она расписалась. После этого хабаровчанка оформила "Мерседесы" стоимостью более 35 миллионов рублей на себ…

26 Aug 2026, 02:39 UTC3 viewsread 28 August 2026
Video

В затопленном дворе на Демьяна Бедного в Хабаровске купаются дети. Плавать там можно было почти все лето: затопило его далеко не в первый раз.

25 Aug 2026, 23:01 UTC3 viewsread 28 August 2026
Photo

16-летний пассажир получил травмы в ДТП, водитель сбежал В посёлке Солонцовый (район имени Лазо) на улице Школьной Nissan Gloria врезался в железобетонную опору. По данным Госавтоинспекции, водитель сбежал с места аварии, его личность устанавливается. На заднем сидении ехали трое подростков, один из них, сидевший в центре (16 лет) получил травмы. Сначала его доставили в районную больницу в Переяславке, а затем пере…

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

Forward network

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.

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

“HABnews27” (@HABnews27), 4,332 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/HABnews27.

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.