Telegram RegisterThe public register of Telegram
Telegram profile photo for Заметки Бэкендера

Channel

Заметки Бэкендера

@backend_it

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

18,622subscribers

-601 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-1001507300353
TypeChannel
Username@backend_it
DescriptionПритягиваем все самое необходимое из Backend технологий. Ссылка: @Portal_v_IT Сотрудничество: @oleginc Канал на бирже: telega.in/c/backend_it
CreatedBetween 1 July 2021 and 31 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/backend_it

Topic

Education — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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.

Growth

18,62219,22318,922.57 August 202618 November 2026
64 measurements spanning 104 days, net -601. 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 18,532–19,313 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
18 Nov 2026, 23:0718,622-22
15 Nov 2026, 23:2018,644-29
12 Nov 2026, 12:0718,673-15
10 Nov 2026, 11:1818,688-14
7 Nov 2026, 20:4518,702-3
6 Nov 2026, 19:4918,705-7
5 Nov 2026, 17:4118,712-9
4 Nov 2026, 15:5518,721-1
3 Nov 2026, 16:4518,722-5
2 Nov 2026, 20:0718,727-10
1 Nov 2026, 21:0618,737-6
31 Oct 2026, 17:5018,743-6
30 Oct 2026, 16:2618,749-12
29 Oct 2026, 14:2118,761-11
28 Oct 2026, 12:5018,772-11
27 Oct 2026, 13:3118,783-2
26 Oct 2026, 13:1018,785-8
25 Oct 2026, 09:5518,793-5
24 Oct 2026, 11:0618,798-3
23 Oct 2026, 12:2018,801first reading

Engagement

116 posts held, back to 26 July 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 100 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.93%
avg views ÷ 18,622 subscribers
Avg views / post
731
57 posts measured
Reaction rate
0.222%
reactions ÷ views · ER floor
Posts in window
57
of 116 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 18 of 57 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 20 November 2026
Posts held116 (26 July 2026 – 20 November 2026)
Views total41,665
Reactions total28
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Nov 2026, 07:33 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,710
Videos
≈18
Links
≈3,740

Lifetime counters from Telegram’s own channel header, read 21 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
55s
Average length
14s

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

59 reactions across 39 posts, in 3 distinct kinds. The most used accounts for 40.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2440.7%
🔥2033.9%
❤1525.4%

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

Measured over the 116 most recent posts we hold, published 26 July 2026 to 20 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
3.45%
4 of 116 posts carry an ad marker
Regulatory tokens
4
posts carrying an erid · 4 distinct tokens
Median views · ads
692
over 4 measured posts
Median views · rest
766
over 112 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
2Vtzqunnr3x120 November 202620 November 2026
2VtzqwKjJqt15 November 20265 November 2026
2VtzqwcJy2v17 November 20267 November 2026
2W5zFGMLB5T117 August 202617 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 116 most recent posts we hold, published 26 July 2026 to 20 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: 2 of 57 posts held from the last 30 days (3.51%) 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).

20 Nov 2026, 15:03 UTC343 viewsread 21 November 2026
Advertisementerid 2Vtzqunnr3xVideo

А вы знали, что у VK есть полезное сообщество для бэкенд-разработчиков ? Инженеры компании рассказывают о том, как работает VK изнутри, что происходит за интерфейсами, когда миллионы пользователей одновременно отправляют сообщения, загружают фото и смотрят клипы. В канале разбирают работу всех сервисов — от VK Play до Tarantool. Делятся подходами к масштабированию, оптимизации и новым архитектурным решениям. Открыто…

20 Nov 2026, 14:27 UTC401 views3 reactionsread 21 November 2026
Photo

PostgreSQL 19: меньше костылей, умнее фоновые процессы и новые возможности SQL PostgreSQL 19 приносит изменения, которые могут заметно упростить жизнь разработчикам и администраторам баз данных. Меньше ручной работы, улучшенные фоновые процессы и встроенные механизмы, способные заменить привычные обходные решения. В этой статье подробно разбираем нововведения PostgreSQL 19: изменения в обслуживании таблиц, синхрони…

❤3

19 Nov 2026, 16:21 UTC569 viewsread 21 November 2026
Photo

