Telegram RegisterThe public register of Telegram
Telegram profile photo for Мой Таганрог

Channel

Мой Таганрог

@MoiTagan

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry

36,645subscribers

-13 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001251355550
TypeChannel
Username@MoiTagan
DescriptionХочешь быть в курсе важных событий Таганрога и Ростовской области? 🔞18+ ✅ Прислать новость @MyTaganrogNewsBot ✅ Заказать рекламу @MyTaganrogAdsBot ✅ Реклама для юрлиц: telega.in/c/MoiTagan ✅ Правила Канала/ЧАТа: t.me/MoiTagan/30383
Created18 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live26 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/MoiTagan

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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 2 other registered channels. They sit inside a group of 10 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
@MoiTagan/180824 · this entry7 Aug 2026, 10:51 UTC@TaganCHP/1261627 Aug 2026, 10:52 UTC1.0072 seconds
@MoiTagan/180832 · this entry7 Aug 2026, 11:38 UTC@TaganCHP/1261707 Aug 2026, 11:39 UTC1.0072 seconds
@MoiTagan/180840 · this entry7 Aug 2026, 12:11 UTC@TaganCHP/1261747 Aug 2026, 12:11 UTC1.00under a minute
@MoiTagan/180983 · this entry7 Aug 2026, 21:30 UTC@TaganCHP/1262877 Aug 2026, 21:30 UTC1.00under a minute
@MoiTagan/180984 · this entry7 Aug 2026, 21:30 UTC@TaganCHP/1262887 Aug 2026, 21:30 UTC1.00under a minute
@RndCHP/837457 Aug 2026, 20:54 UTC@MoiTagan/180977 · this entry7 Aug 2026, 20:54 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@TaganCHP22 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (19–3)
@RndCHP6 (6/6 hand-verifiable sample passed)1.00under a minute@RndCHP (6–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 46 comparable posts for this entry, running 7 August 2026 to 8 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).

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

Recorded under the keys clone_copy · clone_source, last confirmed 8 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 9 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

36,58636,67436,6307 August 2026 — 36,658 subscribers8 August 2026 — 36,654 subscribers9 August 2026 — 36,641 subscribers10 August 2026 — 36,632 subscribers10 August 2026 — 36,628 subscribers11 August 2026 — 36,618 subscribers13 August 2026 — 36,614 subscribers14 August 2026 — 36,615 subscribers15 August 2026 — 36,614 subscribers18 August 2026 — 36,603 subscribers19 August 2026 — 36,614 subscribers20 August 2026 — 36,625 subscribers21 August 2026 — 36,626 subscribers22 August 2026 — 36,647 subscribers24 August 2026 — 36,658 subscribers25 August 2026 — 36,644 subscribers26 August 2026 — 36,638 subscribers27 August 2026 — 36,637 subscribers28 August 2026 — 36,639 subscribers29 August 2026 — 36,660 subscribers30 August 2026 — 36,650 subscribers31 August 2026 — 36,634 subscribers1 September 2026 — 36,630 subscribers2 September 2026 — 36,612 subscribers3 September 2026 — 36,614 subscribers6 September 2026 — 36,598 subscribers9 September 2026 — 36,600 subscribers11 September 2026 — 36,586 subscribers13 September 2026 — 36,610 subscribers15 September 2026 — 36,646 subscribers16 September 2026 — 36,671 subscribers19 September 2026 — 36,674 subscribers26 September 2026 — 36,645 subscribers36,6457 August 202626 September 2026
33 measurements spanning 50 days, net -13. 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 36,573–36,687 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
26 Sept 2026, 09:4236,645-29
19 Sept 2026, 11:1836,674+3
16 Sept 2026, 23:1736,671+25
15 Sept 2026, 03:5636,646+36
13 Sept 2026, 10:2136,610+24
11 Sept 2026, 16:2236,586-14
9 Sept 2026, 05:1936,600+2
6 Sept 2026, 00:1836,598-16
3 Sept 2026, 23:3836,614+2
2 Sept 2026, 13:3736,612-18
1 Sept 2026, 11:4836,630-4
31 Aug 2026, 08:1536,634-16
30 Aug 2026, 06:5436,650-10
29 Aug 2026, 06:2736,660+21
28 Aug 2026, 09:2436,639+2
27 Aug 2026, 08:4736,637-1
26 Aug 2026, 05:5836,638-6
25 Aug 2026, 07:2236,644-14
24 Aug 2026, 09:1236,658+11
22 Aug 2026, 17:1736,647first reading

