Telegram RegisterThe public register of Telegram
Telegram profile photo for Просто Михаил Шебекино 📸

Channel

Просто Михаил Шебекино 📸

@mfoto31

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

46,346subscribers

+565 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001751816142
TypeChannel
Username@mfoto31
DescriptionЛучший канал о Шебекино 🇷🇺 Прислать новость сотрудничество @mfoto31bot Реклама: @mfoto31bot Регистрация в РКН https://gosuslugi.ru/snet/6798f52a19290c0f937eff4c
Created28 October 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/mfoto31

Topic

National news — 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 21 August 2026 and assigned it the closest of 31 fixed categories, at 69% 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 2 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@mfoto31/35933 · this entry18 Aug 2026, 12:34 UTC@love_shbk/2323818 Aug 2026, 12:58 UTC1.0024 minutes
@mfoto31/35975 · this entry20 Aug 2026, 06:49 UTC@love_shbk/2326420 Aug 2026, 07:03 UTC1.0014 minutes
@mfoto31/37786 · this entry29 Oct 2026, 18:36 UTC@love_shbk/2373930 Oct 2026, 03:25 UTC1.008.8 hours
@mfoto31/37787 · this entry30 Oct 2026, 05:54 UTC@love_shbk/2374130 Oct 2026, 06:31 UTC1.0037 minutes
@mfoto31/37946 · this entry5 Nov 2026, 16:45 UTC@love_shbk/237585 Nov 2026, 18:07 UTC1.0082 minutes
@mfoto31/38051 · this entry9 Nov 2026, 14:30 UTC@love_shbk/237719 Nov 2026, 14:31 UTC1.00under a minute
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
@love_shbk8 (8/8 hand-verifiable sample passed)1.0059 minutesthis entry (8–0)
@svodki_svo_kto5 (5/5 hand-verifiable sample passed)1.009.5 hoursthis 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 1,419 comparable posts for this entry, running 5 August 2026 to 11 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).

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

45,77246,49146,131.546,3466 August 202612 November 2026
64 measurements spanning 98 days, net +565. 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 45,664–46,599 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
12 Nov 2026, 01:3646,346-1
10 Nov 2026, 00:0946,347-6
8 Nov 2026, 13:5146,353-17
7 Nov 2026, 09:4546,370-6
6 Nov 2026, 13:0646,376-8
5 Nov 2026, 13:4446,384-20
4 Nov 2026, 15:1946,404-17
3 Nov 2026, 15:2646,421-10
2 Nov 2026, 13:4646,431-15
1 Nov 2026, 11:0646,446-12
31 Oct 2026, 10:2846,458-21
30 Oct 2026, 10:1546,479-1
29 Oct 2026, 08:5546,480-11
28 Oct 2026, 07:4546,491+9
27 Oct 2026, 10:2846,482+25
26 Oct 2026, 08:0546,457-9
25 Oct 2026, 05:0646,466-7
24 Oct 2026, 04:1846,473-1
23 Oct 2026, 02:4846,474-7
22 Oct 2026, 02:3146,481first reading

Engagement

1,544 posts held, back to 5 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 196 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.11%
avg views ÷ 46,346 subscribers
Avg views / post
3,760
456 posts measured
Reaction rate
1.03%
reactions ÷ views · ER floor
Posts in window
456
of 1,544 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 12 November 2026
Posts held1,544 (5 August 2026 – 12 November 2026)
Views total1,714,982
Reactions total17,706
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 16:30 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
≈14,400
Videos
≈5,850
Links
≈18,000

Lifetime counters from Telegram’s own channel header, read 12 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
2h 51m
Average length
39s

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

41,371 reactions across 996 posts, in 17 distinct kinds. The most used accounts for 33.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬13,69433.1%
🙏8,43720.4%
😢5,53513.4%
❤4,54211.0%
custom 54427912971967665322,2085.34%
💯1,7524.23%
🤯1,5853.83%
😱1,3693.31%
🤔5021.21%
custom 54359224977342102144020.972%
💔3150.761%
😡2990.723%
custom 51905273422539964512660.643%
⚡1840.445%
🕊1660.401%
🫡1010.244%
custom 5417948957248618514140.034%

Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 997 of the 1,000 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 41,371 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 8 September 2026 to 12 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.

