Channel
123BR Grupo🇧🇷Oficial
@www123br
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
13,344subscribers
-216 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001127010916 |
|---|---|
| Type | Channel |
| Username | @www123br |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/www123br |
Topic
Other / unclassifiable — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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, 21:17 | 13,344 | -44 |
| 15 Sept 2026, 17:40 | 13,388 | -22 |
| 13 Sept 2026, 23:39 | 13,410 | -27 |
| 12 Sept 2026, 09:40 | 13,437 | -33 |
| 10 Sept 2026, 05:19 | 13,470 | -53 |
| 6 Sept 2026, 21:57 | 13,523 | -36 |
| 4 Sept 2026, 07:58 | 13,559 | -1 |
| 3 Sept 2026, 12:52 | 13,560 | first 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.
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.
@KFBET_Oficial · 49,545
Telegram ranks this channel #4 of 62 here — alongside 61 others — read 3 September 2026
@VOYPG · 93,494
Telegram ranks this channel #8 of 52 here — alongside 51 others — read 3 September 2026
@W1PG_Grupo2 · 60,026
Telegram ranks this channel #8 of 58 here — alongside 57 others — read 3 September 2026
@a777Clubevip · 94,120
Telegram ranks this channel #11 of 81 here — alongside 80 others — read 3 September 2026
@W1PG_BET · 60,755
Telegram ranks this channel #12 of 57 here — alongside 56 others — read 3 September 2026
@VIPGRUPO_COM · 26,395
Telegram ranks this channel #36 of 72 here — alongside 71 others — read 12 September 2026
@bugpgjogo · 46,749
Telegram ranks this channel #46 of 77 here — alongside 76 others — read 3 September 2026
@equipe777 · 89,309
Telegram ranks this channel #49 of 72 here — alongside 71 others — read 3 September 2026
This channel appears in 8 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“123BR Grupo🇧🇷Oficial” (@www123br), 13,344 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/www123br.
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.