Telegram RegisterThe public register of Telegram
Telegram profile photo for БАZA Краснодар

Channel

БАZA Краснодар

@BAZA_Krasnodar1

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

144subscribers

-12 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002248064755
TypeChannel
Username@BAZA_Krasnodar1
CreatedBetween 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/BAZA_Krasnodar1

Topic

Other / unclassifiable — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts 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
@BAZA_Krasnodar1/448 · this entry1 May 2026, 14:40 UTC@baza_novoross/6311 May 2026, 14:40 UTC1.00under a minute
@baza_novoross/63417 May 2026, 08:36 UTC@BAZA_Krasnodar1/451 · this entry17 May 2026, 08:38 UTC1.002 minutes
@BAZA_Krasnodar1/454 · this entry28 May 2026, 15:43 UTC@baza_novoross/63728 May 2026, 15:43 UTC1.00under a minute
@baza_novoross/63828 May 2026, 15:43 UTC@BAZA_Krasnodar1/455 · this entry28 May 2026, 15:43 UTC1.00under a minute
@BAZA_Krasnodar1/459 · this entry1 Jun 2026, 12:40 UTC@baza_novoross/6421 Jun 2026, 12:40 UTC1.00under a minute
@baza_novoross/6433 Jun 2026, 10:42 UTC@BAZA_Krasnodar1/460 · this entry3 Jun 2026, 10:42 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@baza_novoross11 (8/8 hand-verifiable sample passed)1.00under a minute@baza_novoross (6–5)
@BAZA_klub8 (8/8 hand-verifiable sample passed)1.00under a minute@BAZA_klub (7–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 13 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 13 comparable posts for this entry, running 29 April 2026 to 1 July 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).

Of the group of 3 channels, the one whose matching posts we hold earliest is @BAZA_Krasnodar1 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 11 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

1441561507 August 2026 — 156 subscribers8 August 2026 — 156 subscribers16 August 2026 — 155 subscribers24 August 2026 — 154 subscribers31 August 2026 — 152 subscribers10 September 2026 — 151 subscribers19 September 2026 — 150 subscribers4 October 2026 — 149 subscribers14 October 2026 — 148 subscribers29 October 2026 — 147 subscribers4 November 2026 — 145 subscribers12 November 2026 — 144 subscribers7 August 202612 November 2026
12 measurements spanning 97 days, net -12. 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 142–158 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 18:21144-1
4 Nov 2026, 21:46145-2
29 Oct 2026, 13:10147-1
14 Oct 2026, 00:16148-1
4 Oct 2026, 10:16149-1
19 Sept 2026, 03:41150-1
10 Sept 2026, 06:38151-1
31 Aug 2026, 07:04152-2
24 Aug 2026, 15:28154-1
16 Aug 2026, 02:47155-1
8 Aug 2026, 18:31156no change
7 Aug 2026, 20:22156first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 1 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
22s
Average length
11s

Measured directly from 2 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.

Recent posts

1 Jul 2026, 10:23 UTC25 viewsread 8 August 2026
Photo

Твой июль в бизнес-клубе БAZA: масштаб, нетворкинг и мощное окружение ⚡️ Новый месяц - это новые цели, сильные инсайты и встречи, которые меняют масштаб твоего бизнеса. Мы подготовили для тебя насыщенную программу: от бизнес-игр Cashflow и инвестиционных сред до выездных мастермайндов и активного отдыха. 🗓 Полное расписание со всеми датами и городами уже на афише. стать резидентом • записаться на мероприятия • БА…

19 Jun 2026, 09:31 UTC35 viewsread 8 August 2026
Photo

🎲CASHFLOW 202 В АНАПЕ🎲 (Только опытные игроки) 🗓 2 июля 🕐 18:30 Ведущий: Виталий Диденко - бизнес тренер, консультант по стратегии личностного роста, создатель бизнес клуба «БАZА». Играйте в Cashflow вместе с опытными предпринимателями и укрепите своё бизнес-мышление в компании нашего бизнес-клуба. В программе: 1️⃣ Нетворкинг; 2️⃣ Финансовые стратегии; 3️⃣ Работа над ошибками в управлени с деньгами; 4️⃣ Расширен…