Telegram Stars

Stars received
36
across the posts below
Posts paid on
15
of 1,000 we hold a reading for · 2%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mfoto31. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 8 September 2026 to 12 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
10.6%
106 of 1,000 posts carry an ad marker
Regulatory tokens
106
posts carrying an erid · 106 distinct tokens
Median views · ads
3,560
over 106 measured posts
Median views · rest
3,810
over 894 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzquYGxZa18 September 20268 September 2026
2VtzquZnPnL124 September 202624 September 2026
2VtzquZzmde116 September 202616 September 2026
2VtzqubTRNM114 October 202614 October 2026
2VtzqucWrHk13 November 20263 November 2026
2VtzqufsmTa128 September 202628 September 2026
2Vtzqufx26i12 November 20262 November 2026
2Vtzqufy4XF112 October 202612 October 2026
2Vtzqug2ThN121 September 202621 September 2026
2VtzqugwEWZ123 October 202623 October 2026
2VtzqumMkx4111 September 202611 September 2026
2Vtzqumr4Gm122 October 202622 October 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it. 94 further tokens are held for this entry and not listed here.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 8 September 2026 to 12 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

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

12 Nov 2026, 16:27 UTC162 views0 reactionsread 12 November 2026

⚡️ Погиб мирный житель, четыре человека ранены В Шебекино FPV-дрон атаковал автомобиль. Мужчина получил тяжёлые травмы и скончался на месте. Ещё один мужчина получил осколочные ранения головы и руки. Его доставили в больницу. В селе Маломихайловка при атаке дрона на автомобиль мужчина получил множественные осколочные ранения рук и ног. Его доставили в больницу. В больнице оказали помощь двум женщинам с акубаротрав…

12 Nov 2026, 15:48 UTC≈1,280 views7 reactionsread 12 November 2026
Video

⚡️В Шебекино два мужчины получили акубаротравмы в результате атак FPV-дронов. В Шебекино при детонации дронов повреждены кровля социального объекта, автомобиль «ГАЗель» и инфраструктурный объект. В селе Белянка два FPV-дрона атаковали складское помещение предприятия — пробита крыша. Ещё один дрон вызвал возгорание автомобиля. В селе Крапивное от взрыва дрона повреждён грузовой автомобиль. На видео мат

❤3😢2🤬1🤯1

12 Nov 2026, 14:28 UTC≈2,590 views90 reactionsread 12 November 2026

⚡️Погибла 12-летняя девочка в результате атаки беспилотника. Её мать — в тяжёлом состоянии. В районе посёлка Комсомольский Белгородского округа беспилотник атаковал автомобиль. Девочка от полученных травм скончалась на месте. Её мама получила осколочное ранение головы. Женщину в тяжёлом состоянии транспортируют в областную клиническую больницу. Мы в МАХ https://max.ru/mfoto31 Мы в ВК https://vk.com/mfoto31 📝Написа…

😢46🤬37🙏4❤2🤔1

12 Nov 2026, 13:39 UTC≈2,870 views32 reactionsread 12 November 2026
Photo

⚡️ Какие сети — такой и улов! В Шебекино антидроновая сеть поймала беспилотник. Дрон запутался и не сдетонировал. Мы в МАХ https://max.ru/mfoto31 Мы в ВК https://vk.com/mfoto31 📝Написать нам https://t.me/mfoto31bot

🙏21❤7🤔2🤬1custom 54427912971967665321

12 Nov 2026, 12:51 UTC≈2,990 views34 reactionsread 12 November 2026

⚡️В Шебекино мелкоп в результате атаки дрона на автомобиль, по словам очевидцев, один человек погиб, ещё один получил ранения. Информация уточняется. Мы в МАХ https://max.ru/mfoto31 Мы в ВК https://vk.com/mfoto31 📝Написать нам https://t.me/mfoto31bot

😢21🤬9🙏3custom 54427912971967665321

12 Nov 2026, 12:45 UTC≈2,920 views14 reactionsread 12 November 2026
Photo

⚡️В Шебекино, в районе Лиги, произошла детонация дрона на парковке. Повреждены автомобили и остекление многоквартирного дома. Мы в МАХ https://max.ru/mfoto31 Мы в ВК https://vk.com/mfoto31 📝Написать нам https://t.me/mfoto31bot

