Telegram RegisterThe public register of Telegram
Telegram profile photo for ABPPF - Canal de Informações

Channel

ABPPF - Canal de Informações

@ABPPF

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

979subscribers

-8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001792654384
TypeChannel
Username@ABPPF
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/ABPPF

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 19 September 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

979990984.57 August 2026 — 987 subscribers8 August 2026 — 987 subscribers15 August 2026 — 986 subscribers22 August 2026 — 987 subscribers28 August 2026 — 990 subscribers5 September 2026 — 989 subscribers12 September 2026 — 986 subscribers8 October 2026 — 979 subscribers7 August 20268 October 2026
8 measurements spanning 62 days, net -8. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 977–992 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 16:36979-7
12 Sept 2026, 20:37986-3
5 Sept 2026, 13:21989-1
28 Aug 2026, 20:17990+3
22 Aug 2026, 04:38987+1
15 Aug 2026, 06:36986-1
8 Aug 2026, 00:35987no change
7 Aug 2026, 22:15987first reading

Engagement

20 posts held, back to 13 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

358 reactions across 15 posts, in 13 distinct kinds. The most used accounts for 29.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍10529.3%
👏7621.2%
🤡5916.5%
❤5214.5%
😢328.94%
👎174.75%
🏆102.79%
🤬20.559%
⚡10.279%
👌10.279%
🔥10.279%
🙏10.279%
🤯10.279%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 15 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 358 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 April 2026 to 31 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

31 Jul 2026, 16:43 UTC355 views60 reactionsread 8 August 2026

Comunicado Oficial: Recuperação Judicial (Grupo 123 Milhas) Prezados, Informamos que, devido à recente mudança na equipe jurídica da Associação Brasileira de Participantes de Programas de Fidelidade (ABPPF), a orientação anterior sobre a Recuperação Judicial do Grupo 123 Milhas foi atualizada. A recomendação passada de não aderir se baseava na intenção da ABPPF de ajuizar uma Ação Civil Pública. Contudo, em virtude …

🤡54👎4🤬2

30 Jul 2026, 13:07 UTC399 views33 reactionsread 8 August 2026

INFORME JURÍDICO: Liberdade de Cessão e Transferência de Milhas Aéreas O Tribunal de Justiça de Minas Gerais (TJMG) reconhece abusividade em restrições do programa de fidelidade – Julho de 2026 Prezados, A 9ª Câmara Cível do Tribunal de Justiça de Minas Gerais (TJMG) decidiu, por maioria de votos, que são abusivas e nulas as cláusulas contratuais da Azul Linhas Aéreas que limitavam o uso e a cessão de milhas a terc…

👏23❤7👍3

11 Jul 2026, 00:13 UTC655 views36 reactionsread 8 August 2026
Photo

INFORME JURÍDICO: RECUPERAÇÃO JUDICIAL (123 MILHAS) Prezados, Informamos que não há novas atualizações no processo de Recuperação Judicial da 123 Milhas Atenciosamente, Associação Brasileira de Participantes de Programas de Fidelidade

👍17😢15👎3👌1

19 Jun 2026, 21:16 UTC894 views24 reactionsread 8 August 2026
Photo

INFORME JURÍDICO: RECUPERAÇÃO JUDICIAL (123 MILHAS) Prezados, Informamos que não há novas atualizações no processo de Recuperação Judicial da 123 Milhas Atenciosamente, Associação Brasileira de Participantes de Programas de Fidelidade

😢17👎5❤1🤯1

30 May 2026, 12:04 UTC≈1,060 views16 reactionsread 8 August 2026

INFORME JURÍDICO: DIREITOS DO CONSUMIDOR NO CANCELAMENTO DE PASSAGEM COM MILHAS Regras de reembolso, taxas e prazos para devolução de pontos Prezados, Informamos as diretrizes jurídicas vigentes sobre o direito ao reembolso de milhas e pontos em casos de cancelamento de passagens aéreas, seja por iniciativa do passageiro ou por parte da companhia aérea. Cancelamento por Iniciativa do Passageiro: O consumidor tem o …

🏆10❤6

22 May 2026, 18:45 UTC918 views32 reactionsread 8 August 2026

INFORME JURÍDICO: ATUALIZAÇÃO SOBRE A RECUPERAÇÃO JUDICIAL (123 MILHAS) Frustração na penhora de contas dos sócios e os próximos passos Prezados, Informamos as atualizações mais recentes sobre as tentativas de bloqueio patrimonial no processo que envolve o Grupo 123 Milhas, com foco nas medidas de responsabilização dos sócios-administradores. Resumo das Atualizações: A justiça do Rio de Janeiro determinou o arresto…

👍23👎5👏2⚡1❤1

15 May 2026, 18:48 UTC858 views15 reactionsread 8 August 2026

INFORME JURÍDICO: IMPACTOS DA REFORMA TRIBUTÁRIA SOBRE AS MILHAS Novas regras de tributação para o setor de milhas Prezados, Informamos as atualizações sobre como a Reforma Tributária (PEC 45/2019) deve afetar o mercado de milhas e pontos. A transição para o novo sistema tributário traz mudanças na forma como as empresas de fidelidade são taxadas. Resumo das Atualizações: O atual modelo (PIS/Cofins/ISS) será substi…

❤8👍7

8 May 2026, 20:58 UTC853 views19 reactionsread 8 August 2026

Informe Jurídico: Penhora de Milhas para Quitação de Dívidas STJ inicia julgamento sobre a natureza jurídica e penhorabilidade de milhas Prezados, Informamos as atualizações mais recentes sobre o julgamento do Recurso Especial nº 2.198.485 pela 3ª turma do Superior Tribunal de Justiça (STJ), que discute se os pontos e milhas aéreas podem ser penhorados para o pagamento de dívidas cíveis. Resumo das Atualizações: A…

❤10👍9

Showing the 12 most recent of 20 posts we hold for @ABPPF. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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.

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 8 October 2026 — this entry's latest reading, not the date you are reading this.

“ABPPF - Canal de Informações” (@ABPPF), 979 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/ABPPF.

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.