Telegram RegisterThe public register of Telegram
Telegram profile photo for 63 РЕГИОН

Channel

63 РЕГИОН

@reg063

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

63,488subscribers

-498 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-1001987048270
TypeChannel
Username@reg063
DescriptionЭксклюзивные новости Самарской области, Самары и Тольятти. Топ видео и события. По вопросам сотрудничества @ozzy_163
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live5 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/reg063

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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 5 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
@chp_samara/483136 Aug 2026, 15:17 UTC@reg063/24125 · this entry6 Aug 2026, 15:18 UTC1.00under a minute
@chp_samara/483186 Aug 2026, 22:06 UTC@reg063/24131 · this entry6 Aug 2026, 22:07 UTC1.00under a minute
@reg063/24132 · this entry7 Aug 2026, 03:50 UTC@chp_samara/483207 Aug 2026, 03:50 UTC1.00under a minute
@chp_samara/483247 Aug 2026, 09:02 UTC@reg063/24136 · this entry7 Aug 2026, 09:28 UTC1.0026 minutes
@reg063/24137 · this entry7 Aug 2026, 10:11 UTC@chp_samara/483267 Aug 2026, 10:11 UTC1.00under a minute
@reg063/24141 · this entry7 Aug 2026, 14:55 UTC@chp_samara/483317 Aug 2026, 14:56 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@chp_samara8 (8/8 hand-verifiable sample passed)1.00under a minute@chp_samara (53)
@tltvip5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (41)

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. 6 of the 6 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 30 comparable posts for this entry, running 5 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 5, the earliest publisher we hold is @chptlt. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · 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 4 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

63,48863,98663,7376 August 2026 — 63,986 subscribers7 August 2026 — 63,972 subscribers8 August 2026 — 63,963 subscribers9 August 2026 — 63,940 subscribers10 August 2026 — 63,923 subscribers11 August 2026 — 63,909 subscribers12 August 2026 — 63,901 subscribers14 August 2026 — 63,869 subscribers15 August 2026 — 63,870 subscribers16 August 2026 — 63,858 subscribers17 August 2026 — 63,844 subscribers18 August 2026 — 63,830 subscribers19 August 2026 — 63,798 subscribers20 August 2026 — 63,753 subscribers22 August 2026 — 63,758 subscribers24 August 2026 — 63,730 subscribers25 August 2026 — 63,714 subscribers26 August 2026 — 63,685 subscribers27 August 2026 — 63,673 subscribers28 August 2026 — 63,640 subscribers29 August 2026 — 63,618 subscribers30 August 2026 — 63,596 subscribers31 August 2026 — 63,582 subscribers1 September 2026 — 63,548 subscribers2 September 2026 — 63,524 subscribers3 September 2026 — 63,502 subscribers5 September 2026 — 63,488 subscribers6 August 20265 September 2026
27 measurements spanning 29 days, net -498. 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 63,413–64,061 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
5 Sept 2026, 03:4263,488-14
3 Sept 2026, 12:1863,502-22
2 Sept 2026, 09:2363,524-24
1 Sept 2026, 07:5963,548-34
31 Aug 2026, 04:3563,582-14
30 Aug 2026, 04:3563,596-22
29 Aug 2026, 08:0463,618-22
28 Aug 2026, 10:1363,640-33
27 Aug 2026, 08:0563,673-12
26 Aug 2026, 06:1763,685-29
25 Aug 2026, 04:5863,714-16
24 Aug 2026, 00:4863,730-28
22 Aug 2026, 11:1363,758+5
20 Aug 2026, 23:4663,753-45
19 Aug 2026, 20:3463,798-32
18 Aug 2026, 19:5663,830-14
17 Aug 2026, 20:1463,844-14
16 Aug 2026, 17:2563,858-12
15 Aug 2026, 04:2263,870+1
14 Aug 2026, 00:1663,869first reading

Engagement

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

ERR · 30 days
4.35%
avg views ÷ 63,488 subscribers
Avg views / post
2,760
367 posts measured
Reaction rate
0.652%
reactions ÷ views · ER floor
Posts in window
367
of 401 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 342 of 367 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 7 September 2026
Posts held401 (5 August 20267 September 2026)
Views total1,014,677
Reactions total6,212
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Sept 2026, 07:32 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,300
Videos
3,780
Links
16,400

Lifetime counters from Telegram’s own channel header, read 7 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
30m 28s
Average length
41s

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

6,716 reactions across 365 posts, in 37 distinct kinds. The most used accounts for 19.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,29519.3%
💊1,20017.9%
😁76711.4%
🥴3615.38%
👍3365.00%
😭3234.81%
🤯2734.06%
🔥2623.90%
😱2153.20%
🙏1902.83%
🕊1702.53%
🗿1512.25%
🙈1482.20%
🤨1392.07%
👏1372.04%
😢1362.03%
😐1141.70%
🦄991.47%
❤‍🔥520.774%
💔520.774%
17 further kinds2964.41%

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

