Telegram RegisterThe public register of Telegram
Telegram profile photo for Магнитогорск | Культура | Наука

Channel

Магнитогорск | Культура | Наука

@Magnitogorsk_nauch

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry

6,670subscribers

-11 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-1001415820904
TypeChannel
Username@Magnitogorsk_nauch
CreatedBetween 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/Magnitogorsk_nauch

Topic

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 79% 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.

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 word for word on 4 other registered channels. They sit inside a group of 7 channels that share the same post bodies 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Magnitogorsk_crazy/108612 Nov 2025, 14:21 UTC@Magnitogorsk_nauch/1530 · this entry12 Nov 2025, 20:14 UTC1.005.9 hours
@Magnitogorsk_nauch/1532 · this entry14 Nov 2025, 14:42 UTC@Magnitogorsk_crazy/109016 Nov 2025, 14:31 UTC1.0048 hours
@Magnitogorsk_crazy/109218 Nov 2025, 16:44 UTC@Magnitogorsk_nauch/1537 · this entry19 Nov 2025, 16:49 UTC1.0024 hours
@Magnitogorsk_nauch/1536 · this entry18 Nov 2025, 17:34 UTC@Magnitogorsk_crazy/109319 Nov 2025, 16:13 UTC1.0023 hours
@Magnitogorsk_crazy/109521 Nov 2025, 16:08 UTC@Magnitogorsk_nauch/1539 · this entry21 Nov 2025, 16:52 UTC1.0043 minutes
@Magnitogorsk_nauch/1542 · this entry24 Nov 2025, 14:59 UTC@Magnitogorsk_crazy/109925 Nov 2025, 16:44 UTC1.0026 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Magnitogorsk_crazy8 (8/8 hand-verifiable sample passed)1.0024 hourseven
@Magnitogorsk_gide8 (8/8 hand-verifiable sample passed)1.0048 hoursthis entry (53)
@Magnitogorsk_true7 (7/7 hand-verifiable sample passed)1.0028 hours@Magnitogorsk_true (70)
@Magnitogorsk_rage7 (7/7 hand-verifiable sample passed)1.0022 hours@Magnitogorsk_rage (70)

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 21 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 19 comparable posts for this entry, running 11 November 2025 to 29 November 2025. 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).

Across the whole group of 7, the earliest publisher we hold is @Magnitogorsk_true. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 6 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.

Growth

6,6676,6816,6746 August 2026 — 6,681 subscribers7 August 2026 — 6,680 subscribers10 August 2026 — 6,678 subscribers19 August 2026 — 6,675 subscribers23 August 2026 — 6,674 subscribers26 August 2026 — 6,676 subscribers29 August 2026 — 6,675 subscribers1 September 2026 — 6,674 subscribers3 September 2026 — 6,672 subscribers9 September 2026 — 6,667 subscribers13 September 2026 — 6,669 subscribers17 September 2026 — 6,670 subscribers6,6706 August 202617 September 2026
12 measurements spanning 41 days, net -11. 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 6,665–6,683 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 05:166,670+1
13 Sept 2026, 06:196,669+2
9 Sept 2026, 06:386,667-5
3 Sept 2026, 23:586,672-2
1 Sept 2026, 01:066,674-1
29 Aug 2026, 06:076,675-1
26 Aug 2026, 04:456,676+2
23 Aug 2026, 13:166,674-1
19 Aug 2026, 19:026,675-3
10 Aug 2026, 14:386,678-2
7 Aug 2026, 07:236,680-1
6 Aug 2026, 17:176,681first reading

Engagement

20 posts held, back to 11 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 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 20 posts for this entry, the most recent from 30 November 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Nov 2025, 15:06 UTC≈12,600 viewsread 20 August 2026
Photo

Канал временно не обслуживается, за рекламой обращаться к действующему сотруднику на других каналах @Oksana_rek

29 Nov 2025, 13:56 UTC≈12,100 viewsread 20 August 2026
Photo

Жителя Магнитогорска будут судить за пьяную езду на электросамокате Мужчину обвиняют в совершении преступления, предусмотренного ч. 1 ст. 264.1 УК РФ (управление другим механическим транспортным средством лицом, находящимся в состоянии опьянения, подвергнутым административному наказанию за управление транспортным средством в состоянии опьянения). Магнитогорца ранее лишили водительского удостоверения за управление тр

