Telegram RegisterThe public register of Telegram
Telegram profile photo for Remontti

Channel

Remontti

@blogremontti

On this record: Growth · Engagement · Reactions · Posts · Polls · Handles named that no longer answer · Cite this entry

1,310subscribers

-6 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001096225751
TypeChannel
Username@blogremontti
CreatedBetween 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/blogremontti

Growth

1,3101,3161,3137 August 2026 — 1,316 subscribers7 August 2026 — 1,316 subscribers11 August 2026 — 1,313 subscribers15 August 2026 — 1,312 subscribers25 August 2026 — 1,314 subscribers30 August 2026 — 1,313 subscribers8 September 2026 — 1,310 subscribers7 August 20268 September 2026
7 measurements spanning 31 days, net -6. 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 1,309–1,317 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 03:161,310-3
30 Aug 2026, 14:261,313-1
25 Aug 2026, 03:181,314+2
15 Aug 2026, 03:071,312-1
11 Aug 2026, 20:121,313-3
7 Aug 2026, 22:311,316no change
7 Aug 2026, 20:261,316first reading

Engagement

20 posts held, back to 3 December 2024the 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 14 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

553 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 37.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👏20737.4%
20537.1%
🎉6411.6%
👍519.22%
🔥183.25%
🤩71.27%
👎10.181%

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 19 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 553 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 3 December 2024 to 14 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

14 Jul 2026, 20:47 UTC810 views33 reactionsread 7 August 2026
Photo

Servidor DNS #1 – Recursivo com BIND 9.20 no Debian 13 (Trixie) https://blog.remontti.com.br/8358

21👏12

Signed Rudimar Remontti

15 Mar 2026, 15:34 UTC≈1,740 views20 reactionsread 7 August 2026
Photo

Está lançando oficialmente a nova versão 3!!! 🚀 🖥 rrflow.com.br 📖 doc.rrflow.com.br

👏13🎉4🔥2👍1

Signed Rudimar Remontti

17 Feb 2026, 19:43 UTC≈1,930 views8 reactionsread 7 August 2026
Photo

Para que não pode participar do meet 🎬 https://youtu.be/UL38OzlIppQ

👍5👏21

Signed Rudimar Remontti

17 Feb 2026, 15:34 UTC≈1,600 views2 reactionsread 7 August 2026

Versa 😅 IAs ... Versão*

🔥2

Signed Rudimar Remontti

17 Feb 2026, 14:35 UTC≈1,680 views9 reactionsread 7 August 2026
Photo

Hoje as 14h espero vcs! https://meet.remontti.com.br/rrflow3

👏9

Signed Rudimar Remontti

14 Aug 2025, 22:06 UTC≈2,430 views1 reactionsread 7 August 2026

🎥 Links para hoje 14/08 às 19:50h 🕙 - Meet: meet.remontti.com.br/cursorrflow - Youtube: youtube.com/live/Oek3GqK5tk8 Primeira aula dia 12/08: youtube.com/live/IPR_I982C5A

1

Signed Rudimar Remontti

13 Aug 2025, 17:15 UTC≈2,250 views49 reactionsread 7 August 2026
Photo

Instalação do Debian 13 Trixie limpa passo-a-passo (netinst) https://blog.remontti.com.br/8267

👍21👏175🔥4🤩2

Signed Rudimar Remontti

12 Aug 2025, 22:12 UTC≈2,010 views6 reactionsread 7 August 2026

Já já 🕙 🕔 19:50h Ao vivo Youtube youtube.com/live/IPR_I982C5A Meet (quem quiser interagir ao vivo por áudio) meet.remontti.com.br/cursorrflow

🤩32👏1

Signed Rudimar Remontti

11 Aug 2025, 14:49 UTC≈2,210 views14 reactionsread 7 August 2026
Photo

⚠️ Atualização sobre o Curso RR Flow Pessoal, já passamos de 320 inscritos! 🔥 📅 Datas: 12 e 14 de agosto – início às 19:50h 💻 Onde assistir: - Meet (interação ao vivo): meet.remontti.com.br/cursorrflow - YouTube (transmissão ao vivo): Canal @RudimarRemontti - - Link do Dia 1 (12/08): youtube.com/live/IPR_I982C5A - - Link do Dia 2 (14/08): será divulgado em breve! 💡 O Meet será para quem quiser interagir ao vivo, m

👏83🔥3

Signed Rudimar Remontti

4 Aug 2025, 15:08 UTC≈2,120 views24 reactionsread 7 August 2026
Photo

Curso 100% grátis! 📕 O que você vai aprender: - Instalação e uso prático do nfdump - Entendimento completo do funcionamento do nfdump (sem depender do RR Flow) - Fundamentos de análise de tráfego em redes reais - Como o RR Flow utiliza o nfdump como motor por trás de sua API - Passo a passo por toda a documentação do RR Flow, com dicas práticas Para quem é esse curso? - Para provedores, analistas de redes, sys

13👏9👍1🔥1

Signed Rudimar Remontti

26 Jun 2025, 14:27 UTC≈1,960 viewsread 7 August 2026
Poll

Galera, tô curioso: você já conhece ou já usou o RR Flow?

  1. ✌️ Já uso e recomendo!13%
  2. 😒 Já testei, mas ainda não assino.10%
  3. 😮 Tô testando agora.1%
  4. 🫧 Conheço, mas nunca testei.55%
  5. 🤗 Não conhecia, acabei de descobrir!11%
  6. 🙄 Só tô aqui pelo grupo mesmo.9%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Signed Rudimar Remontti

23 Jun 2025, 22:21 UTC≈2,000 views48 reactionsread 7 August 2026
Photo

📦 Versão 2.0 Codename: Fátima Esta versão traz uma profunda evolução para a plataforma, com destaque para a reformulação do painel administrativo, mais moderno, intuitivo e multilíngue. A instalação e configuração das dashboards estão totalmente automatizadas, facilitando a experiência do usuário. A integração com o Grafana também foi aprimorada e passou a ser automática, eliminando etapas manuais. Novas funcionalid

35👍6👏5🤩2

Signed Rudimar Remontti

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

26 Jun 2025, 14:27 UTCAnonymous Poll247 voters

Galera, tô curioso: você já conhece ou já usou o RR Flow?

  1. ✌️ Já uso e recomendo!13%
  2. 😒 Já testei, mas ainda não assino.10%
  3. 😮 Tô testando agora.1%
  4. 🫧 Conheço, mas nunca testei.55%
  5. 🤗 Não conhecia, acabei de descobrir!11%
  6. 🙄 Só tô aqui pelo grupo mesmo.9%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 3 December 2024 to 14 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“Remontti” (@blogremontti), 1,310 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/blogremontti.

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.