Telegram RegisterThe public register of Telegram
Telegram profile photo for Магадан. ЧП

Channel

Магадан. ЧП

@magadanCHP

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

16,469subscribers

+79 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-1001656933729
TypeChannel
Username@magadanCHP
Created29 April 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live8 November 2026
Measurements held57
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/magadanCHP

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.

Growth

16,39016,49416,4427 August 2026 — 16,390 subscribers7 August 2026 — 16,390 subscribers8 August 2026 — 16,394 subscribers9 August 2026 — 16,405 subscribers10 August 2026 — 16,409 subscribers11 August 2026 — 16,414 subscribers12 August 2026 — 16,413 subscribers14 August 2026 — 16,411 subscribers16 August 2026 — 16,408 subscribers17 August 2026 — 16,412 subscribers18 August 2026 — 16,414 subscribers19 August 2026 — 16,415 subscribers20 August 2026 — 16,414 subscribers21 August 2026 — 16,404 subscribers23 August 2026 — 16,437 subscribers24 August 2026 — 16,443 subscribers25 August 2026 — 16,466 subscribers26 August 2026 — 16,463 subscribers27 August 2026 — 16,462 subscribers28 August 2026 — 16,465 subscribers29 August 2026 — 16,467 subscribers30 August 2026 — 16,472 subscribers31 August 2026 — 16,475 subscribers1 September 2026 — 16,470 subscribers4 September 2026 — 16,457 subscribers7 September 2026 — 16,443 subscribers10 September 2026 — 16,442 subscribers12 September 2026 — 16,443 subscribers14 September 2026 — 16,447 subscribers15 September 2026 — 16,449 subscribers17 September 2026 — 16,448 subscribers28 September 2026 — 16,446 subscribers5 October 2026 — 16,423 subscribers9 October 2026 — 16,445 subscribers13 October 2026 — 16,461 subscribers14 October 2026 — 16,474 subscribers15 October 2026 — 16,478 subscribers17 October 2026 — 16,484 subscribers18 October 2026 — 16,486 subscribers20 October 2026 — 16,489 subscribers21 October 2026 — 16,488 subscribers22 October 2026 — 16,491 subscribers23 October 2026 — 16,493 subscribers24 October 2026 — 16,494 subscribers24 October 2026 — 16,484 subscribers25 October 2026 — 16,485 subscribers28 October 2026 — 16,484 subscribers29 October 2026 — 16,490 subscribers30 October 2026 — 16,484 subscribers31 October 2026 — 16,470 subscribers1 November 2026 — 16,464 subscribers2 November 2026 — 16,459 subscribers2 November 2026 — 16,465 subscribers5 November 2026 — 16,471 subscribers6 November 2026 — 16,473 subscribers7 November 2026 — 16,476 subscribers8 November 2026 — 16,469 subscribers16,4697 August 20268 November 2026
57 measurements spanning 93 days, net +79. 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 16,374–16,510 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 57
Measured (UTC)SubscribersChange
8 Nov 2026, 10:1816,469-7
7 Nov 2026, 08:0516,476+3
6 Nov 2026, 08:4916,473+2
5 Nov 2026, 07:0616,471+6
2 Nov 2026, 23:5516,465+6
2 Nov 2026, 03:0716,459-5
1 Nov 2026, 04:3916,464-6
31 Oct 2026, 05:4816,470-14
30 Oct 2026, 04:5816,484-6
29 Oct 2026, 05:0116,490+6
28 Oct 2026, 00:0116,484-1
25 Oct 2026, 19:3016,485+1
24 Oct 2026, 21:5616,484-10
24 Oct 2026, 01:0816,494+1
23 Oct 2026, 04:3716,493+2
22 Oct 2026, 06:4716,491+3
21 Oct 2026, 00:0716,488-1
20 Oct 2026, 01:3816,489+3
18 Oct 2026, 23:2916,486+2
17 Oct 2026, 22:3916,484first reading

Engagement