Measured over the 401 most recent posts we hold, published 5 August 2026 to 7 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
1
of 401 we hold a reading for · 0.2%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @reg063. 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 401 most recent posts we hold for this entry, published 5 August 2026 to 7 September 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
0.748%
3 of 401 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
2,440
over 3 measured posts
Median views · rest
2,800
over 398 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
2Vtzqumt1xw118 August 202618 August 2026
2Vtzqutxp11118 August 202618 August 2026
2Vtzqvcpf4w125 August 202625 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 401 most recent posts we hold, published 5 August 2026 to 7 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

7 Sept 2026, 07:14 UTC335 views2 reactionsread 7 September 2026
Photo

🤯Штрафы за нарушения ПДД хотят утроить. Лихачей, которые нарушили правила более 50 раз за один год, призвали «награждать» увеличением размера штрафов в два раза. А тем, кому удалось собрать более 100 нарушений, материальное наказание нужно утроить, предложили в Национальном автомобильном союзе. Отмечается, что в среднем водители нарушают около пяти-шести раз за год, а количество нарушений с годами становится всё ме

🥴2

7 Sept 2026, 06:55 UTC531 views2 reactionsread 7 September 2026
Photo

Автомобильный мост открыли на границе России и КНДР. Движение по нему будет идти круглый год. Это позволит бизнесу нарастить объемы перевозок и сократить транспортные издержки. Мост проходит через реку Туманную (на территории России – Приморский край). Открыли объект по видеосвязи Мишустин и председатель кабмина КНДР. РИА Новости 🔴 ВАЖНО! Пока есть доступ подпишись на наши каналы👇 РЕГИОН 63 | ЧП САМАРА | КАНАЛ

😁2

7 Sept 2026, 06:29 UTC811 views5 reactionsread 7 September 2026
Photo

⚡️ ChatGPT начали БЛОКИРОВАТЬ в России — теперь сайт перестаёт открываться ещё до того, как успевает связаться с серверами OpenAI, сообщают СМИ. Раньше OpenAI сама не пускала пользователей с российских IP, а теперь соединение с chatgpt.com в российских сетях обрывается прямо при подключении. Из-за этого перестало нормально работать и приложение ChatGPT, оно использует тот же домен. При этом некоторые служебные адр

😁5

7 Sept 2026, 06:02 UTC≈1,120 views2 reactionsread 7 September 2026

⚡️В небе над Самарской областью сбили вражеские БПЛА ВСЕ ПОДРОБНОСТИ ПО БПЛА В РАДАР 63: https://max.ru/join/PJeQ7kvX9379UrBe4lSvNGOWhY2YEQ4cqcKLaqSs58w

🙏2

7 Sept 2026, 03:48 UTC≈1,800 views21 reactionsread 7 September 2026
Video

😅На полном баке… овса. Замечено в Тольятти. 🔴 ВАЖНО! Пока есть доступ подпишись на наши каналы👇 РЕГИОН 63 | ЧП САМАРА | КАНАЛ САМАРА | Канал Тольятти

14🔥6😁1

7 Sept 2026, 03:20 UTC≈1,920 views42 reactionsread 7 September 2026
Photo

🤯В Японии обвинили Россию за то что США сбросили на них ядерную бомбу По мнению профессора университета Васэда Аримы Тэцуо, Россия несёт ответственность за атомные бомбардировки — так как атомная бомба не была бы применена против Японии, если бы СССР не нарушил Ялтинское соглашение и не стал стремительно расширять своё влияние. Как отмечает профессор, в последние годы такая точка зрения стала распространяться и в С

🥴21💊14😁3🤯21👍1

6 Sept 2026, 20:53 UTC≈2,140 views15 reactionsread 7 September 2026
Photo

Дональд Трамп после доклада Уиткоффа и Кушнера сначала позвонит Владимиру Путину и только потом — Зеленскому Оба звонка должны состояться 7 сентября, перед ними президент США заслушает отчёт своих представителей об итогах переговоров в Москве и Киеве. Тем временем, целый ряд СМИ публикует предполагаемые детали нового мирного плана Трампа по Украине: — полное прекращение огня с обеих сторон — территориальные усту

💊73👍3😁1😐1

6 Sept 2026, 19:15 UTC≈2,410 views39 reactionsread 7 September 2026
Photo