Engagement

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

ERR · 30 days
0.838%
avg views ÷ 36,645 subscribers
Avg views / post
307
607 posts measured
Reaction rate
0.484%
reactions ÷ views · ER floor
Posts in window
614
of 1,272 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. It is computed over the 196 of 607 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 September 2026
Posts held1,272 (7 August 2026 – 27 September 2026)
Views total186,358
Reactions total362
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 03:35 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
≈117,000
Videos
≈14,600
Links
≈109,000

Lifetime counters from Telegram’s own channel header, read 27 September 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
1h 00m
Average length
36s

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

578 reactions across 286 posts, in 27 distinct kinds. The most used accounts for 26.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏15426.6%
❤14525.1%
👍7012.1%
👎406.92%
🤬325.54%
😱254.33%
😢213.63%
😁203.46%
🤣193.29%
🔥91.56%
❤‍🔥61.04%
😈61.04%
💯40.692%
⚡30.519%
🎉30.519%
👌30.519%
🤔30.519%
👏20.346%
💋20.346%
😭20.346%
7 further kinds91.56%

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 319 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 578 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 13 August 2026 to 27 September 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.

Advertising

Ad load
0.1%
1 of 1,000 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
215
over 1 measured post
Median views · rest
295
over 990 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. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VSb5zEWsXx116 August 202616 August 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.

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

27 Sept 2026, 02:59 UTC136 viewsread 27 September 2026
Video

❗️ ⚠️ Таганрог и вся Ростовская область, ВНИМАНИЕ❗️ Мы следим за небом 24/7 и подаём сигнал только тогда, когда он действительно нужен. Поэтому Монитор самый посещаемый канал MAX в Таганроге, имеющий регистрацию в Роскомнадзоре: https://max.ru/taganroginfo ✅ Атаки БПЛА, ракетная опасность, воздушная активность в Ростовской области — всё отслеживается в реальном времени. Мы сообщаем о воздушной угрозе сразу — без за…

27 Sept 2026, 01:02 UTC136 viewsread 27 September 2026
Photo

❗️28 сентября председатель Городской Думы Роман Валерьевич Корякин проводит приемы: ✅ с 15.45 – прием граждан, представителей юридических лиц и общественных организаций по адресу: ул. Фрунзе, 59 (общественная приемная Губернатора Ростовской области в г. Таганроге). Прием проводится по предварительной записи, тел. 8(8634) 363-003, 8(8634) 383-030; ✅ с 17.00 до 18.00 – прием жителей 17-го округа по адресу: ул. Ленина…

26 Sept 2026, 23:58 UTC265 views1 reactionsread 27 September 2026

❗️❗️❗️❗️❗️ Красный Луч и близлежащие тревога по БПЛА и далее в направлении Ровеньки ЛНР, Свердловск и Ростовская область Об этом сообщают мониторинговые каналы. Будьте внимательны и осторожны. 📱 Монитор Ростовской области - оповещения об опасностях! 🟣 Монитор в MAX!

😱1

26 Sept 2026, 22:18 UTC439 views1 reactionsread 27 September 2026

❗️❗️❗️❗️❗️ ЛНР, продолжаются фиксации БПЛА в направлении Ростовской, Воронежской области. Об этом сообщают мониторинговые каналы. Будьте внимательны и осторожны. 📱 Монитор Ростовской области - оповещения об опасностях! 🟣 Монитор в MAX!