🤬11❤1😡1custom 54427912971967665321

12 Nov 2026, 12:33 UTC≈2,770 views21 reactionsread 12 November 2026

⚡️В Шебекино на мелкоп дрон атаковал автомобиль. По предварительной информации, один человек получил тяжёлые ранения. Мы в МАХ https://max.ru/mfoto31 Мы в ВК https://vk.com/mfoto31 📝Написать нам https://t.me/mfoto31bot

🙏14🤬6custom 54427912971967665321

12 Nov 2026, 11:03 UTC≈2,770 views14 reactionsread 12 November 2026
Advertisementerid 2VtzqwSKGjgVideo

Что такое процедура банкротства: кому она нужна и зачем В этом видео юрист Аделина Тимонова расскажет, что такое процедура банкротства, кому она подходит, какие долги можно списать и зачем её проходить. 👩‍⚖️ Сопровождение банкротства по всей России, без личного присутствия в суде. 📩 Бесплатная консультация в личных сообщениях: ТГ: https://t.me/Timonova_Adelina_D МАХ: https://maxln.ru/dJejha ВК: https://vk.com/id20…

🤬9❤2custom 51905273422539964511custom 54359224977342102141custom 54427912971967665321

12 Nov 2026, 10:47 UTC≈2,770 views13 reactionsread 12 November 2026

Пуски крылатых ракет Мы в МАХ https://max.ru/mfoto31 Мы в ВК https://vk.com/mfoto31 📝Написать нам https://t.me/mfoto31bot

🙏12custom 54427912971967665321

12 Nov 2026, 10:40 UTC≈2,920 views27 reactionsread 12 November 2026
Photo

⚡️В Шебекино в результате атак ВСУ пострадали четыре человека. FPV-дрон атаковал многоквартирный дом. Ранения головы получили два мужчины: один — мелкие осколочные, второй — осколочные ранения головы, плеча и рук. При ударе второго дрона по коммерческому объекту пострадали ещё два человека. Мужчина получил осколочное ранение лица, у женщины диагностировали акубаротравму. Повреждены многоквартирный дом, коммерчески…

🤬9🙏8❤5😢3custom 54427912971967665322

12 Nov 2026, 10:27 UTC≈2,830 views13 reactionsread 12 November 2026
Photo

⚖️ Несовершеннолетнего жителя Губкина будут судить за государственную измену По данным УФСБ России по Белгородской области, в августе 2025 года 16-летний житель Губкина через Telegram согласился сотрудничать с представителем СБУ за денежное вознаграждение. По заданию украинских кураторов подросток установил скрытую видеокамеру для наблюдения за объектом транспортной инфраструктуры вблизи железной дороги. Также в Во…

🤯6❤2🤬2😢2😱1

12 Nov 2026, 08:43 UTC≈3,130 views30 reactionsread 12 November 2026

⚡️ В Шебекино в результате атак ВСУ пострадала мирная жительница. Женщина получила осколочные ранения уха при детонации FPV-дрона. В Шебекино повреждены коммерческий объект, частный дом и четыре автомобиля. В Вознесеновке огнём уничтожен автомобиль. Во Ржевке повреждены два частных дома и две машины. Под удар также попал автомобиль — разбиты стёкла и кузов. Мы в МАХ https://max.ru/mfoto31 Мы в ВК https://vk.com/…

🤬17🙏5❤4custom 54427912971967665323😡1

Showing the 12 most recent of 1,544 posts we hold for @mfoto31. 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

@mfoto31 edited 2 posts 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
4 October 2026
Most recent edit
11 October 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @mfoto31 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
2 October 2026
Most recent seen missing
2 October 2026
Median time before seen missing
20 hours
Seen missing in the last 30 days
0

