Telegram RegisterThe public register of Telegram
Telegram profile photo for «БЛОГ ВЛАДИВОСТОК»

Channel

«БЛОГ ВЛАДИВОСТОК»

@blog_vladivostok

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

10,467subscribers

-422 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-1001077378130
TypeChannel
Username@blog_vladivostok
DescriptionТут своя атмосфера👌 Вопросы,предложения/отклоняют заявку в чат: @Blogvladivostok_bot Я в MAX-подпишись! 👉 https://max.ru/blog_vladivostok
Created3 April 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/blog_vladivostok

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 4 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
@serch/49406 Aug 2026, 08:30 UTC@blog_vladivostok/26748 · this entry7 Aug 2026, 11:18 UTC1.0027 hours
@serch/49888 Aug 2026, 11:33 UTC@blog_vladivostok/26770 · this entry9 Aug 2026, 22:41 UTC1.0035 hours
@serch/510614 Aug 2026, 20:15 UTC@blog_vladivostok/26815 · this entry15 Aug 2026, 05:44 UTC1.009.5 hours
@serch/526924 Aug 2026, 15:17 UTC@blog_vladivostok/26914 · this entry24 Aug 2026, 15:28 UTC1.0011 minutes
@serch/528725 Aug 2026, 12:44 UTC@blog_vladivostok/26931 · this entry26 Aug 2026, 11:18 UTC1.0023 hours
@serch/700514 Nov 2026, 07:55 UTC@blog_vladivostok/27867 · this entry14 Nov 2026, 10:20 UTC1.002.4 hours
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
@serch10 (8/8 hand-verifiable sample passed)1.0011 hours@serch (10–0)
@bbbreaking5 (5/5 hand-verifiable sample passed)1.004.7 hours@bbbreaking (5–0)
@Vvobandito11 (8/8 hand-verifiable sample passed)1.003.8 hours@Vvobandito (7–4)
@nadezdinskiirayon7 (7/7 hand-verifiable sample passed)1.0034 minutesthis entry (4–3)

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. 17 of the 17 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 165 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 keys clone_copy · clone_mutual, last confirmed 18 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

10,46710,88910,6787 August 2026 — 10,889 subscribers7 August 2026 — 10,888 subscribers8 August 2026 — 10,886 subscribers9 August 2026 — 10,885 subscribers10 August 2026 — 10,887 subscribers12 August 2026 — 10,886 subscribers13 August 2026 — 10,884 subscribers14 August 2026 — 10,881 subscribers19 August 2026 — 10,880 subscribers21 August 2026 — 10,875 subscribers23 August 2026 — 10,873 subscribers24 August 2026 — 10,868 subscribers25 August 2026 — 10,863 subscribers26 August 2026 — 10,861 subscribers27 August 2026 — 10,866 subscribers28 August 2026 — 10,861 subscribers29 August 2026 — 10,862 subscribers30 August 2026 — 10,861 subscribers31 August 2026 — 10,859 subscribers1 September 2026 — 10,857 subscribers2 September 2026 — 10,858 subscribers3 September 2026 — 10,860 subscribers5 September 2026 — 10,861 subscribers9 September 2026 — 10,862 subscribers11 September 2026 — 10,859 subscribers13 September 2026 — 10,852 subscribers15 September 2026 — 10,850 subscribers16 September 2026 — 10,848 subscribers19 September 2026 — 10,847 subscribers26 September 2026 — 10,808 subscribers4 October 2026 — 10,806 subscribers9 October 2026 — 10,805 subscribers14 October 2026 — 10,804 subscribers16 October 2026 — 10,803 subscribers17 October 2026 — 10,801 subscribers18 October 2026 — 10,798 subscribers19 October 2026 — 10,600 subscribers20 October 2026 — 10,577 subscribers21 October 2026 — 10,512 subscribers22 October 2026 — 10,513 subscribers24 October 2026 — 10,514 subscribers25 October 2026 — 10,510 subscribers26 October 2026 — 10,508 subscribers27 October 2026 — 10,509 subscribers29 October 2026 — 10,506 subscribers30 October 2026 — 10,504 subscribers31 October 2026 — 10,499 subscribers1 November 2026 — 10,497 subscribers2 November 2026 — 10,495 subscribers3 November 2026 — 10,491 subscribers4 November 2026 — 10,492 subscribers5 November 2026 — 10,488 subscribers9 November 2026 — 10,483 subscribers11 November 2026 — 10,485 subscribers13 November 2026 — 10,474 subscribers17 November 2026 — 10,467 subscribers7 August 202617 November 2026
56 measurements spanning 102 days, net -422. 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 10,404–10,952 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
17 Nov 2026, 09:3910,467-7
13 Nov 2026, 23:4610,474-11
11 Nov 2026, 09:0510,485+2
9 Nov 2026, 18:0810,483-5
5 Nov 2026, 22:4510,488-4
4 Nov 2026, 20:4710,492+1
3 Nov 2026, 16:4710,491-4
2 Nov 2026, 15:2810,495-2
1 Nov 2026, 13:5610,497-2
31 Oct 2026, 11:3110,499-5
30 Oct 2026, 12:5610,504-2
29 Oct 2026, 09:4710,506-3
27 Oct 2026, 06:5610,509+1
26 Oct 2026, 04:0810,508-2
25 Oct 2026, 02:2810,510-4
24 Oct 2026, 02:2710,514+1
22 Oct 2026, 23:1010,513+1
21 Oct 2026, 22:1010,512-65
20 Oct 2026, 15:1610,577-23
19 Oct 2026, 17:0010,600first reading

