7,2 млн рублей призового фонда и реальные задачи космической отрасли 🚀 В сентябре пройдет серия КосмоХакатонов для студентов, молодых ученых и специалистов. Участникам предстоит за два дня разработать собственное решение, поработать с экспертами и представить проект жюри. Участников ждут: 🛰 реальные задачи космической отрасли 👥 команды от 3 до 5 человек 💻 очный и онлайн-форматы 🧑💻 работа с экспертами и трекерами 🏆…

Channel
Backend Portal | Программирование
@BackendPortal
On this record: Topic · Growth · Engagement · What this channel posts · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
16,106subscribers
-216 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 | -1001633059299 |
|---|---|
| Type | Channel |
| Username | @BackendPortal |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/BackendPortal |
Topic
Technology — 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 59% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 20:39 | 16,106 | -1 |
| 17 Sept 2026, 15:01 | 16,107 | -10 |
| 13 Sept 2026, 20:36 | 16,117 | -8 |
| 12 Sept 2026, 03:17 | 16,125 | -24 |
| 9 Sept 2026, 18:55 | 16,149 | +3 |
| 6 Sept 2026, 08:37 | 16,146 | -6 |
| 3 Sept 2026, 22:02 | 16,152 | -5 |
| 2 Sept 2026, 10:23 | 16,157 | -7 |
| 1 Sept 2026, 08:13 | 16,164 | -9 |
| 31 Aug 2026, 10:12 | 16,173 | -13 |
| 30 Aug 2026, 12:04 | 16,186 | +1 |
| 29 Aug 2026, 15:33 | 16,185 | -5 |
| 28 Aug 2026, 18:34 | 16,190 | -6 |
| 27 Aug 2026, 21:15 | 16,196 | -2 |
| 27 Aug 2026, 00:28 | 16,198 | -6 |
| 26 Aug 2026, 01:23 | 16,204 | -9 |
| 25 Aug 2026, 00:34 | 16,213 | -3 |
| 23 Aug 2026, 12:48 | 16,216 | -11 |
| 21 Aug 2026, 19:59 | 16,227 | -4 |
| 20 Aug 2026, 16:03 | 16,231 | first reading |
Engagement
82 posts held, back to 29 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 59 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.86%
- avg views ÷ 16,106 subscribers
- Avg views / post
- 943
- 14 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 14
- of 82 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.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 82 (29 July 2026 – 3 September 2026) |
| Views total | 13,206 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:03 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
- Video runtime
- 3m 08s
- Average length
- 21s
Measured directly from 9 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.
Advertising
- Ad load
- 2.44%
- 2 of 82 posts carry an ad marker
- Regulatory tokens
- 2
- posts carrying an erid · 2 distinct tokens
- Median views · ads
- 1,260
- over 2 measured posts
- Median views · rest
- 1,270
- over 80 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.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2SDnjdAYnyZ | 1 | 11 August 2026 | 11 August 2026 |
| 2Vtzqw8Jxi7 | 1 | 21 August 2026 | 21 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 82 most recent posts we hold, published 29 July 2026 to 3 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
Следующая тема: Routing. Материал о том, что на самом деле происходит после того, как запрос покидает браузер, и как работает routing на разных уровнях. Network routing, routers, routing tables, BGP, OSPF, static и dynamic routes, backend routing, path parameters, query parameters, nested routes, API versioning, middleware, route matching — а также то, что происходит под капотом routing engine. Это не очередной ра…
Backend Checklist: JSON-сериализация Сериализация — это преобразование Python-объектов в текст для передачи по сети. Звучит как простая смена формата, но на деле это скорее перевод с одного языка на другой. А при переводе часть информации может потеряться. В JSON всего семь типов, а у ваших объектов их гораздо больше. Весь набор типов JSON — это object, array, string, number, true, false и null. И всё. Никаких date…
Недавно довольно часто пользуюсь Ansible — очень сильный проект с открытым исходным кодом, уже 69,1 тысячи звёзд на GitHub. 1️⃣ Автоматизацию можно описывать обычными текстовыми сценариями и использовать их для развёртывания приложений, настройки серверов и управления облачной инфраструктурой. Недавно мне нужно было подготовить окружение сразу на трёх новых машинах. Написал один playbook — и всё поднялось почти авт…
now() — это не «сейчас», а скорее «когда-то было сейчас». На самом деле now() возвращает время начала текущей транзакции. Реальные часы продолжают идти, но каждый последующий вызов now(), CURRENT_TIMESTAMP, CURRENT_TIME и CURRENT_DATE внутри этой же транзакции всё равно возвращает одно и то же время. В Postgres это называется transaction-frozen timestamp. То есть INSERT на 10 000 строк с created_at DEFAULT now() п…
Настоящая находка среди репозиториев. В нём собраны все основные шаги по защите и усилению безопасности Linux-сервера. Если у вас есть VPS, стоит сохранить: → https://github.com/imthenachoman/How-To-Secure-A-Linux-Server 👉 @BackendPortal
Все говорят «поставь кэш». Но почти никто не показывает, где система реально развалится. Breakscale — это не обычный генератор нагрузки. Это симулятор архитектуры, где ты собираешь систему, постепенно увеличиваешь трафик и смотришь, что сломается первым. В демонстрации: 2 запроса/с — всё зелёное 840 запросов/с — 99% запросов падают И самое интересное — узкое место вообще не в API. Обе базы данных загружены на 99,…
⚡️⚡️Joker 2026 — теперь больше, чем Java-конференция. Что изменилось? Огромные системы на Java будут жить еще много лет и знание платформы никак не обесценится. Однако сама работа инженера меняется. Код всё чаще можно поручить машине, а вот ответственность за архитектуру и рабочий продукт — нет. В этом году Joker пройдет в два дня: 14 октября разберем инженерную базу и современные практики, а 15-го обсудим разрабо…
Приложения и базы данных, которые стоят за ними. Instagram — PostgreSQL Reddit — PostgreSQL Twitch — PostgreSQL Notion — PostgreSQL Figma — PostgreSQL ChatGPT — PostgreSQL Skype — PostgreSQL GitHub — MySQL Shopify — MySQL Slack — MySQL YouTube — MySQL Uber — MySQL Airbnb — MySQL Facebook — MySQL Netflix — Cassandra Discord — ScyllaDB Забавно, насколько большая часть крупнейших сервисов в мире до сих пор держится…
👉 @BackendPortal
Ядро Linux приближается к отметке в 2 000 уязвимостей за один выпуск. Ещё несколько лет назад их было около 500 на выпуск. Потом число перевалило за 1 000. Затем за 1 500. Грег Кроа-Хартман, один из самых опытных сопровождающих ядра Linux, показал эту тенденцию перед своим выступлением на Kernel Recipes 2026. При этом сама кодовая база не выросла настолько сильно. В ней по-прежнему около 40 миллионов строк. Измен…
Вышел pnpm 12! Лучший менеджер пакетов для JavaScript-проектов. ✓ Безопасен по умолчанию ✓ Полностью переписан с нуля на Rust ✓ В 3 раза быстрее при чистой установке → https://pnpm.io/blog/releases/12.0 👉 @BackendPortal
Showing the 12 most recent of 82 posts we hold for @BackendPortal. 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
@BackendPortal 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
- 10 August 2026
- Most recent edit
- 10 August 2026
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 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
@dejavu041 · 49,886
Telegram ranks this channel #2 of 80 here — alongside 79 others — read 25 August 2026
@PythonPortal · 50,417
Telegram ranks this channel #2 of 80 here — alongside 79 others — read 25 August 2026
@FrontendPortal · 36,678
Telegram ranks this channel #3 of 90 here — alongside 89 others — read 1 September 2026
@IT_Portal · 100,284
Telegram ranks this channel #5 of 78 here — alongside 77 others — read 15 August 2026
@python_tg · 20,963
Telegram ranks this channel #16 of 85 here — alongside 84 others — read 25 September 2026
@developer_shelf · 26,815
Telegram ranks this channel #19 of 63 here — alongside 62 others — read 11 September 2026
@python_piton_javascript · 126,249
Telegram ranks this channel #23 of 84 here — alongside 83 others — read 13 August 2026
@EnglishScript · 45,107
Telegram ranks this channel #27 of 82 here — alongside 81 others — read 27 August 2026
@maths_lib · 25,423
Telegram ranks this channel #29 of 67 here — alongside 66 others — read 14 September 2026
@trendo · 67,788
Telegram ranks this channel #29 of 90 here — alongside 89 others — read 20 August 2026
@ai4telegram · 922,526
Telegram ranks this channel #29 of 73 here — alongside 72 others — read 8 August 2026
@howdyho_official · 78,781
Telegram ranks this channel #30 of 90 here — alongside 89 others — read 18 August 2026
@porscode_tg · 28,393
Telegram ranks this channel #35 of 77 here — alongside 76 others — read 9 September 2026
@seniorpy · 39,864
Telegram ranks this channel #43 of 92 here — alongside 91 others — read 30 August 2026
@code_ready · 21,604
Telegram ranks this channel #52 of 89 here — alongside 88 others — read 23 September 2026
@productivity_Q · 26,585
Telegram ranks this channel #52 of 84 here — alongside 83 others — read 12 September 2026
@unity_gamedev_unreal · 32,817
Telegram ranks this channel #64 of 76 here — alongside 75 others — read 4 September 2026
@Python_per_month · 28,238
Telegram ranks this channel #65 of 86 here — alongside 85 others — read 9 September 2026
@sitodel · 25,725
Telegram ranks this channel #70 of 89 here — alongside 88 others — read 13 September 2026
@vibecoding_tg · 63,075
Telegram ranks this channel #72 of 85 here — alongside 84 others — read 1 September 2026
@sovuche · 105,414
Telegram ranks this channel #93 of 94 here — alongside 93 others — read 21 August 2026
This channel appears in 21 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Backend Portal | Программирование” (@BackendPortal), 16,106 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/BackendPortal.
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.