11 Jun 2026, 11:40 UTC29 viewsread 8 August 2026
Photo

Открытая встреча Бизнес Клуба «БАZA» в Новороссийске! 🗓 25 июня 🕔 17:00 Что вас ждёт: ◾️Нетворкинг с единомышленниками ◾️Презентация каждого участника ◾️Выступление тайного гостя (имя раскроем позже 😉) ◾️Живое общение и обмен опытом ⚠ Количество мест ограничено! Не упустите возможность найти полезные знакомства и вдохновение для своего бизнеса! РЕГИСТРАЦИЯ • стать резидентом • записаться на мероприятия • …

3 Jun 2026, 10:42 UTC26 viewsread 8 August 2026
Photo

Cashflow 101 в АНАПЕ 🗓️ 9 июня в 18:00 Это не игра. Это — личный финансовый план, который вы составите по итогу. Что вы получите в результате: ◾️Диагностику: Поймете свои ошибки в обращении с деньгами. ◾️Инструменты: Узнаете 3-4 рабочие стратегии инвестирования. ◾️Опыт: Совершите все финансовые ошибки в игре, а не в жизни. ◾️Окружение: Знакомства с теми, кто думает как инвестор. Готовы сделать первый шаг? РЕГИС…

1 Jun 2026, 12:40 UTC15 viewsread 8 August 2026
Photo

🤖 ИСКУССТВЕННЫЙ ИНТЕЛЛЕКТ В БИЗНЕСЕ 6 июня состоится закрытый практический мастер-класс для резидентов бизнес-клуба БАZА. Сегодня про искусственный интеллект говорят все. Но одно дело слышать про него в новостях или смотреть ролики в интернете, и совсем другое — реально внедрять его в работу своей компании и получать результат. Поэтому мы решили провести не лекцию и не очередную дискуссию на тему будущего технолог…

1 Jun 2026, 07:49 UTC16 viewsread 8 August 2026
Photo

Делимся с вами календарем событий на этот месяц. ⚡️ НАПОМИНАЕМ О ФОРМАТАХ НАШИХ ВСТРЕЧ: Закрытые мероприятия - эксклюзивно для действующих резидентов бизнес-клуба «БАZA». Глубокая проработка, мастермайнды, обмен опытом «без галстуков» и синергия сильных. Открытые мероприятия - встречи, на которые мы с радостью приглашаем всех желающих! Если вы хотите познакомиться с клубом, прокачать свои навыки и найти новых парт…

28 May 2026, 15:43 UTC21 viewsread 8 August 2026
Video

Екатерина Волкова, Бизнес клуб «БАZA» поздравляет тебя с днем рождения. 🎉 Желаем достижения новых высот, невероятных творческих взлётов и неиссякаемого вдохновения. Никогда не останавливайся на достигнутом и пусть тебя всегда окружает лучшее, поддерживающее и сильное окружение. С днем рождения 🥳

28 May 2026, 15:43 UTC24 viewsread 8 August 2026
Video

Павел Бедаков, Бизнес клуб «БАZA» поздравляет тебя с днем рождения. 🎊 Желаем новых грандиозных карьерных высот, масштабных проектов, в которые веришь и горишь делом, и, конечно, мощных достижений. Пусть каждый твой шаг ведёт к успеху, бизнес-интуиция никогда не подводит, а рядом всегда будет сильная команда единомышленников. Только вперед, к новым вершинам. С днем рождения 🎂

17 May 2026, 08:38 UTC27 viewsread 8 August 2026
Photo

Открытая встреча Бизнес Клуба «БАZA» в Новороссийске! 🗓 21 мая 🕔 17:00 Что вас ждёт: ◾️Нетворкинг с единомышленниками ◾️Презентация каждого участника ◾️Выступление тайного гостя (имя раскроем позже 😉) ◾️Живое общение и обмен опытом ⚠ Количество мест ограничено! Не упустите возможность найти полезные знакомства и вдохновение для своего бизнеса! РЕГИСТРАЦИЯ Наш сайт • стать резидентом • записаться на меропри…

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

Mentions

Named by 3 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.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 November 2026 — this entry's latest reading, not the date you are reading this.

“БАZA Краснодар” (@BAZA_Krasnodar1), 144 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/BAZA_Krasnodar1.

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.