89 posts held, back to 3 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 65 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.5%
avg views ÷ 16,469 subscribers
Avg views / post
3,040
25 posts measured
Reaction rate
0.945%
reactions ÷ views · ER floor
Posts in window
25
of 89 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 6 November 2026
Posts held89 (3 August 2026 – 6 November 2026)
Views total76,120
Reactions total719
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 04: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

Video runtime
20m 09s
Average length
30s

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

3,356 reactions across 89 posts, in 40 distinct kinds. The most used accounts for 12.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣42712.7%
❤38811.6%
👍35910.7%
🙏2908.64%
🤬2647.87%
🙈2367.03%
😱1955.81%
🤯1735.15%
👀1674.98%
😡1414.20%
😢1283.81%
🔥792.35%
🤡661.97%
😁611.82%
😨611.82%
☃591.76%
🤔501.49%
💩290.864%
😭260.775%
🫡220.656%
20 further kinds1354.02%

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

Measured over the 89 most recent posts we hold, published 3 August 2026 to 6 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: 14 of 25 posts held from the last 30 days (56.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).

6 Nov 2026, 07:23 UTC≈2,270 views12 reactionsread 8 November 2026
Photo

❗️Из-за неисправности электросети загорелся частный дом в Магадане МЧС: ЧП произошло на ул. Широкой в 9:55. Возгорание началось в одной из комнат, пока хозяева спали. Проснувшись от запаха дыма, жильцы своевременно покинули помещение. К месту тушения прибыли пожарные и спасатели в количестве 32 человек и 8 ед. техники. Пожар ликвидирован на площади 15 кв. м, никто не пострадал. Предварительно, причиной мог стать ав…

😨5❤3💩1🤡1🤨1🙈1

6 Nov 2026, 06:29 UTC≈2,270 views13 reactionsread 8 November 2026
Photo

❗️Наблюдение за медведями в Магаданской области завершено до будущей весны. Как сообщили в правительстве региона, за прошедшую неделю охотоведам поступило одно сообщение о встрече с бурым хищником, но оно не подтвердилось. В связи с тем, что на Колыме установились стабильно низкие температуры и снежный покров, мониторинг продолжится в рамках постоянного рейда, подчеркнули в Госохотнадзоре. 📲 ЧП МАКС ⚠️ Предложка ЧП

🤣5🙏4👍2❤1🙈1

6 Nov 2026, 04:03 UTC≈2,390 views29 reactionsread 8 November 2026
Photo

❗️Новую остановку на Кольцевой, установленную специалистами ГЭЛУД на прошлой неделе, повредили неизвестные. Как сообщила мэр Магадана, следы повреждений были обнаружены вчера – по данному факту было подано заявление в полицию, ведется розыск вандалов. Лариса Поликанова напомнила, что в Магадане работает система «Безопасный город», установлено несколько сотен камер видеонаблюдения, которые позволяют отслеживать проти…

🤬24🙈3❤1😢1

6 Nov 2026, 02:36 UTC≈2,630 views122 reactionsread 8 November 2026
Photo

Магаданка пожаловалась в соцсетях на авто, которую припарковали прямо напротив детского садика. По мнению жительницы, имея машину с таким рисунком, владельцу стоит думать, где ее оставлять 🤔 📲 ЧП МАКС ⚠️ Прислать фото/видео в ЧП

🤣91👍8💯6🙈5❤3🤡3💩2🔥2

5 Nov 2026, 01:09 UTC≈2,930 views37 reactionsread 8 November 2026
Video

От подписчика: И куда так торопится? 😡 📲 ЧП МАКС ⚠️ Прислать фото/видео в ЧП

😡27🤡5💩2🙈2❤1

5 Nov 2026, 00:35 UTC≈2,930 views24 reactionsread 8 November 2026
Photo

❗️Теперь официально ГАИ: Вечером 4 ноября в районе 1807 км ФАД «Колыма» 58-летний водитель микроавтобуса «Тойота Региус» нарушил правила расположения т/с на проезжей части и столкнулся со встречной Хондой Фит, которую отбросило на двигающийся следом за «Тойотой» минивэн. В результате ДТП пострадали водитель и три пассажира микроавтобуса: женщина 1977 г.р. и двое мужчин 1964 года и 1980 годов рождения. По факту про…