Почему потоки Node.js съедают всю память и как Backpressure решает эту проблему При копировании файла размером 2 ГБ в медленный поток записи потребление памяти достигло 2077 МБ. Но правильная обработка write() позволила снизить его до 85 МБ — почти в 24 раза меньше! В этой статье на наглядных примерах разбираем, как работает Backpressure в Node.js, почему игнорирование обратного давления приводит к перерасходу памя…

19 Nov 2026, 13:50 UTC596 views1 reactionsread 21 November 2026
Photo

10 возможностей Java 21–25, которые действительно стоит использовать За последние пять релизов Java получила немало новых возможностей. Но какие из них действительно полезны в повседневной разработке, а не просто красиво выглядят в списке обновлений? В этой статье автор делится 10 возможностями Java 21–25, которые изменили подход его команды к написанию кода и оказались полезными на практике. ➡️ Перейти на сайт ❤…

👍1

18 Nov 2026, 16:12 UTC687 viewsread 21 November 2026
Photo

REST API в облаке: пошаговый гайд на Java + Spring Представьте, что у вас есть бэкенд-приложение с REST API и вы хотите обращаться к нему не только с локальной машины, но и через браузер, Postman, фронтенд или моб. приложение. Для этого можно настраивать маршрутизацию, туннелирование, искать белый IP — или просто задеплоить приложение в облако. Держите пошаговую инструкцию, в которой развернём Java-приложение на …

18 Nov 2026, 11:59 UTC718 viewsread 21 November 2026
Photo

Паттерн BFF (бэкенд для фронтенда): преимущества, недостатки и лучшие практики для реализации Если вы хотите стать настоящим мастером API, то вам обязательно нужно знать о паттерне BFF и как его использовать. В этой статье рассказываем, как создавать управляемую архитектуру с использованием BFF, избегая избыточной сложности и головной боли при поддержке. ➡️ Перейти на сайт ❤️ Заметки Бэкендера // Чат

17 Nov 2026, 15:32 UTC711 viewsread 21 November 2026
Photo

Наконец-то, пополнение всех популярных сервисов в одном месте в Телеграм! — Apple ID — Steam — Spotify, YouTube Premium, — ESIM — Claude, ChatGPT Моментальное исполнение заказа, попробуйте прямо сейчас

16 Nov 2026, 16:13 UTC775 viewsread 21 November 2026
Photo

Почему Deno быстрее Node.js: технический разбор Сравниваешь производительность серверных платформ и хочешь понять реальные преимущества Deno перед Node.js? Автор провёл глубокое техническое исследование, чтобы выяснить, где именно Deno получает выигрыш в скорости. Анализ показывает: Deno стабильно обходит Node.js на HTTP-нагрузке в 1.65 раза (72,400 req/sec против 44,000). Основные причины — более эффективный event…

16 Nov 2026, 11:18 UTC817 viewsread 21 November 2026
Photo

Огромная библиотека решений для Go Ищешь качественные примеры кода на Go, которые уже протестированы и соответствуют современным практикам языка? Go Cookbook собрал готовые решения для самых распространенных задач. База содержит сотни сниппетов по основным категориям: работа с Web, асинхронное программирование, базы данных, шифрование и DevOps. Каждый пример имеет развернутые комментарии, тесты и демонстрирует прав…

16 Nov 2026, 09:04 UTC814 viewsread 21 November 2026
Photo

54 DevOps-проекта для портфолио Хочешь собрать реальный DevOps-проект за выходные и добавить в резюме? В этом репозитории собраны 54 практических задания — от базовых до продвинутых. Проекты охватывают все ключевые технологии: Terraform, AWS, Azure, Kubernetes, CI/CD, DevSecOps, мониторинг и serverless. Каждый проект — это готовый кейс с инфраструктурой как код, безопасными настройками и документацией. ➡️ Перейти …

10 Nov 2026, 16:11 UTC≈1,210 viewsread 21 November 2026
Photo

