Telegram RegisterThe public register of Telegram

Channel

Backender | CMD

@backender_it

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

6,398subscribers

-5 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001712111703
TypeChannel
Username@backender_it
DescriptionСамые полезные и интересные курсы для бэкенд разработчиков! Ссылка: @Portal_v_IT Сотрудничество: @oleginc, @tatiana_inc Канал на бирже: https://telega.in/c/backender_it
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/backender_it

Topic

Education — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 96% 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. 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
@backender_it/4650 · this entry4 Aug 2026, 08:07 UTC@archivator_it/56314 Aug 2026, 16:07 UTC0.998.0 hours
@archivator_it/56304 Aug 2026, 11:07 UTC@backender_it/4652 · this entry4 Aug 2026, 16:07 UTC0.985.0 hours
@archivator_it/56161 Aug 2026, 08:07 UTC@backender_it/4642 · this entry1 Aug 2026, 11:07 UTC0.983.0 hours
@archivator_it/56325 Aug 2026, 08:07 UTC@backender_it/4654 · this entry5 Aug 2026, 11:07 UTC0.983.0 hours
@backender_it/4653 · this entry5 Aug 2026, 08:07 UTC@archivator_it/56345 Aug 2026, 16:07 UTC0.988.0 hours
@archivator_it/56366 Aug 2026, 11:07 UTC@backender_it/4658 · this entry6 Aug 2026, 16:07 UTC0.985.0 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@archivator_it12 (8/8 hand-verifiable sample passed)0.985.0 hours@archivator_it (84)
@it_pirate_tg10 (8/8 hand-verifiable sample passed)0.975.0 hoursthis entry (82)

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

What this cannot establish

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

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 3 of the 10 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 23 comparable posts for this entry, running 31 July 2026 to 7 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 3, the earliest publisher we hold is @backender_it — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, last confirmed 7 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 2 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

6,3986,4036,400.57 August 2026 — 6,403 subscribers7 August 2026 — 6,403 subscribers11 August 2026 — 6,398 subscribers7 August 202611 August 2026
3 measurements spanning 4 days, net -5. 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 6,397–6,404 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 02:576,398-5
7 Aug 2026, 18:356,403no change
7 Aug 2026, 03:176,403first reading

Engagement

33 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.81%
avg views ÷ 6,398 subscribers
Avg views / post
180
33 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
33
of 33 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held33 (31 July 202611 August 2026)
Views total5,927
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:11 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
3,610
Videos
11
Links
3,630

Lifetime counters from Telegram’s own channel header, read 12 August 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
4s
Average length
4s

Measured directly from 1 video 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

11 Aug 2026, 09:24 UTC132 viewsread 12 August 2026
Video

👩‍💻 Всем программистам посвящается! Вот 14 авторских обучающих IT каналов по самым востребованным областям программирования: Выбирай своё направление: 👩‍💻 Python — t.me/python_ready 🤔 InfoSec & Хакинг — t.me/hacking_ready 🖥 SQL & Базы Данных — t.me/sql_ready 👩‍💻 IT Новости — t.me/it_ready 🤖 AI & ML — t.me/neuro_ready 👩‍💻 Frontend — t.me/frontend_ready 👩‍💻 C/C++ — https://t.me/cpp_ready 👩‍💻 C# & Unity — t.

10 Aug 2026, 16:07 UTC162 viewsread 12 August 2026
Photo

🌎 Docker Deep Dive: Zero to Docker in a single book (2025) ❔ Чему вы научитесь: 🔵 понимать устройство образов: слои, кэш, манифесты, мультиархитектурные сборки; 🔵 писать Dockerfile и собирать компактные образы через многоступенчатые сборки; 🔵 разбираться в изоляции контейнеров: namespaces, cgroups, работа рантайма; 🔵 настраивать сети и тома, связывать контейнеры между собой; 🔵 подписывать образы, сканировать их на у

10 Aug 2026, 11:07 UTC156 viewsread 12 August 2026
Photo

🌎 MongoDB in Action, Third Edition: Building on the Atlas Data Platform (2025) ❔ Чему вы научитесь: 🔵 проектировать документные схемы: вложение против ссылок, работа с денормализацией; 🔵 писать запросы и агрегационные конвейеры вместо привычного SQL; 🔵 подбирать индексы под нагрузку и читать планы выполнения; 🔵 разворачивать и эксплуатировать кластер в Atlas; 🔵 настраивать репликацию и шардирование, выбирать ключ ша

10 Aug 2026, 08:07 UTC143 viewsread 12 August 2026
Photo

🌎 Electrical engineering without prior knowledge: Understand the basics within 7 days (2020) ❔ Чему вы научитесь: 🔵 оперировать базовыми величинами: напряжение, ток, сопротивление, мощность; 🔵 применять закон Ома и правила Кирхгофа к последовательным и параллельным цепям; 🔵 различать постоянный и переменный ток, понимать частоту и действующее значение; 🔵 разбираться в назначении резисторов, конденсаторов и катушек в

