Telegram RegisterThe public register of Telegram
Telegram profile photo for ДПС КОНТРОЛЬ Благовещенск @dpskontrol_28rus

Channel

ДПС КОНТРОЛЬ Благовещенск @dpskontrol_28rus

@dpskontrol_28rus

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

23,366subscribers

+211 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-1001638542408
TypeChannel
Username@dpskontrol_28rus
DescriptionДорожные новости г.Благовещенска и Амурской области.
Created12 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/dpskontrol_28rus

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 86% 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
@dpskontrol_28rus/34012 · this entry23 Oct 2026, 06:26 UTC@skaner28/2539123 Oct 2026, 11:58 UTC0.995.5 hours
@dpskontrol_28rus/33565 · this entry2 Sept 2026, 23:50 UTC@skaner28/248753 Sept 2026, 00:12 UTC0.9922 minutes
@dpskontrol_28rus/34185 · this entry9 Nov 2026, 00:26 UTC@skaner28/255389 Nov 2026, 01:40 UTC0.9974 minutes
@dpskontrol_28rus/33904 · this entry13 Oct 2026, 00:04 UTC@skaner28/2527113 Oct 2026, 01:50 UTC0.991.8 hours
@dpskontrol_28rus/33497 · this entry31 Aug 2026, 00:08 UTC@skaner28/2482831 Aug 2026, 00:41 UTC0.9433 minutes
@dpskontrol_28rus/33259 · this entry10 Aug 2026, 00:00 UTC@skaner28/2454010 Aug 2026, 01:03 UTC0.9463 minutes
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
@skaner2814 (8/8 hand-verifiable sample passed)0.9668 minutesthis entry (11–3)
@dpckontrol_28rus6 (6/6 hand-verifiable sample passed)0.9946 minutesthis entry (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. 3 of the 3 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 233 comparable posts for this entry, running 4 August 2026 to 17 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 17 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

23,15423,36623,2607 August 202616 November 2026
62 measurements spanning 101 days, net +211. 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 23,122–23,398 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
16 Nov 2026, 03:3823,366+15
12 Nov 2026, 18:2123,351+19
10 Nov 2026, 11:5423,332+7
8 Nov 2026, 23:4023,325+3
7 Nov 2026, 18:4523,322-2
5 Nov 2026, 18:5923,324-2
4 Nov 2026, 20:5123,326-2
3 Nov 2026, 20:3823,328+5
2 Nov 2026, 21:0923,323-4
1 Nov 2026, 23:2623,327+1
1 Nov 2026, 00:2723,326+4
31 Oct 2026, 00:4923,322+24
29 Oct 2026, 23:1023,298-2
28 Oct 2026, 23:4723,300-4
27 Oct 2026, 19:1023,304-6
26 Oct 2026, 20:2623,310-4
25 Oct 2026, 19:3123,314+1
24 Oct 2026, 22:3623,313+7
24 Oct 2026, 00:5523,306-7
22 Oct 2026, 21:5623,313first reading

Engagement

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

ERR · 30 days
11.8%
avg views ÷ 23,366 subscribers
Avg views / post
2,770
195 posts measured
Reaction rate
0.591%
reactions ÷ views · ER floor
Posts in window
195
of 630 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 17 November 2026
Posts held630 (4 August 2026 – 17 November 2026)
Views total539,643
Reactions total3,188
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 15:01 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
≈15,100
Videos
≈14,900
Links
≈1,040

Lifetime counters from Telegram’s own channel header, read 17 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 09m
Average length
21s

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

9,762 reactions across 628 posts, in 36 distinct kinds. The most used accounts for 21.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬2,08121.3%
❤1,81318.6%
👍1,37614.1%
🤣8058.25%
👀7457.63%
😱6686.84%
🤯4824.94%
😁2792.86%
👏2682.75%
🔥2632.69%
🙏2132.18%
🕊1111.14%
💯1011.03%
😡900.922%
🏆650.666%
🥴610.625%
🤝530.543%
🤷‍♂520.533%
🤨360.369%
😢330.338%
16 further kinds1671.71%

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

Measured over the 630 most recent posts we hold, published 4 August 2026 to 17 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
2
across the posts below
Posts paid on
2
of 630 we hold a reading for · 0.3%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dpskontrol_28rus. 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 630 most recent posts we hold for this entry, published 4 August 2026 to 17 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
1.27%
8 of 630 posts carry an ad marker
Regulatory tokens
8
posts carrying an erid · 1 distinct token
Median views · ads
2,630
over 8 measured posts
Median views · rest
2,800
over 622 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
2Vtzqv78n9Q84 August 202617 November 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 630 most recent posts we hold, published 4 August 2026 to 17 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: 15 of 195 posts held from the last 30 days (7.69%) 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).

