Telegram RegisterThe public register of Telegram
Telegram profile photo for SqlCom.ru - сообщество MS SQL

Supergroup

SqlCom.ru - сообщество MS SQL

@sqlcom

On this record: Growth · Engagement · Citations · Cite this entry

6,922members

-49 since we began measuring on 6 August 2026

1,164 online right now

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

Register entry

Telegram ID-1001060829887
TypeSupergroup
Username@sqlcom
Description@sqlcom - основной канал (только MS SQL) @sql_ninja - второй канал (BigData) @sql_jobs - вакансии По вопросам рекламы - @Dm1tr1ch
CreatedBetween 1 May 2016 and 28 February 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live27 August 2026
Measurements held9
On Telegramt.me/sqlcom

Growth

6,9226,9726,9476 August 2026 — 6,971 members7 August 2026 — 6,964 members10 August 2026 — 6,970 members13 August 2026 — 6,972 members17 August 2026 — 6,967 members20 August 2026 — 6,965 members24 August 2026 — 6,954 members27 August 2026 — 6,922 members27 August 2026 — 6,922 members6 August 202627 August 2026
9 measurements spanning 21 days, net -49. 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,915–6,980 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
27 Aug 2026, 19:146,922no change
27 Aug 2026, 07:536,922-32
24 Aug 2026, 03:336,954-11
20 Aug 2026, 10:236,965-2
17 Aug 2026, 10:466,967-5
13 Aug 2026, 11:356,972+2
10 Aug 2026, 15:186,970+6
7 Aug 2026, 07:146,964-7
6 Aug 2026, 13:386,971first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Mentions

Named by 3 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.

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

“SqlCom.ru - сообщество MS SQL” (@sqlcom), 6,922 members as measured 27 August 2026. Telegram Register, tgregister.com/channel/sqlcom.

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.