9 Aug 2026, 16:07 UTC143 viewsread 12 August 2026
Photo

🌎 Hacks, Leaks, and Revelations: The Art of Analyzing Hacked and Leaked Data (2024) ❔ Чему вы научитесь: 🔵 безопасно принимать и хранить чувствительные датасеты, работая в изолированном окружении; 🔵 разбирать сырые дампы: архивы, логи, выгрузки БД, почтовые ящики; 🔵 искать по большим объёмам данных через CLI-инструменты и grep-подобные конвейеры; 🔵 писать скрипты на Python для парсинга и структурирования нестандартн

9 Aug 2026, 11:07 UTC147 viewsread 12 August 2026
Photo

🌎 TypeScript Cookbook: Real World Type-Level Programming (2023) ❔ Чему вы научитесь: 🔵 писать условные и сопоставляемые типы, выводить типы через infer; 🔵 работать с дженериками и ограничениями, не скатываясь в any; 🔵 строить type guards и дискриминируемые объединения; 🔵 типизировать сторонние библиотеки и писать декларации; 🔵 настраивать tsconfig и режимы строгости под проект; 🔵 разбирать ошибки компилятора, а не г

9 Aug 2026, 08:07 UTC141 viewsread 12 August 2026
Photo

🌎 Canva Cookbook: Unlock the full potential of Canva with practical recipes for creating stunning visuals effortlessly (2025) ❔ Чему вы научитесь: 🔵 собирать макеты под конкретные форматы: посты, сторис, презентации, печать; 🔵 работать с типографикой, сетками и выравниванием внутри редактора; 🔵 заводить brand kit — шрифты, палитру, логотипы — и держать материалы в едином стиле; 🔵 использовать шаблоны как основу, а н

8 Aug 2026, 16:07 UTC161 viewsread 12 August 2026
Photo

🌎 RESTful API Design Principles: A practical guide to the architecture of the web (2025) ❔ Чему вы научитесь: 🔵 проектировать ресурсы и URI-структуру вместо RPC-вызовов в обёртке HTTP; 🔵 корректно применять методы, коды состояния и семантику идемпотентности; 🔵 работать с кэшированием, условными запросами и заголовками HTTP; 🔵 версионировать API и развивать контракт без поломки клиентов; 🔵 продумывать пагинацию, филь

8 Aug 2026, 11:07 UTC160 viewsread 12 August 2026
Photo

🌎 CockroachDB: The Definitive Guide: Distributed Data at Scale, 2nd Edition (2025) ❔ Чему вы научитесь: 🔵 разворачивать кластер и понимать устройство слоёв: ranges, replicas, Raft; 🔵 проектировать схему и первичные ключи так, чтобы не собирать hotspot; 🔵 работать с распределёнными транзакциями и уровнями изоляции; 🔵 размещать данные по регионам и настраивать survival goals; 🔵 читать планы запросов и оптимизировать р

8 Aug 2026, 08:07 UTC151 viewsread 12 August 2026
Photo

🌎 The Nature of Code: Simulating Natural Systems with JavaScript. Daniel Shiffman (2024) ❔ Чему вы научитесь: 🔵 описывать движение через векторы, силы и ускорение; 🔵 моделировать физику: гравитацию, трение, пружины, столкновения; 🔵 строить осцилляции и тригонометрические траектории; 🔵 генерировать фракталы и рекурсивные структуры; 🔵 писать автономных агентов и симуляции роевого поведения; 🔵 применять клеточные автом

7 Aug 2026, 16:07 UTC173 viewsread 12 August 2026
Photo

🌎 Machine Learning Q and AI: 30 Essential Questions and Answers on Machine Learning and AI (2024) ❔ Чему вы научитесь: 🔵 разбираться в тонких местах нейросетей: эмбеддинги, инициализация, нормализация; 🔵 понимать устройство трансформеров и механизма внимания; 🔵 выбирать способ дообучения больших моделей и оценивать его стоимость; 🔵 корректно строить валидацию и доверительные интервалы для метрик; 🔵 объяснять, почему

7 Aug 2026, 11:07 UTC175 viewsread 12 August 2026
Photo

🌎 Mastering MySQL Administration: High Availability, Security, Performance, and Efficiency (2024) ❔ Чему вы научитесь: 🔵 настраивать репликацию и отказоустойчивые топологии, планировать failover; 🔵 разбирать медленные запросы: EXPLAIN, индексы, план выполнения; 🔵 тюнить InnoDB — буферный пул, журналы, параметры конфигурации; 🔵 закрывать доступ: привилегии, шифрование соединений, аудит; 🔵 выстраивать резервное копиро

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

Citation-graph rank

Citation-graph rank — 1,129,217 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“Backender | CMD” (@backender_it), 6,398 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/backender_it.

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.