17 Nov 2026, 06:17 UTC≈1,790 views4 reactionsread 17 November 2026
Photo

🚗🚗🚗 Новотроицкое шоссе - Воронкова.

❤2👀1😁1

17 Nov 2026, 05:28 UTC≈1,960 views6 reactionsread 17 November 2026
Photo

🚗🚗🚗 По Студенческой, за Игнатьевским шоссе.

🥴3❤1👀1👏1

17 Nov 2026, 05:21 UTC≈1,810 views6 reactionsread 17 November 2026
Advertisementerid 2Vtzqv78n9QPhoto

Информация для автолюбителей! Вызов аварийного комиссара https://wa.me/79243432000 выезд на место ДТП | оформление европротокола Автострахование https://wa.me/79243441000 - Представительство в страховой компании | юридическое сопровождение в суде - Независимая экспертиза | расчет ущерба Страховой автоюрист. Региональный центр независимых экспертов. Благовещенск, 50 лет октября 63, 408 of. Рекламодатель: индивид…

👍4❤1🤬1

17 Nov 2026, 04:53 UTC≈1,870 views5 reactionsread 17 November 2026
Photo

🚗🚗🚗 На панораме.

❤2👀1👍1😁1

17 Nov 2026, 03:24 UTC≈2,170 views15 reactionsread 17 November 2026
Photo

🚧 Квартал улицы Кузнечной в Благовещенске перекроют для реконструкции канализационного коллектора Как уточняет администрация города, с 19 ноября работы начнутся на очередном отрезке —от Амурской до Зейской. Участок закроют для автомобилистов. На маршруты общественного транспорта перекрытие не повлияет. Открыть движение здесь планируют 1 февраля 2027 года. Работы проведет «Ротек» по заказу АКС.

😡13❤1👏1

17 Nov 2026, 00:40 UTC≈2,210 views10 reactionsread 17 November 2026
Photo

🚓Отдел Госавтоинспекции г. Благовещенска и Благовещенского муниципального округа сообщает: За прошедшие сутки на дорогах г. Благовещенска и Благовещенского муниципального округа зарегистрировано 8 дорожно-транспортных происшествий, без пострадавших в них людей. Уважаемые водители, Госавтоинспекция обращает ваше внимание! Соблюдение скоростного режима - ключевой фактор безопастности на дорогах. Помните: выбор скоро…

👍5❤4👏1

17 Nov 2026, 00:23 UTC≈2,110 views24 reactionsread 17 November 2026
Photo

🎥🎥🎥🎥🎥 Неприятный сюрприз. На Тепличке ночью прорвало трубу .

🤯16😱6❤1👏1

17 Nov 2026, 00:14 UTC≈2,230 views11 reactionsread 17 November 2026
Photo

😨😨😨😨 На Воронкова потоп. По возможности объезжате .

❤6🤯4👏1

16 Nov 2026, 23:55 UTC≈2,130 views9 reactionsread 17 November 2026
Photo

🚗🚗🚗 Ленина - Театральная тройничок. Несоблюдение дистанции.

👏5👀3❤1

16 Nov 2026, 23:44 UTC≈2,240 views8 reactionsread 17 November 2026
Photo

🚓Сводка происшествий за 16 ноября За минувшие сутки на дорогах региона произошло 21 дорожно-транспортное происшествие, в трех из них пострадали люди. На территории региона пресечено 3450 нарушений Правил дорожного движения, из них в трех случаях водители управляли транспортом в состоянии опьянения. За управление транспортным средством с тонированными стеклами к административной ответственности привлечено пять водит…

❤5👏2👀1

16 Nov 2026, 21:18 UTC≈2,340 views11 reactionsread 17 November 2026
Video