Engagement

384 posts held, back to 3 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 72 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.96%
avg views ÷ 10,467 subscribers
Avg views / post
938
159 posts measured
Reaction rate
2.67%
reactions ÷ views · ER floor
Posts in window
165
of 384 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 155 of 159 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 17 November 2026
Posts held384 (3 August 2026 – 17 November 2026)
Views total149,156
Reactions total3,885
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 23:55 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
≈9,620
Videos
≈8,460
Links
≈3,050

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
1h 23m
Average length
35s

Measured directly from 144 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,626 reactions across 370 posts, in 22 distinct kinds. The most used accounts for 16.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁1,58016.4%
👍1,21812.7%
🤣1,19012.4%
🔥1,05310.9%
❤9559.92%
😱7778.07%
👀6837.10%
😍6136.37%
💯4434.60%
😢2552.65%
👌1581.64%
😨1281.33%
😐1091.13%
🎉850.883%
custom 5204206774437031951790.821%
🤪770.8%
🤝670.696%
🙏550.571%
❤‍🔥410.426%
👏410.426%
2 further kinds190.197%

Custom emoji. One row above is a 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 count beside it is 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 371 of the 384 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,626 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 384 most recent posts we hold, published 3 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.

Advertising

Ad load
1.82%
7 of 384 posts carry an ad marker
Regulatory tokens
7
posts carrying an erid · 7 distinct tokens
Median views · ads
842
over 7 measured posts
Median views · rest
1,030
over 369 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
2SDnjcXPgsD16 November 20266 November 2026
2SDnjcXPgsD1117 August 202617 August 2026
2SDnjdPNVJS113 November 202613 November 2026
2VtzqxbrnVH131 August 202631 August 2026
CQH36pWzJqVKtS29vGNHnSNVD4yJXVVHztUuKFoydWkroa14 November 20264 November 2026
CQH36pWzJqVKtS2A3KhiNSWEKm9cvzuBBfiXiGUshV5g8217 November 20267 November 2026
CQH36pWzJqVKtS2A4AumcxiTD5ffrJzp6Ra8trU8X8CMQy15 November 20265 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 384 most recent posts we hold, published 3 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: 1 of 165 posts held from the last 30 days (0.606%) 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, 12:58 UTC666 views3 reactionsread 17 November 2026

⚠️⚠️⚠️⚠️Есть кто в Москву летит в первых числах декабря? Напишите мне в личку 👉 @Blogvladivostok_bot

👀3

17 Nov 2026, 11:54 UTC745 views33 reactionsread 17 November 2026
Video

Просто стоял и снимал видео. Никаких тайм лапсов❤️

❤29👍4

17 Nov 2026, 11:51 UTC734 views11 reactionsread 17 November 2026
Photo

Более 700 тысяч российских сайтов могут отключиться из-за сбоя у хостинг-провайдера Timeweb. За полчаса пользователи оставили около 2200 жалоб на работу хостинга и облачной платформы Timeweb Cloud. В компании подтвердили проблемы с сетевым оборудованием и сообщили, что инженеры восстанавливают сервисы. Также массовые сбои интернета начались во всех регионах России. Цифровой апокалипсис начался 🤨

👀11

17 Nov 2026, 10:53 UTC755 views5 reactionsread 17 November 2026
Video

Я не знаю почему видео тормозит каждый раз🤦🏻🤷🏻‍♂️ Сбор продолжается и он срочный ‼️ Многие из вас помогают, были суммы и 10 и даже 50 тыс рублей, каждая сумма важна, напомню, что даже 100 рублей решают! Уже собрано 140000 руб, это приличная сумма для мелких закупок, но для мавика это очень и очень мало, а он нужен, и генераторы к зиме парням нужны… Кто ещё не видел, или не думал-хочет ли он помочь, то время подумать.…

🙏4❤1

17 Nov 2026, 10:46 UTC728 views17 reactionsread 17 November 2026
Video

Парень показал, как правильно надо передавать показания счётчиков Сохраняем, чтобы не забыть

❤10😁6🔥1

17 Nov 2026, 09:34 UTC768 views16 reactionsread 17 November 2026
Photo

Новым Джеймс Бондом стал Роберт Паттинсон — об это сообщил официальный аккаунт фильма в X. Режиссером фильма стал Дени Вильнёв, а по слухам планируется 3 фильма. «Сказать, что роль — воплощение моей мечты, это ничего не сказать», — сказал Роберт Паттинсон про то, что стал Агентом 007. Зато ему машина Бонда не нужна, он быстрее бегает 😁