Трамп заявил, что Луна принадлежит США Он опубликовал фотографию Луны, на которой располагается надпись «Луна наша» (The Moon is ours). ❗️ЕЖЕДНЕВНЫЙ МОНИТИРИНГ БПЛА В РАДАР 63 РЕГИОН

💊20😁14👍5

6 Sept 2026, 14:09 UTC≈2,740 views9 reactionsread 7 September 2026

Траты жителей Самарской области выросли до 48 тысячи рублей в месяц. Это средняя сумма, которую каждый местный житель оставляет в магазинах и сервисах, подсчитали аналитики РИА Новости по итогам первого полугодия 2026 года. Потребительский спрос в регионе вырос на 3,32% по сравнению с аналогичным периодом прошлого года. 🔴 ВАЖНО! Пока есть доступ подпишись на наши каналы👇 РЕГИОН 63 | ЧП САМАРА | КАНАЛ САМАРА | К

🥴9

6 Sept 2026, 12:20 UTC≈2,660 viewsread 7 September 2026

7 сентября по данным ГУ МЧС России по Самарской области, местами в регионе ожидается сильный дождь. ❗️Владельцам частных домов рекомендуют заранее подготовить дренажные системы для отвода дождевого стока. Спасатели призывают жителей воздержаться от поездок на личном автотранспорте, быть внимательными и осторожными. ГТРК Самара 🔴 ВАЖНО! Пока есть доступ подпишись на наши каналы👇 РЕГИОН 63 | ЧП САМАРА | КАНАЛ СА

6 Sept 2026, 11:10 UTC≈2,770 views7 reactionsread 7 September 2026
Photo

Злоупотребление острым может привести к раку желудка. Умеренно острый перец обычно безопасен и даже может быть полезен. Но если регулярно есть его в больших количествах, могут появиться изжога, боли и обострение гастрита или язвы. Врач советует здоровым людям не превышать 5–10 граммов свежего чили в день или половину чайной ложки сушёного. Острые магазинные соусы лучше ограничить парой чайных ложек и не есть каждый

🥴4😱3

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

@reg063 edited 1 post 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
16 August 2026
Most recent edit
16 August 2026

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.

ЧП САМАРА
@chp_samara · 252,545
#1
ТОЛЬЯТТИ
@tltvip · 149,813
#2
САМАРА
@samara_vip · 58,850
#3
ЧП ТОЛЬЯТТИ
@chptlt · 97,991
#4
Подслушано Самара🐐
@psamara · 40,532
#5
Самара ДТП | samara.dtp.official
@samaradtp · 100,453
#6
ТОЛЬЯТТИ
@tlt_63ru · 113,400
#7
Самара с огоньком
@samartop · 63,625
#8
ТОЛЬЯТТИ ОНЛАЙН
@tlt_online · 23,201
#9
Автолюбители 63
@autoclub163 · 3,050
#10
Самара №1
@samaratg01 · 25,083
#11
63.RU | НОВОСТИ САМАРЫ | ТОЛЬЯТТИ
@news63ru · 59,085
#12
Самара и Самарская губерния
@live_63 · 37,821
#13
Убежище Самара
@samara · 58,800
#14
Красоты Самарской Губернии
@krasoty63 · 13,619
#15
Воронцова вещает 🦊
@vorontsova63ru · 31,053
#16
СЫЗРАНЬ
@syzranvip · 19,353
#17
САМАРСКОЕ ОБОЗРЕНИЕ
@i63media · 11,668
#18
Новости Самары и Области
@samara_smi · 92,503
#19
КП Самара. Новости региона
@truekpru63 · 8,742
#20
Типичный Тольятти | Новости
@typ_tlt · 23,412
#21
ЧАПАЕВСК life
@chvk63 · 14,699
#22
Штефан знает!
@shtefanksenia · 25,916
#23
МЧС Самарской области
@mchs_samara · 9,292
#24
Самарская область
@SamarOblast · 7,203
#25
Привет со Дна 🇸🇱 Крылья Советов Самара
@privetsodna · 7,128
#26
Коммерсантъ Волга
@kommersant_volga · 7,315
#27
САМАРА | 450media
@samara450media · 10,586
#28
Самара Новости | Новости Самары и Самарской области
@samarap · 15,321
#29
ГТРК САМАРА
@gtrksamara · 13,332
#30
Главный по новостям Тольятти
@protlt · 3,549 (as read 21 August 2026)
#31
ГУ МВД России по Самарской области
@guvd63 · 4,047
#32
Александр Хинштейн
@Hinshtein · 216,370
#33
САМАРА life
@samara_life63 · 19,230
#34
Куйбышевский|Самара
@kuiblife · 10,498
#35
Новости Чапаевска
@chapa_63 · 4,575
#36
Координаты Самара
@koordinaty_smr · 3,987
#37
БАНДИТСКАЯ САМАРА
@banditskayasamara · 28,629
#38
Вести с Дворянской
@adm_samara · 2,369
#39
Куда Пойти? | Афиша Тольятти
@afisha_tlt · 49,980
#40
SMR_TODAY | Самара
@today_smr · 6,503
#41
Как-то так | Тольятти
@togliatty24 · 6,465
#42
ЕЩЁ Самара
@eshcho_samara · 4,289
#43
Куйбышевский/Волгарь/Сухая Самарка
@stoshka_lives_matter · 8,698
#44
Самара Онлайн 24
@samara24onl · 9,750
#45
ВОЛГА НЬЮС - Новости Самары
@vninform · 2,489
#46
Чёткий Регион
@region63ru · 1,731
#47
СУ СК России по Самарской области
@su_skr63 · 2,971
#48
Прокуратура Самарской области
@samara_proc · 2,813
#49
В Самаре и точка
@vsamareitochka63 · 6,268
#50
ЧП и ДТП | ТОЛЬЯТТИ
@dtpvtlt · 5,519
#51
Николай Ренц
@renc_nikolay · 1,283
#52
Вся Самара с колёс 🚗
@Off_Road63 · 1,778
#53
450media | LIVE
@live450media · 1,053
#54
Самара-ГИС
@samaragisnews · 4,814
#55
Самара
@vsamare · 15,102
#56
САМАРА И ОБЛАСТЬ.
@reg_63 · 4,876
#57
Сочно о Самаре
@samarasochno · 1,628
#58
Ретро Самара
@samararetro · 12,931
#59
Ретро Тольятти
@tltretro · 15,965
#60
ПФК «Крылья Советов»
@fckssamara_official · 37,726
#61
Красоты Тольятти и Самарской области
@tlt_view · 44,075
#62
ФК «Акрон» Тольятти
@fcakron · 24,727
#63
Засекин
@zasekinru · 5,635
#64
Мемная Самара
@mem_samara · 1,927
#65
ХК «Лада» Тольятти
@hc_lada · 20,101
#66
Госавтоинспекция Самарской области
@Gosavtoinspektsiya63 · 2,159
#67
Волга, Ромб и Два Крыла🇸🇱
@volga_romb · 3,828
#68
Саров. тот самый Абзац
@sarovden · 3,566
#69
Кот нюхает цветы
@ferrum1229 · 403
#70
ТК Гуд’ОК
@gudokmall · 11,051
#71

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