Forward network

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

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Жесть Шебекино
@zhest_shebekino_channel · 60,703
#1
ШÖ ❓ Шебекино
@Sho_Shebekino · 30,893
#2
Шёпот Шебекино
@club_shebekino · 48,680
#3
Настоящий Гладков
@vvgladkov · 398,604
#4
Жесть Белгород
@zhest_belgorod · 588,064
#5
Подслушано Шебекино
@love_shbk · 8,996
#6
Радар Белгород
@radarb31 · 137,294
#7
Белгород №1
@belgorod01 · 189,419
#8
Блэтгород
@bletgorod · 106,261
#9
Белгород С-400🚀🇷🇺
@belgorodc400 · 49,050
#10
Белгородская область оповещения, тревоги
@lpr1_Belgorod_alarm · 56,977
#11
grohot_pgr
@grohot_pgr · 30
#12
Казачья Лопань Z
@kozacha23 · 39,532
#13
Владимир Жданов
@vn_zhdanov · 4,165
#14
БелПлюс
@belplus_bg · 70,366
#15
Взрывы Белгород🇷🇺
@vzrivi_belgorod1 · 34,186
#16
онлайн 31🇷🇺
@onlain31 · 5,448
#17
БЕЛГОРОДЕЦ
@belgorodecRU · 91,989
#18
Белгород — Молния
@bbbelgorod · 48,790
#19
Белгородский Андеграунд
@undeground_belgorod_31 · 33,758
#20
Авто Белгород
@avto_belgorod31 · 25,598
#21
Белгород | ФОНАРЬ🔦
@fonartv · 26,899
#22
Бел.Ру | Новости Белгорода
@IABelRu · 34,326
#23
Белгородский канал
@channelbel · 7,227
#24
ЧП Белгород
@chp_bel · 63,022
#25
Go31 | Новости Белгорода
@belgorod_go31 · 35,112
#26
Оперштаб Белгородской области
@operativno31 · 15,383
#27
Старый Оскол !NEWS
@belgorod_best31 · 7,599
#28
ZOV Белгород
@top_news_su · 2,257
#29
bel31online
@bel31online · 7
#30
📬Открытый Белгород
@openbelgorod · 5,751
#31
Красная Яруга🇷🇺
@krasnaya_yaruga31 · 29,585
#32
Белгородчина31🇷🇺
@belgorodchina31 · 6,729
#33
Мэрия Белгорода
@beladm31 · 6,737
#34
Белгород Сирена🚨🇷🇺
@belgorod_sirena31 · 12,995
#35
Шебекино | НОВОСТИ
@shebekino_info · 3,587
#36
Приграничный Радар
@prigranichie_radar1 · 32,154
#37
🚀Приграничный Наблюдатель🇷🇺
@ZOV_granicy · 11,464
#38
Жесть Курск
@zhest_kursk_146 · 91,251
#39
МЧС Белгородской области
@mchs31 · 18,395
#40
🇷🇺ОперСводки 31🇷🇺
@opersvodki_belgorod · 18,563
#41
🚨Белгород | Live
@belgorod_live1 · 13,547
#42
Мир Белогорья
@mirbelogorya · 12,268
#43
Правительство Белгородской области
@belregion_ru · 4,565
#44
Сводки и Аналитика СВО (Резерв)
@rezervsvo · 203,600
#45
Border Notes Shebekino | Записки с границы Шебекино
@bordernotes · 622
#46
Оперштаб Курской области 🇷🇺
@gubernator_46 · 182,482
#47
ПОГРАНИЧНИК ИЗ АДА
@pograni4nik_iz_ada · 103,983
#48
ZАПИСКИ VЕТЕРАНА 🇷🇺
@notes_veterans · 273,644
#49
Группировка «СЕВЕР»|Приграничье
@grp_sever · 33,746
#50
Два майора
@dva_majors · 1,161,954
#51
МАЛИКОВЪ
@steelmalikov · 14,058
#52
БелГородские подробности
@bel_podrobnosti · 7,130
#53
Пепел ➜ Белгород
@belpepel · 169,095
#54
Тринадцатый.
@Z13_Separ · 208,541
#55
Мир сегодня с "Юрий Подоляка"
@yurasumy · 2,662,248
#56
Стас Фейс🫡
@Stasfeisiia · 5,966
#57
Readovka
@readovkanews · 2,015,419
#58
ТРУДНЫЙ ТОКОВ
@tokov · 3,214
#59
SHOT
@shot_shot · 1,265,529
#60
Старше Эдды
@vysokygovorit · 484,806
#61
Белгород №1. Жизнь
@belgorod01people · 38,026
#62
СУДЖА РОДНАЯ 🇷🇺
@rodnaya_sudzha · 71,120
#63
Поддубный |Z|О|V| edition
@epoddubny · 567,778
#64
Харьковское направление
@XNRRussia · 25,020
#65
контент мурчановой
@molchanovaioy · 210
#66