Доброе утро всем ☺️ сегодня 17 ноября, вторник😎 на данный момент на улице -18🥶

❤9👍2

16 Nov 2026, 13:22 UTC≈2,580 views14 reactionsread 17 November 2026
Video

😊😊😊😊

👍8❤3🔥1🤣1🥴1

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

@dpskontrol_28rus edited 3 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
6 October 2026
Most recent edit
6 November 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 5 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.

Благовещенск №1
@amurblg1 · 44,785
#1
Skaner28
@skaner28 · 35,835
#2
Autoroadblg
@autoroadblg · 6,924
#3
Порт Амур
@portamur_ru · 12,050
#4
Дважды два
@Portal2x2 · 8,706
#5
Благовещенск
@blagoveshchensk_rf · 11,507
#6
Новости Благовещенска и не только
@novosti_blg · 33,847
#7
Амур.Инфо
@AmurInfo_news · 37,060
#8
Госавтоинспекция Амурской области
@gibdd28 · 6,366
#9
Благовещенск
@blaga24 · 23,894
#10
Вести — Амурская область
@gtrkamur · 11,057
#11
МЧС Амурской области
@mchs28 · 3,919
#12
dtp_blg
@dtp_blg · 5,444
#13
Амурский Минтранс
@mintrans_amur · 3,405
#14
Amur Mash
@amur_mash · 53,546
#15
28news - Новости Благовещенска
@the28News · 24,813
#16
Подслушано отзовик Благовещенск
@otzovik_podslushano · 2,205
#17
«Амурская правда»
@ampravda · 16,106
#18
ДПС контроль Благовещенск
@dpckontrol_28rus · 10,583
#19
ТЕЛЕПОРТ.РФ
@amurobl · 4,394
#20
Благовещенск Сегодня | новости
@blaga_veg · 7,658
#21
Олег Имамеев
@imameev · 11,466
#22
SVB NEWS
@svb_news · 8,219
#23
Непростой Свободный
@notsvb · 10,224
#24
Белогорск РФ
@belogorsk28ru · 12,011
#25
Мелюков С.Ю.
@smeliukov · 10,707
#26
Пресс-служба администрации Бурейского округа
@presssluzhba · 1,833
#27
Амурские волны
@amurvolny · 1,732
#28
Новости Свободненского района. Пресс-служба
@svobregion_28 · 1,494
#29
BLAG_DTP_NEWS
@blag_dtp_news · 2,772
#30
Дороги.БЛГ 🌐 online
@dorogi_blg · 808
#31
Первый Зейский канал 🇷🇺
@zeya_perviy · 4,592
#32
Управление по делам ГОЧС г. Благовещенска
@ugochs28 · 749
#33
МЦУ Благовещенска
@mcu_blag · 1,240
#34
Дорожный Благовещенск
@roadblg · 2,309
#35
Blagmedia | Благовещенск
@blagmedia · 11,518
#36
Регион 28 | Благовещенск авто
@region_blg · 3,131
#37
Blagmedia
@blag_media · 9,935
#38
BlagShok | Благовещенск
@blag_shok · 4,250
#39
Амурский СМЕРШ
@symbol404 · 1,525
#40
Аmur.life
@amurlife1 · 26,546
#41
АСН24 — Амурская служба новостей
@asn24ru · 11,614
#42
АМУР ТВ
@amurobl_tv · 7,834
#43
Василий Орлов
@OrlovAmur · 21,524
#44
Амурская полиция
@mvd_28_amur · 4,120
#45
Амурские спасатели (Амурский центр ГЗ и ПБ)
@amursiespasateli · 2,538
#46
Амурская область | Правительство
@amurobl_official · 10,590
#47
Прокуратура Амурской области
@prokuratura28 · 5,777
#48
Чисанчи
@chissanchi · 8,163
#49
Амурский
@Amur_telega · 9,246
#50
Общественно-Культурный Центр.
@okcblag · 5,262
#51
Амурские отголоски 🥇
@amurotgoloski · 2,690
#52
Gazeta-bam.ru • Тында
@gazeta_bam · 4,842
#53
Министерство по физической культуре и спорту Амурской области
@min_fks28 · 2,454
#54
Amur Travel
@amur_travel · 8,036
#55
ТЫНДА NEWS
@tyndanews · 11,744
#56
SVBSTAR ⚡ Свободный
@svbstar · 13,566
#57
Зейский вестник
@zvportal · 6,944
#58
Минкультуры Амурской области
@minkultamur · 1,650
#59
Министерство здравоохранения Амурской области
@minzdravamur · 1,644
#60
Белогорск Z ИНФО
@belogorsklife · 8,098
#61
Следком Амурской области
@amursledcom · 2,482
#62
Амурский минлес
@amurles · 803
#63
Город Свободный|Пресс-служба SVB
@news_svobodniy · 5,634
#64
Благовещенский городской суд Амурской области
@blg_sud · 1,937
#65
Администрация города Райчихинск
@adm_Raichikhinsk · 2,563
#66
Народный фронт | Амурская область
@nfamuroblast · 1,609
#67
Минэкономразвития Амурской области
@mineconomamur · 1,816
#68
Управление культуры города Благовещенска
@kulturablg · 1,134
#69
Благовещенский муниципальный округ Амурская область
@blagraionamur · 1,862
#70
МолодБлаг
@molodblag28 · 2,334
#71
Амур-Китай 🇷🇺 🇨🇳
@amurchina · 3,777
#72
ZOновости28
@ZOnovosti28 · 7,147
#73
МинЖКХ Амурской области
@mingkh_amur · 749
#74
Минцифры Амурской области
@digital_amurobl · 918
#75
Администрация Серышевского муниципального округа
@adm_ser · 1,195
#76
Министерство сельского хозяйства Амурской области
@agro_amurobl · 353
#77
АмГУ ONLINE
@amsu_online · 3,832
#78
🇷🇺ZОV России 🇷🇺
@zov_channel · 3,165
#79
Администрация Октябрьского округа
@oktr_amur · 1,653
#80
Memreporter
@memreporter28 · 1,008
#81
Торгово-промышленная палата Амурской области
@tppamur · 1,510
#82
Администрация города Зеи Амурской области
@amurobladmzeya · 1,605
#83
РКС Благовещенск
@Amurcomsys · 1,289
#84
Тамбовский муниципальный округ
@tambovskiiraion · 1,541
#85
Фото Амурской области
@vestiselem · 594
#86
Библиотеки Благовещенска
@biblioteki_blag · 751
#87

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

