Telegram RegisterThe public register of Telegram
Telegram profile photo for SQL Portal | Базы Данных

Channel

SQL Portal | Базы Данных

@SQLPortal

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

13,838subscribers

-80 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-1002186115711
TypeChannel
Username@SQLPortal
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live22 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/SQLPortal

Growth

13,83813,91813,8787 August 2026 — 13,918 subscribers7 August 2026 — 13,918 subscribers8 August 2026 — 13,909 subscribers9 August 2026 — 13,903 subscribers10 August 2026 — 13,893 subscribers11 August 2026 — 13,887 subscribers12 August 2026 — 13,879 subscribers13 August 2026 — 13,874 subscribers14 August 2026 — 13,864 subscribers16 August 2026 — 13,860 subscribers18 August 2026 — 13,858 subscribers19 August 2026 — 13,857 subscribers20 August 2026 — 13,854 subscribers21 August 2026 — 13,849 subscribers22 August 2026 — 13,838 subscribers7 August 202622 August 2026
15 measurements spanning 15 days, net -80. 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 13,826–13,930 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 15:4713,838-11
21 Aug 2026, 09:2413,849-5
20 Aug 2026, 06:2313,854-3
19 Aug 2026, 08:4413,857-1
18 Aug 2026, 11:5713,858-2
16 Aug 2026, 06:2813,860-4
14 Aug 2026, 19:5613,864-10
13 Aug 2026, 09:2513,874-5
12 Aug 2026, 12:3813,879-8
11 Aug 2026, 12:4213,887-6
10 Aug 2026, 14:5413,893-10
9 Aug 2026, 15:3313,903-6
8 Aug 2026, 14:5013,909-9
7 Aug 2026, 13:1613,918no change
7 Aug 2026, 13:0913,918first reading

Engagement

53 posts held, back to 29 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 29 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.99%
avg views ÷ 13,838 subscribers
Avg views / post
967
53 posts measured
Reaction rate
0.489%
reactions ÷ views · ER floor
Posts in window
53
of 53 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 51 of 53 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 22 August 2026
Posts held53 (29 July 202622 August 2026)
Views total51,264
Reactions total242
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 14:22 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
1m 09s
Average length
35s

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.

Reaction mix

242 reactions across 51 posts, in 6 distinct kinds. The most used accounts for 46.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11246.3%
👍7832.2%
👀218.68%
🔥177.02%
😁114.55%
🤔31.24%

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

Measured over the 53 most recent posts we hold, published 29 July 2026 to 22 August 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

22 Aug 2026, 06:07 UTC394 views3 reactionsread 22 August 2026
Photo

JOIN как в ORM: можно ли заставить PostgreSQL понимать связи между таблицами? В статье разбирают интересную идею: вместо того чтобы каждый раз вручную прописывать JOIN ... ON, использовать уже существующие связи FOREIGN KEY как навигацию между таблицами. Автор показывает, почему стандартный SQL до сих пор не умеет нормально использовать FK при построении JOIN, какие подходы уже существовали и как реализовать подобн

3

21 Aug 2026, 16:07 UTC509 views2 reactionsread 22 August 2026
Video

Ценный ресурс для разработчиков онлайн справочник «DevDocs» Сборник документации множества языков программирования, библиотек и фреймворков в одном интерфейсе. Сервис обеспечивает быстрый поиск, возможность работы офлайн и гибкую настройку отображения. Экономьте время и работайте эффективно 👍 👉 @SQLPortal

👍2

21 Aug 2026, 06:07 UTC697 views6 reactionsread 22 August 2026
Photo

Бесплатный курс Python с нуля до pandas Пошагово изучаем основы для Python и переходим к работе с данными через pandas, NumPy и Matplotlib. Туториал построен на практических примерах и помогает быстро перейти от базового синтаксиса к реальным задачам. Ставим реакции и залетаем 😎 👉 @SQLPortal

👍6

20 Aug 2026, 16:07 UTC721 views6 reactionsread 22 August 2026
Photo

5 советов по PostgreSQL, которыми большинство разработчиков никогда не пользуется Используйте условные/частичные индексы. Вместо индексации всего столбца индексируйте только строки, которые реально используются в ваших запросах (например, status = 'active'). Такой индекс меньше, поиск быстрее, а места на диске требуется меньше. Минимизируйте N+1-запросы. Вместо выполнения отдельного запроса внутри цикла получите вс

👍42

20 Aug 2026, 06:07 UTC767 views2 reactionsread 22 August 2026
Photo

Pro tip для ускорения запросов Если условие WHERE использует несколько столбцов, создание составного индекса может значительно повысить производительность. 👉 @SQLPortal