😁1

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

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.

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.

ЧП Таганрог
@TaganCHP · 56,440
#1
Таганрог. Происшествия
@taganrog_chp61 · 102,431
#2
Блокнот Таганрог
@bloknot_taganrog · 30,541
#3
Таганрог Главный
@taganrogonline · 10,316
#4
Новости Таганрога
@novosti_taganroga · 25,699
#5
ЧП Таганрог
@chptaganrog · 19,413
#6
Мой Таганрог
@moi_taganrog · 8,945
#7
Это Ростов новости
@etorostov · 396,182
#8
Авто Таганрог
@avtotaganrog · 7,399
#9
РОСТОВ ГЛАВНЫЙ - РОСТОВ НОВОСТИ - 161
@rostov_glavniy · 283,497
#10
Таганрог Онлайн
@taganrog_online · 5,187
#11
Движение Первых| город Таганрог
@mypervietaganrog · 763
#12
Мамочки Папочки Таганрога и Ростова
@tagmamapapa · 4,048
#13
Жилье и работа Таганрог
@mytaganrogcom · 10,770
#14
Светлана Камбулова
@KambulovaSvetlana · 23,273
#15
Юрий Слюсарь
@Yuri_Slusar · 166,366
#16
Новости Ростова | 161.RU
@news161ru · 213,654
#17
РАZИН 🇷🇺
@razin_ZOV · 13,812
#18
Privet-Rostov.ru - новости Ростов-на-Дону
@privet_rostov_ru · 177,492
#19
CULT
@cult_61 · 1,457
#20
Типичный Донецк
@itsdonetsk · 617,009
#21
Администрация города Таганрога
@taganrogadmin · 7,041
#22
Don Mash
@don_mash · 79,391
#23
Политехнический институт ДГТУ в г. Таганроге
@ya_politeh_taganrog · 1,510
#24
Фортовские❤️⚽️
@fortovskie · 138
#25

Read from Telegram’s recommendation API, most recently 1 September 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.

ЧП Таганрог
@TaganCHP · 56,440
Telegram ranks this channel #2 of 17 here — alongside 16 others — read 23 August 2026
Таганрог. Происшествия
@taganrog_chp61 · 102,431
Telegram ranks this channel #2 of 21 here — alongside 20 others — read 15 August 2026
Блокнот Таганрог
@bloknot_taganrog · 30,541
Telegram ranks this channel #3 of 56 here — alongside 55 others — read 7 September 2026
Светлана Камбулова
@KambulovaSvetlana · 23,273
Telegram ranks this channel #5 of 84 here — alongside 83 others — read 18 September 2026
Таганрог | События | Новости
@Taganrog_narod · 29,573
Telegram ranks this channel #6 of 76 here — alongside 75 others — read 8 September 2026
Новости Таганрога
@novosti_taganroga · 25,699
Telegram ranks this channel #7 of 33 here — alongside 32 others — read 13 September 2026
Таганрог | События | Подслушано
@Taganrog_podslushal · 36,839
Telegram ranks this channel #7 of 67 here — alongside 66 others — read 8 September 2026
Новости Ростова и Области
@rostov_smi · 152,046
Telegram ranks this channel #27 of 76 here — alongside 75 others — read 12 August 2026
ЭТО РОСТОВ, ДЕТКА! 💎
@etorostov_tg · 21,921
Telegram ranks this channel #62 of 84 here — alongside 83 others — read 22 September 2026
Жесть Ростов
@zhest_rostov_161 · 32,797
Telegram ranks this channel #67 of 84 here — alongside 83 others — read 4 September 2026
Юрий Слюсарь
@Yuri_Slusar · 166,366
Telegram ranks this channel #83 of 89 here — alongside 88 others — read 12 August 2026

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

“Мой Таганрог” (@MoiTagan), 36,645 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/MoiTagan.

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.