Channel
PRONOGRAM π π €π π π π β½οΈ Pronostics football sur Telegram β¨ π π°πΈπ πΎπ½ 2026-2027
@pronogram_officiel
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
2,457subscribers
-176 since we began measuring on 16 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
Register entry
| Telegram ID | -1001390257127 |
|---|---|
| Type | Channel |
| Username | @pronogram_officiel |
| Created | Between 1 March 2018 and 31 July 2021 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 15 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/pronogram_officiel |
Topic
Gambling & betting β 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 7 Nov 2026, 04:11 | 2,457 | -3 |
| 3 Nov 2026, 20:17 | 2,460 | +2 |
| 1 Nov 2026, 05:21 | 2,458 | -8 |
| 29 Oct 2026, 04:28 | 2,466 | -6 |
| 26 Oct 2026, 00:38 | 2,472 | -13 |
| 23 Oct 2026, 01:00 | 2,485 | +1 |
| 19 Oct 2026, 20:56 | 2,484 | -4 |
| 17 Oct 2026, 03:28 | 2,488 | -3 |
| 14 Oct 2026, 00:21 | 2,491 | -11 |
| 8 Oct 2026, 22:37 | 2,502 | -14 |
| 2 Oct 2026, 09:41 | 2,516 | -35 |
| 16 Sept 2026, 06:56 | 2,551 | -11 |
| 15 Sept 2026, 00:46 | 2,562 | no change |
| 12 Sept 2026, 14:40 | 2,562 | -8 |
| 8 Sept 2026, 08:57 | 2,570 | -17 |
| 2 Sept 2026, 17:56 | 2,587 | -9 |
| 30 Aug 2026, 16:34 | 2,596 | -9 |
| 27 Aug 2026, 12:24 | 2,605 | -3 |
| 24 Aug 2026, 21:55 | 2,608 | -15 |
| 20 Aug 2026, 21:28 | 2,623 | 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.
@Pronostic_Coupon_Fixed_Gratuit Β· 140,160
Telegram ranks this channel #24 of 51 here β alongside 50 others β read 16 August 2026
@parieursfoot Β· 62,100
Telegram ranks this channel #44 of 68 here β alongside 67 others β read 22 August 2026
This channel appears in 2 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 7 November 2026 β this entry's latest reading, not the date you are reading this.
βPRONOGRAM π π €π π π π β½οΈ Pronostics football sur Telegram β¨ π π°πΈπ πΎπ½ 2026-2027β (@pronogram_officiel), 2,457 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/pronogram_officiel.
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.