Telegram RegisterThe public register of Telegram
Telegram profile photo for АЗАТ АБИТОВ🔈🔉🔊

Channel

АЗАТ АБИТОВ🔈🔉🔊

@azat_abitov

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

606subscribers

-3 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-1001673205371
TypeChannel
Username@azat_abitov
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 November 2026
Measurements held5
Confirmed unchanged5 times, most recently 14 November 2026
On Telegramt.me/azat_abitov

Topic

Music — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@azat_abitov/125 · this entry10 Dec 2025, 05:19 UTC@GulsirenAbdullina/21311 Dec 2025, 07:38 UTC1.0026 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
@GulsirenAbdullina6 (6/6 hand-verifiable sample passed)1.0015 hoursthis entry (5–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 0 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 14 comparable posts for this entry, running 11 February 2024 to 1 April 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 2 channels, the one whose matching posts we hold earliest is @azat_abitov — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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 2 registered channels linked by matching posts. 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

606609607.57 August 2026 — 609 subscribers8 August 2026 — 609 subscribers16 September 2026 — 608 subscribers29 September 2026 — 607 subscribers17 October 2026 — 606 subscribers7 August 202617 October 2026
5 measurements spanning 70 days, net -3. 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 606–609 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Oct 2026, 05:38606-1
29 Sept 2026, 21:35607-1
16 Sept 2026, 02:55608-1
8 Aug 2026, 03:04609no change
7 Aug 2026, 20:20609first reading

Engagement

20 posts held, back to 14 January 2024 — 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 20 posts for this entry, the most recent from 1 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
6m 03s
Average length
30s

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

215 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 36.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7936.7%
🔥7635.3%
❤4219.5%
🎉156.98%
😍20.93%
👏10.465%

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

Measured over the 20 most recent posts we hold, published 14 January 2024 to 1 April 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.

Recent posts

1 Apr 2026, 11:36 UTC278 views2 reactionsread 8 August 2026
Video

ЯР ЧАЛЛЫ! Это не шутка! Концертка бер атна калып бара, ә билетлар әле күп!🤷‍♂️ Без сезне сагынып киләбез!Сез дә сагынган булсагыз, тизерәк билетлар алыгыз да концертка килегез!❤️ Күрешербез дип өметләнеп калабыз!🤞 Билеты: https://bileton.ru/events/gulsiren-abdullina-azat-abitov-239532

🔥1😍1

16 Feb 2026, 06:47 UTC516 views3 reactionsread 8 August 2026
Forwarded from @GulsirenAbdullinaVideo

Гашыйклар көне белән!❤️ «МАТУР ҖЫР» @oscar_usmanov көе🎶 Сания Әхмәтҗанова сүзләре📜 @dinar787 аранжировкасы📀 @adelkhzstudio тавыш яздыру🎙️ Җыр бүгеннән барлык музыкаль площадкаларда😍 Тыңлый аласыз монда ⬇️ https://band.link/matur_zhyr

❤2😍1

4 Feb 2026, 08:36 UTC≈1,470 views6 reactionsread 8 August 2026
Video

Первый город нашего тура - Альметьевск! Для нас это один и самых важных концертов этого года! Поэтому приглашаем всех наших дорогих зрителей и друзей на свой большой концерт! Мы приготовили для Вас много интересного и прекрасного!❤️ Увидимся 17 февраля в Альметьевске,ДК Нефтьче❤️ Ссылки на билеты: 🎫shadan.media - https://shadan.media/abitov?utm_source=ig&utm_medium=social&utm_content=link_in_bio#event/2599162 🎫Би…

🔥4❤2

25 Jan 2026, 13:01 UTC821 views9 reactionsread 8 August 2026
Video

17 ФЕВРАЛЯ | АЛЬМЕТЬЕВСК | ДК НЕФТЬЧЕ Билеты можно найти во всех наших соцсетях, а также на сайтах bileton.ru , kassir.ru и VK Билеты 🎫 Прямая ссылка на концерт: https://nabchelny.kassir.ru/koncert/azat-abitov-i-gulsiren—abdullina-g-elabuga p.s. Вы очень сильно нас поддержите если отправите это приглашение своим друзьям и родным из города Альметьевск❤️

🔥9

12 Dec 2025, 08:32 UTC≈1,070 views9 reactionsread 8 August 2026
Photo

Премьера! "Булды инде" https://band.link/Buldy_inde

🔥9

10 Dec 2025, 05:19 UTC≈1,020 views10 reactionsread 8 August 2026
Photo

Әлмәттә яшәүче тамашачыларыбыз, без сезне көтеп калабыз! ❤️ Билетлар сатуга чыкты👇 https://shadan.media/concert#event/2599162

❤7🔥3

18 Nov 2025, 18:00 UTC≈2,830 views9 reactionsread 8 August 2026
Photo

Иң көтелгән яңалыгыбыз белән бүлешәбез!🔥 Ниһаять, 5 елдан соң янәдән Казанда концерт! Дуслар, 24 февральны һәм сезне концертыбызда түземсезлек белән көтәбез!!! Билетлар kassir.ru сайтында, кассада һәм таратучыларда. Прямая ссылка на билеты: https://kzn.kassir.ru/koncert/kts-chulpan/azat-abitov-i-gulsiren--abdullina_2026-02-24

🔥6❤3

27 Oct 2025, 09:15 UTC≈1,980 views1 reactionsread 8 August 2026
Video

Түбән Камада булачак концертка аз гына вакыт калып бар, шуңа күрә билетлар алырга самое время дуслар!😉 Все билеты в bileton.ru https://bileton.ru/events/gulsiren-abdullina-azat-abitov-219363 Ә бәлки пригласительныйлар берәр ничек разыграть итергәдер?!🤔

🔥1

15 Oct 2025, 12:06 UTC≈2,160 views11 reactionsread 8 August 2026
Video

Подготовка к концертам продолжается! 🤩 Ближайшие концерты: Кукмор - 27 октября https://shadan.media/concert#event/2555897 Нижнекамск - 14 ноября https://bileton.ru/events/gulsiren-abdullina-azat-abitov-219363 p.s. график на 2026 год скоро выложим!

🔥11

6 Oct 2025, 05:13 UTC≈1,260 views7 reactionsread 8 August 2026
Video

И в Казани и в Челнах и в Нижнекамске и в других наших любимых городах наши концерты будут обязательно, мы сильно готовимся!❤️ Но обо всем по порядку, потому что уже 27 ОКТЯБРЯ У НАС КОНЦЕРТ В КУКМОРЕ! Всех приглашаем,всех ждем, потому что именно от Вас, дорогие зрители, зависит, будут у нас концерты или нет! Билеты по ссылке: https://shadan.media/concert#event/2555897 и на кассе РДК Кукмор.

❤4🔥3

3 Oct 2025, 15:48 UTC≈1,860 views32 reactionsread 8 August 2026
Video

Video, posted without a caption

🔥24👍8

29 Sept 2025, 15:13 UTC≈1,280 views6 reactionsread 8 August 2026
Video

Фотосессия мизгелләре. Ничек сезгә образлар? Стилист: https://t.me/+Sos7yB0IR2hhMmIy Образлар: https://t.me/stilman_magazine

👍4🔥2

Showing the 12 most recent of 20 posts we hold for @azat_abitov. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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 17 October 2026 — this entry's latest reading, not the date you are reading this.

“АЗАТ АБИТОВ🔈🔉🔊” (@azat_abitov), 606 subscribers as measured 17 October 2026. Telegram Register, tgregister.com/channel/azat_abitov.

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.