Channel
Lobo.Vip | Canal Oficial ®
@Lobobetofficial
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
10,487subscribers
-123 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 | -1002244119292 |
|---|---|
| Type | Channel |
| Username | @Lobobetofficial |
| Created | Between 1 May 2024 and 31 October 2024 — 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 | 9 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Lobobetofficial |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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, 23:59 | 10,487 | -27 |
| 15 Sept 2026, 19:57 | 10,514 | -25 |
| 14 Sept 2026, 02:20 | 10,539 | -15 |
| 12 Sept 2026, 11:38 | 10,554 | -18 |
| 10 Sept 2026, 10:16 | 10,572 | -26 |
| 7 Sept 2026, 07:20 | 10,598 | -8 |
| 4 Sept 2026, 12:59 | 10,606 | -4 |
| 3 Sept 2026, 12:53 | 10,610 | no change |
| 3 Sept 2026, 12:47 | 10,610 | 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.
@AAvipcom · 35,339
Telegram ranks this channel #31 of 71 here — alongside 70 others — read 3 September 2026
@vipyhgame · 33,871
Telegram ranks this channel #43 of 66 here — alongside 65 others — read 3 September 2026
@bet3kofficial · 76,232
Telegram ranks this channel #62 of 82 here — alongside 81 others — read 3 September 2026
@QGbetOfficial · 25,334
Telegram ranks this channel #72 of 86 here — alongside 85 others — read 14 September 2026
@brtopoficial · 26,536
Telegram ranks this channel #77 of 87 here — alongside 86 others — read 12 September 2026
@app2hbet · 22,729
Telegram ranks this channel #78 of 81 here — alongside 80 others — read 20 September 2026
@a52bet · 99,313
Telegram ranks this channel #86 of 87 here — alongside 86 others — read 3 September 2026
This channel appears in 7 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.
“Lobo.Vip | Canal Oficial ®” (@Lobobetofficial), 10,487 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Lobobetofficial.
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.