Read from Telegram’s recommendation API, most recently 27 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

ШÖ ❓ Шебекино
@Sho_Shebekino · 30,893
Telegram ranks this channel #2 of 57 here — alongside 56 others — read 6 September 2026
Жесть Шебекино
@zhest_shebekino_channel · 60,703
Telegram ranks this channel #2 of 59 here — alongside 58 others — read 22 August 2026
Шёпот Шебекино
@club_shebekino · 48,680
Telegram ranks this channel #3 of 59 here — alongside 58 others — read 26 August 2026
Казачья Лопань Z
@kozacha23 · 39,532
Telegram ranks this channel #8 of 84 here — alongside 83 others — read 30 August 2026
Авто Белгород
@avto_belgorod31 · 25,598
Telegram ranks this channel #13 of 83 here — alongside 82 others — read 14 September 2026
Белгородский Андеграунд
@undeground_belgorod_31 · 33,758
Telegram ranks this channel #14 of 82 here — alongside 81 others — read 4 September 2026
ЧП Белгород
@chp_bel · 63,022
Telegram ranks this channel #15 of 85 here — alongside 84 others — read 21 August 2026
Радар Белгород
@radarb31 · 137,294
Telegram ranks this channel #15 of 79 here — alongside 78 others — read 13 August 2026
Zона приграничья🇷🇺
@glaZ_graniZa · 20,609
Telegram ranks this channel #16 of 80 here — alongside 79 others — read 25 September 2026
Белгородский Осведомитель
@belgorod_informant · 22,233
Telegram ranks this channel #16 of 82 here — alongside 81 others — read 20 September 2026
Белгород С-400🚀🇷🇺
@belgorodc400 · 49,050
Telegram ranks this channel #16 of 83 here — alongside 82 others — read 25 August 2026
Взрывы Белгород🇷🇺
@vzrivi_belgorod1 · 34,186
Telegram ranks this channel #17 of 82 here — alongside 81 others — read 3 September 2026
Белгород — Молния
@bbbelgorod · 48,790
Telegram ranks this channel #17 of 88 here — alongside 87 others — read 26 August 2026
Go31 | Новости Белгорода
@belgorod_go31 · 35,112
Telegram ranks this channel #18 of 83 here — alongside 82 others — read 2 September 2026
bel31online
@bel31online · 7
Telegram ranks this channel #18 of 82 here — alongside 81 others — read 27 August 2026
Белгород | ФОНАРЬ🔦
@fonartv · 26,899
Telegram ranks this channel #19 of 88 here — alongside 87 others — read 11 September 2026
Бел.Ру | Новости Белгорода
@IABelRu · 34,326
Telegram ranks this channel #19 of 86 here — alongside 85 others — read 3 September 2026
Настоящий Гладков
@vvgladkov · 398,604
Telegram ranks this channel #19 of 87 here — alongside 86 others — read 10 August 2026
Красная Яруга🇷🇺
@krasnaya_yaruga31 · 29,585
Telegram ranks this channel #20 of 59 here — alongside 58 others — read 7 September 2026
БЕЛГОРОДЕЦ
@belgorodecRU · 91,989
Telegram ranks this channel #20 of 57 here — alongside 56 others — read 16 August 2026
Белгород
@belgorod_tg · 38,637
Telegram ranks this channel #23 of 81 here — alongside 80 others — read 30 August 2026
Блэтгород
@bletgorod · 106,261
Telegram ranks this channel #23 of 81 here — alongside 80 others — read 15 August 2026
БелПлюс
@belplus_bg · 70,366
Telegram ranks this channel #25 of 80 here — alongside 79 others — read 20 August 2026
Белгород №1
@belgorod01 · 189,419
Telegram ranks this channel #25 of 84 here — alongside 83 others — read 11 August 2026

This channel appears in 42 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“Просто Михаил Шебекино 📸” (@mfoto31), 46,346 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/mfoto31.

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.