https://t.me/obsidian_br

Channel
Canais e Grupos - TI
@grupos_ti
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
11,379subscribers
-186 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001093136010 |
|---|---|
| Type | Channel |
| Username | @grupos_ti |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/grupos_ti |
Topic
Technology — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 17 Sept 2026, 12:39 | 11,379 | -18 |
| 15 Sept 2026, 11:37 | 11,397 | -16 |
| 13 Sept 2026, 17:41 | 11,413 | -7 |
| 12 Sept 2026, 02:17 | 11,420 | -11 |
| 9 Sept 2026, 20:41 | 11,431 | -10 |
| 6 Sept 2026, 15:18 | 11,441 | -4 |
| 4 Sept 2026, 06:36 | 11,445 | -4 |
| 1 Sept 2026, 22:26 | 11,449 | -9 |
| 1 Sept 2026, 01:38 | 11,458 | -8 |
| 31 Aug 2026, 00:05 | 11,466 | -1 |
| 30 Aug 2026, 01:54 | 11,467 | +1 |
| 29 Aug 2026, 02:47 | 11,466 | -9 |
| 28 Aug 2026, 05:45 | 11,475 | +3 |
| 27 Aug 2026, 02:23 | 11,472 | -3 |
| 26 Aug 2026, 02:44 | 11,475 | -3 |
| 25 Aug 2026, 04:16 | 11,478 | -8 |
| 24 Aug 2026, 00:56 | 11,486 | -4 |
| 22 Aug 2026, 10:28 | 11,490 | -6 |
| 21 Aug 2026, 04:15 | 11,496 | -3 |
| 20 Aug 2026, 04:34 | 11,499 | first reading |
Engagement
20 posts held, back to 23 June 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 44 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 29 December 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
#Canal #Web #Programação < ! - - Guia para Desenvolvedores Front-End e Backend - - > https://t.me/GuiaDev
Grupo para divulgação de vagas/freelas Front-End / Back-End / DevOps https://t.me/DevsVagas
#Grupo #Linux - Arch Linux Brasil https://t.me/archlinuxbr
#Grupo #Web #Programação O maior grupo brasileiro de desenvolvimento Front-End do Telegram https://t.me/FrontEndBR
#Grupo #Web #Programação Grupo brasileiro de desenvolvimento Back-End https://t.me/BackEndBrasil
#Grupo #Programação - Os Programadores t.me/osprogramadores Canal do grupo: https://t.co/yxAwkGYEHh Canal com vagas de emprego pelo mundo: https://t.me/osprogramadores_vagas
#Grupo Developers Grupo para discussões e dúvidas sobre programação e diversos assuntos relacionados à TI. https://t.me/grupodevelopers
Grupos da Faculdade VINCIT de tecnologia: #faculdade #hacker #qa #java #projetos https://t.me/uniciv_hacker https://t.me/uniciv_qa https://t.me/uniciv_projetos https://t.me/uniciv_java
Começando na informática! #geral Grupo para iniciantes ou leigos na informática, para tirar dúvidas ou trocar experiências em windows, Linux e Android. https://t.me/meuprimeirolinux
CANAL PARA OS USUÁRIOS DO ANDROID QUE CURTEM PROGRAMAÇÃO, HACKING, TERMUX, EMULAÇÃO, CURIOSIDADES, ETC. REGRAS: •Proibido conteúdo adulto •Proibido conteúdo agressivo •Proibido uso de palavrões •Proibido trava zap •Proibido menor idade #CANAL t.me/androsofoch
#Grupo #Programação - Os Programadores t.me/osprogramadores Link para o podcast do grupo: https://open.spotify.com/show/0IrqGbURcNnumdHVkfKIFA Canal do grupo: https://t.co/yxAwkGYEHh
Showing the 12 most recent of 20 posts we hold for @grupos_ti. 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.
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
Names
Channels on the register whose handles appear in this channel's posts.
@osprogramadores · 4,1192 postsAndrosofoCH
@androsofoch · 1,0621 postArch Linux Brasil
@archlinuxbr · 2,4311 postBack-End Brasil
@BackEndBrasil · 3,4321 postDevs VAGAS
@DevsVagas · 4,5201 postFront-End BR
@FrontEndBR · 5,9141 postCNPG Grupo👑|Canal Oficial👑
@GRUPOCN · 3,4561 postDevelopers
@grupodevelopers · 2,5211 postGuia Dev
@GuiaDev · 7,0011 postOsProgramadores_vagas
@osprogramadores_vagas · 6151 postData Science, Programação e Simulação. 💻📈
@simulacao · 1,1431 post🇻 🇮 🇱 🇭 🇦 🇱 🇻 🇦
@VILHALVA100_CANAL · 1831 post
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.
Handles this channel named that no longer answer
- Dead references
- 7
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 7
- vacant every time we have ever looked
@grupos_ti named 7 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 5 posts, 8 August 2026 – 13 August 2026
named in 4 posts, 8 August 2026 – 16 August 2026
named in 4 posts, 8 August 2026 – 16 August 2026
named in 4 posts, 8 August 2026 – 16 August 2026
named in 4 posts, 8 August 2026 – 16 August 2026
named in 4 posts, 8 August 2026 – 16 August 2026
named in 4 posts, 8 August 2026 – 16 August 2026
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Canais e Grupos - TI” (@grupos_ti), 11,379 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/grupos_ti.
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.