28 Nov 2025, 16:59 UTC≈12,100 viewsread 20 August 2026
Photo

Мошенники оформили на жителя Магнитогорска кредит без его ведома. По данному факту возбуждено уголовное дело по статье 159 УК РФ (мошенничество).

27 Nov 2025, 17:52 UTC≈12,100 viewsread 20 August 2026
Photo

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

26 Nov 2025, 16:33 UTC≈12,600 viewsread 20 August 2026
Photo

В Госавтоинспекции Магнитогорска подвели итоги рейда "Тонировка". За три часа рейда 20 водителей привлечены к административной ответственности в соответствии с ч. 3.1 статьи 12.5 КоАП РФ «Управление транспортным средством, на котором установлены стекла, светопропускание которых не соответствует требованиям технического регламента Таможенного союза «О безопасности колесных транспортных средств». В отношении 20-летнег

25 Nov 2025, 16:07 UTC≈12,200 viewsread 20 August 2026
Photo

Госавтоинспекция Магнитогорска отправила микроавтобус с неисправным рулём на спецстоянку. В Магнитогорске подвели итоги профилактической акции «Автобус».

24 Nov 2025, 14:59 UTC≈12,400 viewsread 20 August 2026
Photo

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

23 Nov 2025, 15:05 UTC≈12,500 viewsread 20 August 2026
Photo

20-летнего водителя из Магнитогорска отправили под арест на пять суток за тонированный автомобиль. 21 ноября сотрудники Госавтоинспекции провели рейдовое мероприятие «Тонировка», в рамках которого обращали внимание на светопропускание стёкол автомобилей.

22 Nov 2025, 15:52 UTC≈12,100 viewsread 20 August 2026
Photo

Завершается ремонт шестикилометрового участка трассы Стерлитамак-Белорецк-Магнитогорск В Башкирии завершается ремонт участка трассы Стерлитамак-Белорецк-Магнитогорск протяженностью шесть километров в обход Белорецка, сообщает Минтранс республики. Работы проводятся в рамках нацпроекта «Инфраструктура для жизни». По данным министерства, подрядчик выполнил фрезерование старого покрытия и провел укладку выравнивающего

21 Nov 2025, 16:52 UTC≈12,100 viewsread 20 August 2026
Photo

В Калужской области медики соревновались в стрельбе Сотрудники Центральной клинической медико-санитарной части продемонстрировали свои навыки в обращении с оружием. В спортивном комплексе "Металлург-Магнитогорск" состоялись состязания по стрельбе из пневматической винтовки. Мероприятие было организовано профсоюзным комитетом учреждения здравоохранения. Участие в соревнованиях приняли 34 работника - 10 мужчин и 24 ж

20 Nov 2025, 20:36 UTC≈12,100 viewsread 20 August 2026
Photo

МЮЗИКЛ «ДЕВЧАТА» С ПЕРВЫХ ПОКАЗОВ СТАЛ ХИТОМ В МАГНИТОГОРСКЕ Новый мюзикл композитора Егора Шашина и либреттиста Евгения Муравьева по мотивам одноименной повести Бориса Бедного, вышедший из-под пера авторов буквально в прошлом году, но уже взятый в работу четырьмя творческими коллективами, поставила на сцене Магнитогорского театра оперы и балета известный московский режиссер Алла Чепинога. В постановочной команде та

19 Nov 2025, 16:49 UTC≈12,500 viewsread 20 August 2026
Photo

В минувшие выходные пожарные Магнитогорска тушили котельную на левом берегу 15 и 16 ноября сотрудники Магнитогорского пожарно-спасательного гарнизона пять раз выезжали на тушение пожаров. 15 ноября в 22:40 огнеборцы работали на тушении пожара на улице Елькина. По данным МЧС, огнем уничтожены отопительный котел, шлакоблочная кровля и сэндвич-панели строения. Пожар был ликвидирован двумя пожарными расчетами за 25 мин

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

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

“Магнитогорск | Культура | Наука” (@Magnitogorsk_nauch), 6,670 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Magnitogorsk_nauch.

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.