Автоматизация тестирования в Go для микросервисов Разбираешься с тестированием в микросервисной архитектуре, где ошибки в одном сервисе могут сорвать весь релиз и привести к реальным потерям? Основная проблема: высокие издержки ручных проверок при десятках сервисов и постоянных релизах. Решение — внедрение системного подхода к автоматизации на Go с полуторалетним опытом автора: от скепсиса команды до полного призна…

10 Nov 2026, 11:11 UTC924 viewsread 21 November 2026
Photo

Начало программирования игр на C++. Третье издание. Изучите C++ с нуля, создавая забавные игры -- Что вы узнаете: Всегда мечтали создавать свои игры? С третьим изданием книги «Начало программирования игр на C++» вы сможете воплотить эту мечту в реальность! Это руководство для начинающих обновлено и улучшено и включает новейшие функции VS 2022, SFML и современные методы программирования на C++20. Вы получите увлекат…

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

Posts recorded as deleted after publishing

We recorded 9 posts on @backend_it 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
12 August 2026
Most recent seen missing
16 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
2

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

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.

Backend | Python, Java, PHP, Rust, SQL, C#
@backenderrr · 10,356
#1
Open IT | Программирование
@openit_tg · 34,427
#2
ITLES | Уроки программирования
@itles_tg · 15,803
#3
Porscode | CMD
@porscode_tg · 28,031
#4
GitHub Community
@github · 155,143
#5
Programmer & IT Memes
@itmemes · 121,781
#6
Open IT | Архив
@openit_archive · 18,761
#7
CodeCamp
@codecamp · 177,161
#8
Сборник IT знаний
@sbornik_znanii · 10,337
#9
Porscode | Archive
@porscode_archive · 9,705
#10
Заметки Фронтендера
@frontend_tg · 5,513
#11
IT-Academy | Айти
@it_academy_tg · 12,524
#12
Книжное хранилище
@knijnoe_xranilishe · 19,476
#13
Frontend Archive
@frontenderrrr · 3,108
#14
[PYTHON:TODAY]
@python2day · 63,245
#15
XOR
@xor_journal · 191,253
#16
Backend Portal | Программирование
@BackendPortal · 16,344
#17
IT Portal
@IT_Portal · 118,729
#18
BZD • Книги для программистов
@bzd_channel · 36,183
#19
Кодим на Коленке | Уроки по программированию
@code_on_tg · 8,838
#20
ITайник | курсы, уроки
@itainik · 13,147
#21
Книжки айтишки
@books_itishki · 7,380
#22
UzDev Jobs – IT Jobs
@uzdev_jobs · 26,256
#23
Склад айтишки
@skladitshki · 7,206
#24
Верстак | IT
@itverstak · 6,832
#25
Golang
@Golang_google · 40,397
#26
CodeMode | Программирование
@code_m0de · 10,740
#27
медиатрендс
@mediatrends · 602,084
#28
Code Guru
@codeguru_tg · 8,705
#29
Senior Python Developer
@seniorpy · 39,004
#30
IT-Сэнсэй | Уроки по программированию
@it_sensei · 11,043
#31
Machinelearning
@ai_machinelearning_big_data · 274,529
#32
NOP::Nuances of Programming
@nuancesprog · 55,838
#33
Простой Python | Программирование
@python_piton_javascript · 123,155
#34
Python Expert | Программирование
@pythonexpert_it · 10,412
#35
Библиотека программиста
@proglibrary · 77,413
#36
Python и 1000 уязвимостей
@osint_pythons · 36,436
#37
Хауди Хо - IT юмор, жизнь программиста
@howdyho_official · 77,183
#38
hahacker_news
@hahacker_news · 25,178
#39
Senior Java Developer
@seniorjavist · 20,316
#40
Windows Community
@wind_community · 40,810
#41
Python/ django
@pythonl · 58,071
#42
Анализ данных (Data analysis)
@data_analysis_ml · 51,975
#43
Библиотека Go-разработчика | Golang
@goproglib · 23,855
#44
Social Engineering
@Social_engineering · 124,611
#45
Библиотека Программиста
@code_library · 17,542
#46
Data Science: Алгоритмы и Структуры данных
@structuredata · 7,572
#47
Гайды по БД и SQL
@learn_bd_sql · 6,109
#48
Java библиотека
@javalib · 30,227
#49
Data Secrets
@data_secrets · 96,432
#50
Хабр
@habr_com · 134,920
#51
Golang Books
@golang_books · 16,848
#52
Java Learning
@Java_per_month · 16,388
#53
Сайтодел | GitHub, Верстка, Сайты, Вайбкодинг
@sitodel · 25,371
#54
INSPECTOR | OSINT
@it_fullstak · 11,103
#55
Не баг, а фича
@bugfeature · 547,298
#56
Code Learning
@codelearning_tg · 9,200
#57
Библиотека питониста | Python, Django, Flask
@pyproglib · 36,894
#58
DevOps
@DevOPSitsec · 23,873
#59
Node.JS [ru] | Серверный JavaScript
@we_use_js · 10,557
#60
Programmer memes
@programmer_memes · 50,386
#61
ИБ Книга | Библиотека ИБ
@itbook_library · 15,886
#62
infosec
@it_secur · 63,745
#63
Видеоуроки IT
@videos_it · 5,962
#64
Python Portal
@PythonPortal · 50,746
#65
Эксплойт
@exploitex · 2,016,103
#66
Бэкдор
@whackdoor · 1,527,665
#67
Physics.Math.Code
@physics_lib · 146,667
#68
Технотренды
@techno_media · 920,314
#69
Python Learning
@Python_per_month · 27,798
#70
Винда для чайника
@the_winda · 5,987
#71
Ustoz-Shogird
@UstozShogird · 22,890
#72
Программист
@progeri · 14,972
#73

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