САМАРА
@samara_vip · 58,850
Telegram ranks this channel #2 of 67 here — alongside 66 others — read 22 August 2026
ЧП ТОЛЬЯТТИ
@chptlt · 97,991
Telegram ranks this channel #4 of 29 here — alongside 28 others — read 16 August 2026
ТОЛЬЯТТИ
@tltvip · 149,813
Telegram ranks this channel #4 of 29 here — alongside 28 others — read 12 August 2026
Подслушано Самара🐐
@psamara · 40,532
Telegram ranks this channel #5 of 74 here — alongside 73 others — read 30 August 2026
ЧП САМАРА
@chp_samara · 252,545
Telegram ranks this channel #5 of 45 here — alongside 44 others — read 11 August 2026
ТОЛЬЯТТИ
@tlt_63ru · 113,400
Telegram ranks this channel #6 of 31 here — alongside 30 others — read 14 August 2026
Куда Пойти? | Афиша Тольятти
@afisha_tlt · 49,980
Telegram ranks this channel #7 of 45 here — alongside 44 others — read 25 August 2026
Новости Самары и Области
@samara_smi · 92,503
Telegram ranks this channel #9 of 66 here — alongside 65 others — read 17 August 2026
Самара и Самарская губерния
@live_63 · 37,821
Telegram ranks this channel #10 of 73 here — alongside 72 others — read 31 August 2026
Самара с огоньком
@samartop · 63,625
Telegram ranks this channel #10 of 74 here — alongside 73 others — read 21 August 2026
Убежище Самара
@samara · 58,800
Telegram ranks this channel #12 of 75 here — alongside 74 others — read 22 August 2026
Самара ДТП | samara.dtp.official
@samaradtp · 100,453
Telegram ranks this channel #13 of 62 here — alongside 61 others — read 15 August 2026
63.RU | НОВОСТИ САМАРЫ | ТОЛЬЯТТИ
@news63ru · 59,085
Telegram ranks this channel #21 of 90 here — alongside 89 others — read 22 August 2026
Воронцова вещает 🦊
@vorontsova63ru · 31,053
Telegram ranks this channel #40 of 93 here — alongside 92 others — read 6 September 2026

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

“63 РЕГИОН” (@reg063), 63,488 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/reg063.

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.