Благовещенск
@blaga24 · 23,894
Telegram ranks this channel #3 of 66 here — alongside 65 others — read 16 September 2026
Новости Благовещенска и не только
@novosti_blg · 33,847
Telegram ranks this channel #3 of 92 here — alongside 91 others — read 3 September 2026
Skaner28
@skaner28 · 35,835
Telegram ranks this channel #3 of 90 here — alongside 89 others — read 2 September 2026
Благовещенск №1
@amurblg1 · 44,785
Telegram ranks this channel #3 of 60 here — alongside 59 others — read 27 August 2026
Типичный Благовещенск
@Blagoveshchensku · 67,429
Telegram ranks this channel #5 of 78 here — alongside 77 others — read 4 October 2026
Новости Благовещенска и Амура
@blagoveshensk_smi · 24,199
Telegram ranks this channel #7 of 45 here — alongside 44 others — read 16 September 2026
28news - Новости Благовещенска
@the28News · 24,813
Telegram ranks this channel #11 of 85 here — alongside 84 others — read 14 September 2026
Амур.Инфо
@AmurInfo_news · 37,060
Telegram ranks this channel #15 of 95 here — alongside 94 others — read 31 August 2026
Amur Mash
@amur_mash · 53,546
Telegram ranks this channel #40 of 97 here — alongside 96 others — read 24 August 2026
Вакансии в Благовещенске
@blagoveshchensx_rabota · 22,445
Telegram ranks this channel #43 of 66 here — alongside 65 others — read 20 September 2026
Василий Орлов
@OrlovAmur · 21,524
Telegram ranks this channel #54 of 97 here — alongside 96 others — read 22 September 2026
Аmur.life
@amurlife1 · 26,546
Telegram ranks this channel #76 of 92 here — alongside 91 others — read 12 September 2026

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

“ДПС КОНТРОЛЬ Благовещенск @dpskontrol_28rus” (@dpskontrol_28rus), 23,366 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/dpskontrol_28rus.

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.