Channel
€ VIP $
@Moro_cco1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,087subscribers
-185 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001835446828 |
|---|---|
| Type | Channel |
| Username | @Moro_cco1 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/Moro_cco1 |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 21:05 | 4,087 | -10 |
| 1 Nov 2026, 05:31 | 4,097 | -28 |
| 29 Oct 2026, 01:40 | 4,125 | -77 |
| 25 Oct 2026, 18:17 | 4,202 | -57 |
| 22 Oct 2026, 20:50 | 4,259 | -31 |
| 19 Oct 2026, 22:57 | 4,290 | -48 |
| 16 Oct 2026, 22:59 | 4,338 | +334 |
| 14 Oct 2026, 07:45 | 4,004 | -42 |
| 10 Oct 2026, 22:57 | 4,046 | -115 |
| 4 Oct 2026, 18:41 | 4,161 | -107 |
| 25 Sept 2026, 07:19 | 4,268 | -302 |
| 15 Sept 2026, 06:59 | 4,570 | -61 |
| 11 Sept 2026, 08:16 | 4,631 | -44 |
| 6 Sept 2026, 12:00 | 4,675 | -22 |
| 2 Sept 2026, 20:21 | 4,697 | no change |
| 2 Sept 2026, 04:35 | 4,697 | -38 |
| 29 Aug 2026, 18:37 | 4,735 | -40 |
| 27 Aug 2026, 04:45 | 4,775 | +503 |
| 26 Aug 2026, 06:00 | 4,272 | 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.
@kimoobet_Tips · 374,025
Telegram ranks this channel #24 of 40 here — alongside 39 others — read 16 September 2026
@WorldWideFootballBetss · 32,096
Telegram ranks this channel #46 of 61 here — alongside 60 others — read 10 September 2026
@WarriorCoin_Ann · 298,448
Telegram ranks this channel #58 of 78 here — alongside 77 others — read 26 August 2026
@m7asbah · 19,255
Telegram ranks this channel #68 of 77 here — alongside 76 others — read 4 October 2026
This channel appears in 4 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“€ VIP $” (@Moro_cco1), 4,087 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/Moro_cco1.
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.