😁13😐2😨1

17 Nov 2026, 09:09 UTC817 views19 reactionsread 17 November 2026
Photo

2027 год будет годом войн, экономических потрясений и климатических катастроф — The Economist представили традиционный прогноз на своей обложке. Лучше следующий год не станет: военные конфликты обострятся, будут происходить новые цифровые кражи, а глобальное потепление принесёт рекордную жару и пожары. Искусственный интеллект продолжит быстро развиваться, начнутся проблемы с грузовым судоходством, а политика Трампа…

😱10👍4😢4💯1

17 Nov 2026, 04:35 UTC904 views2 reactionsread 17 November 2026

Как обстановка на дорогах? Снег есть? Накидайте фоток в комментариях

👍2

Showing the 12 most recent of 384 posts we hold for @blog_vladivostok. 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 recorded as deleted after publishing

We recorded 2 posts on @blog_vladivostok 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
24 August 2026
Most recent seen missing
4 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
1

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

17 Nov 2026, 01:10 UTCAnonymous Poll236 voters

Снег будет?

  1. Да, вечером начнется и нам кабзда69%
  2. Пройдет мимо, как всегда 🥺31%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 384 most recent posts we hold, published 3 August 2026 to 17 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

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.

ДЕРЗКИЙ ВЛАДИВОСТОК ⚓️
@Vvobandito · 20,136
Telegram ranks this channel #12 of 94 here — alongside 93 others — read 28 September 2026
revizor_vdk
@revizor_vdk · 20,628
Telegram ranks this channel #14 of 86 here — alongside 85 others — read 26 September 2026
DPS VL | Владивосток, Приморье, Россия
@dpsvl · 114,442
Telegram ranks this channel #20 of 80 here — alongside 79 others — read 21 August 2026
dpskontrol_125rus
@dpskontrol_125rus · 49,979
Telegram ranks this channel #21 of 90 here — alongside 89 others — read 25 August 2026
Новости Приморья | Владивостока
@novosti_primorye25 · 113,565
Telegram ranks this channel #28 of 87 here — alongside 86 others — read 21 August 2026
Newsbox24
@NBS24 · 46,946
Telegram ranks this channel #29 of 90 here — alongside 89 others — read 27 August 2026
Новости Владивостока и не только
@novosti_vdk · 58,447
Telegram ranks this channel #31 of 88 here — alongside 87 others — read 22 August 2026
VLNews25 l Новости Владивостока и Приморья
@vlnews25 · 48,128
Telegram ranks this channel #32 of 89 here — alongside 88 others — read 26 August 2026
Svodka25 l Новости Приморья и Владивостока
@svodka25 · 233,742
Telegram ranks this channel #41 of 70 here — alongside 69 others — read 21 August 2026
Право руля!
@primorchannel · 53,326
Telegram ranks this channel #42 of 93 here — alongside 92 others — read 24 August 2026
Вкратце | Владивосток
@vkratce_vld · 40,085
Telegram ranks this channel #44 of 79 here — alongside 78 others — read 30 August 2026
Новости VL.ru | Владивосток
@newsvlru · 87,758
Telegram ranks this channel #44 of 93 here — alongside 92 others — read 21 August 2026
Город В | Владивосток
@gorod_vl · 25,364
Telegram ranks this channel #45 of 93 here — alongside 92 others — read 13 September 2026
NEWS.VL | Владивосток и Приморье
@newsvlc · 66,272
Telegram ranks this channel #46 of 94 here — alongside 93 others — read 21 August 2026
Вести Приморье
@vestiprimorye · 24,785
Telegram ranks this channel #48 of 94 here — alongside 93 others — read 14 September 2026
PrimaMedia.Приморье
@primamedia · 40,983
Telegram ranks this channel #50 of 92 here — alongside 91 others — read 29 August 2026
Telegram Владивостока
@telega_vladivostok · 61,843
Telegram ranks this channel #58 of 94 here — alongside 93 others — read 24 August 2026
Владивосток Online
@Vladivostokl · 66,026
Telegram ranks this channel #60 of 84 here — alongside 83 others — read 26 August 2026
ПРИМОРСКИЙ РАЙ | Владивосток
@prim_ray · 25,318
Telegram ranks this channel #67 of 93 here — alongside 92 others — read 13 September 2026
Полиция Приморья
@prim_police · 18,827
Telegram ranks this channel #88 of 91 here — alongside 90 others — read 4 October 2026
Правительство Приморского края
@primorskyru · 34,825
Telegram ranks this channel #90 of 94 here — alongside 93 others — read 2 September 2026
Кожемяко | официально
@kozhemiakoofficial · 52,655
Telegram ranks this channel #91 of 95 here — alongside 94 others — read 24 August 2026

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

“«БЛОГ ВЛАДИВОСТОК»” (@blog_vladivostok), 10,467 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/blog_vladivostok.

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.