Open IT | Архив
@openit_archive · 18,761
Telegram ranks this channel #6 of 59 here — alongside 58 others — read 5 October 2026
Porscode | CMD
@porscode_tg · 28,031
Telegram ranks this channel #6 of 77 here — alongside 76 others — read 9 September 2026
Windows Community
@wind_community · 40,810
Telegram ranks this channel #6 of 74 here — alongside 73 others — read 29 August 2026
Полка Разработчика
@developer_shelf · 26,696
Telegram ranks this channel #11 of 63 here — alongside 62 others — read 11 September 2026
Книжное хранилище
@knijnoe_xranilishe · 19,476
Telegram ranks this channel #16 of 73 here — alongside 72 others — read 30 September 2026
[404] — программирование
@procode404 · 39,987
Telegram ranks this channel #25 of 83 here — alongside 82 others — read 30 August 2026
Простой Python | Программирование
@python_piton_javascript · 123,155
Telegram ranks this channel #30 of 84 here — alongside 83 others — read 13 August 2026
Сайтодел | GitHub, Верстка, Сайты, Вайбкодинг
@sitodel · 25,371
Telegram ranks this channel #31 of 89 here — alongside 88 others — read 13 September 2026
Senior Java Developer
@seniorjavist · 20,316
Telegram ranks this channel #34 of 89 here — alongside 88 others — read 26 September 2026
Учебные фильмы 🎞
@maths_lib · 25,583
Telegram ranks this channel #37 of 67 here — alongside 66 others — read 14 September 2026
Эрудиция | Digital и бизнес образование
@eruditurl24 · 96,131
Telegram ranks this channel #41 of 86 here — alongside 85 others — read 16 August 2026
Senior Python Developer
@seniorpy · 39,004
Telegram ranks this channel #42 of 92 here — alongside 91 others — read 30 August 2026
NOP::Nuances of Programming
@nuancesprog · 55,838
Telegram ranks this channel #43 of 84 here — alongside 83 others — read 23 August 2026
Айтишка - Digital & IT
@ITtishka · 21,065
Telegram ranks this channel #48 of 88 here — alongside 87 others — read 23 September 2026
Java библиотека
@javalib · 30,227
Telegram ranks this channel #52 of 84 here — alongside 83 others — read 7 September 2026
Python Learning
@Python_per_month · 27,798
Telegram ranks this channel #56 of 86 here — alongside 85 others — read 9 September 2026
Unity & Unreal | GameDev
@unity_gamedev_unreal · 32,386
Telegram ranks this channel #72 of 76 here — alongside 75 others — read 4 September 2026

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

“Заметки Бэкендера” (@backend_it), 18,622 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/backend_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.