😡13❤3🙈3🌚2😨2🤣1

4 Nov 2026, 21:50 UTC≈2,800 views43 reactionsread 8 November 2026
Video

❗️Момент вчерашнего ДТП с участием Тойоты Хайс за Аткой от подписчика. Очевидцы сообщают о нескольких пострадавших. 📲 ЧП МАКС ⚠️ Предложка ЧП

😱27🤯7🤡4❤2🌚1👀1🙏1

4 Nov 2026, 11:13 UTC≈2,890 views57 reactionsread 8 November 2026
Video

От подписчицы: Вчера на перекрестке Ленина и Пушкина водитель Nissan Patrol нагло подрезал меня с правой полосы, где разрешен поворот направо. Видимо, правила не для него и такие действия могли привести к ДТП 😡 📲 ЧП МАКС ⚠️ Прислать фото/видео в ЧП

🤬46👍4🤣2😡2💊1🤡1🙈1

4 Nov 2026, 10:52 UTC≈2,820 views18 reactionsread 8 November 2026
Photo

❗ГАИ: Вечером 4 ноября в районе 1378 км федеральной автодороги «Колыма», 50-летний водитель тягача Урал с полуприцепом не справился с управлением и съехал с дороги с последующим опрокидыванием. В результате происшествия водитель, находившийся в состоянии алкогольного опьянения, получил травмы. 📲 ЧП МАКС

😡11😱3❤1💩1🤣1🙈1

4 Nov 2026, 09:47 UTC≈2,830 views19 reactionsread 8 November 2026
Photo

❗Спасатели привлекались для ликвидации последствий ДТП МЧС: На 1379 км ФАД Колыма в районе поселка Холодный водитель автомобиля марки Урал тягач не справился с управлением и совершил съезд в кювет. Пожарные ПСЧ-4 г. Сусумана с помощью гидравлическиого инструмента деблокировали застрявшего в кабине машины водителя и передали сотрудникам скорой помощи. 📲 ЧП МАКС

🙏10👀2🤣2🤬2🤯2🙈1

4 Nov 2026, 09:05 UTC≈2,950 views33 reactionsread 8 November 2026
Video

От подписчика: ❗Серьезное ДТП за Аткой – микроавтобус выехал на встречку и столкнулся с легковушкой. Предварительно, есть несколько пострадавших. Ждем официальной информации 📲 ЧП МАКС ⚠️ Прислать новость

🙏16🤯10👀4❤1🌚1🤣1

3 Nov 2026, 09:05 UTC≈3,000 views12 reactionsread 6 November 2026
Photo

❗️Теперь официально МЧС: Утром 3 ноября в Магадане загорелось строение, состоящее из трех контейнеров. Огнеборцев вызвал хозяин постройки. К месту тушения прибыли 13 пожарных и спасателей на 3 единицах техники. Очаг возгорания находился в одном из трех отсеков, где располагался производственный цех. Благодаря оперативным действиям огнеборцев в короткие сроки удалось ликвидировать возгорание на 36 квадратах, не доп…

❤7😢3👀1🤡1

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

@magadanCHP 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
25 August 2026
Most recent edit
25 August 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 3 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.

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.

Appears in Telegram’s recommendations for other channels

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.

МАГАДАН LIVE
@magadan_live1 · 41,478
Telegram ranks this channel #4 of 30 here — alongside 29 others — read 17 September 2026
Богдан Булычёв🇷🇺
@bogdee · 21,619
Telegram ranks this channel #38 of 84 here — alongside 83 others — read 22 September 2026
Смотровая вышка
@magadan_magadan · 28,122
Telegram ranks this channel #45 of 94 here — alongside 93 others — read 17 September 2026

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.

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

“Магадан. ЧП” (@magadanCHP), 16,469 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/magadanCHP.

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.