2

19 Aug 2026, 16:07 UTC823 views2 reactionsread 22 August 2026
Photo

SQL Tip (MySQL) Некоторые функции для агрегации и поиска значений в SQL: MIN(), MAX() — поиск минимального/максимального значения среди всех строк CEIL() — округление числа вверх до ближайшего целого REPLACE() — удаление символа из строки или его замена 👉 @SQLPortal

👍2

19 Aug 2026, 06:07 UTC842 views3 reactionsread 22 August 2026
Photo

SQL CHEATSHEET ДЛЯ РАЗРАБОТЧИКОВ Освойте самые важные SQL-команды в одном месте. Изучаете базы данных, готовитесь к собеседованию, разрабатываете backend-приложения или работаете разработчиком — SQL является обязательным навыком. В этом cheatsheet: • SELECT • WHERE • ORDER BY • GROUP BY и HAVING • JOIN • Агрегатные функции • Подзапросы • INSERT, UPDATE и DELETE • Wildcards • Основные типы данных SQL 👉 @SQLPorta

👍3

18 Aug 2026, 16:59 UTC875 views3 reactionsread 22 August 2026
Photo

GitHub раздаёт знания бесплатно: интерактивные курсы по Git Платформа запустила cборку онлайн курсов, где можно прокачать навыки работы с Git и GitHub без подписок. Ветки, коммиты, pull request’ы, Actions и реальные командные сценарии всё в формате интерактивных Быстрый и лёгкий способ подтянуть базу и перестать гуглить «как откатить коммит» в неподходящий момент 👇 👉 @SQLPortal

3

18 Aug 2026, 06:06 UTC835 views2 reactionsread 22 August 2026
Photo

Вам не нужен перегруженный клиент для баз данных, чтобы просто посмотреть содержимое таблицы. Data Peek — минималистичный desktop SQL-клиент с поддержкой ИИ для разработчиков, работающих с PostgreSQL, MySQL, Microsoft SQL Server и SQLite. Он позволяет в одном приложении просматривать, запрашивать и управлять данными, объединяя SQL-редактор на базе Monaco, инструменты для работы со схемой, AI-ассистента и средства а

2

17 Aug 2026, 16:06 UTC879 views5 reactionsread 22 August 2026
Photo

Мёд по Git: шпаргалка которая закрывает 90% задач Нашёл мощную cheat sheet по Git всё самое нужное на нескольких страницах: инициализация, коммиты, ветки, merge, diff, stash, rebase и работа с удалёнными репозиториями Особенно удобно, что показаны не только команды, но и как всё двигается внутри Git: staging area, история коммитов, ветки и их слияние Сохраняем PDF за лайк ❤️ 👉 @SQLPortal

5

17 Aug 2026, 06:06 UTC947 views5 reactionsread 22 August 2026
Photo

Интерактивные дорожные карты Когда новички заходят в IT они часто теряются в океане технологий Платформа призвана решить проблему и предлагает понятные визуальные карты обучения, составленные экспертами и сообществом. Здесь можно отследить свой прогресс, найти лучшие источники и понять что реально стоит учить в 2025 Забирай пригодится 🪑 👉 @SQLPortal

👍32

16 Aug 2026, 16:06 UTC989 views5 reactionsread 22 August 2026
Photo

Игра в SQL кальмара от DataLemur Интерактивная игра для прокачки SQL-навыков. Выполняешь реальные задачки в формате интервью и тут же проверяешь результат. Подойдёт всем, кто хочет практиковать SQL с пользой. 👉 @SQLPortal

3👍2

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

Polls

The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

16 Aug 2026, 06:06 UTCAnonymous Quiz187 voters

Варианты:

  1. A25%
  2. B18%
  3. C52%
  4. D5%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

11 Aug 2026, 16:06 UTCAnonymous Quiz159 voters

Варианты

  1. A28%
  2. B27%
  3. C40%
  4. D4%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

8 Aug 2026, 16:06 UTCAnonymous Quiz224 voters

Варианты:

  1. A10%
  2. B50%
  3. C21%
  4. D18%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 53 most recent posts we hold, published 29 July 2026 to 22 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 873,834 of 1,583,249entries 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.

Forward network

Republished by

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

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.

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.

IT Portal
@IT_Portal · 101,184
Telegram ranks this channel #16 of 78 here — alongside 77 others — read 15 August 2026
Простой Python | Программирование
@python_piton_javascript · 128,051
Telegram ranks this channel #78 of 84 here — alongside 83 others — read 13 August 2026

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

“SQL Portal | Базы Данных” (@SQLPortal), 13,838 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/SQLPortal.

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.