Telegram RegisterThe public register of Telegram
Telegram profile photo for ATTIVAMENTE POLVERARA

Channel

ATTIVAMENTE POLVERARA

@AttivamentePolverara

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

446subscribers

-1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001499654341
TypeChannel
Username@AttivamentePolverara
CreatedBetween 1 May 2020 and 31 December 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/AttivamentePolverara

Topic

Local community — 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 21 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 why it has no browse page of its own yet.

Growth

44644844712 August 2026 — 447 subscribers12 August 2026 — 447 subscribers27 August 2026 — 448 subscribers5 September 2026 — 447 subscribers12 September 2026 — 446 subscribers12 August 202612 September 2026
5 measurements spanning 31 days, net -1. 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 446–448 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 17:21446-1
5 Sept 2026, 13:16447-1
27 Aug 2026, 14:55448+1
12 Aug 2026, 13:01447no change
12 Aug 2026, 12:48447first reading

Engagement

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

Reaction mix

13 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 61.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
861.5%
👍323.1%
👌17.69%
🙏17.69%

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 7 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 13 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 5 February 2026 to 28 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

27 Jul 2026, 14:49 UTC227 viewsread 12 August 2026

Si informa che giovedì prossimo 30 luglio, alle ore 21.00, si terrà il Consiglio Comunale presso la Casa delle Associazioni. Qui sotto l'ordine del giorno.

10 Jul 2026, 17:01 UTC341 views3 reactionsread 12 August 2026

📞𝟏𝟏𝟔𝟏𝟏𝟕 👩‍⚕️ 𝑵𝒖𝒎𝒆𝒓𝒐 𝒑𝒆𝒓 𝒍'𝒂𝒄𝒄𝒆𝒔𝒔𝒐 𝒂𝒊 𝒔𝒆𝒓𝒗𝒊𝒛𝒊 𝒅𝒊 𝒄𝒖𝒓𝒆 𝒎𝒆𝒅𝒊𝒄𝒉𝒆 𝒏𝒐𝒏 𝒖𝒓𝒈𝒆𝒏𝒕𝒊 𝒆 𝒄𝒐𝒏𝒕𝒊𝒏𝒖𝒊𝒕𝒂̀ 𝒂𝒔𝒔𝒊𝒔𝒕𝒆𝒏𝒛𝒊𝒂𝒍𝒆 (𝒆𝒙 𝒈𝒖𝒂𝒓𝒅𝒊𝒂 𝒎𝒆𝒅𝒊𝒄𝒂). Da qualche settimana è attivo il numero di telefono unico gratuito della Regione del Veneto 𝟭𝟭𝟲𝟭𝟭𝟳 dedicato alle esigenze sanitarie non urgenti, attivo 24 ore su 24, 7 giorni su 7. ✅ Per contattare la Continuità Assistenziale (ex Guardia Medica) ✅ Per ricevere informazioni e orientamento sui serv

3

4 Jul 2026, 15:04 UTC348 viewsread 12 August 2026

𝗥𝗲𝘀𝗼𝗰𝗼𝗻𝘁𝗼 𝗱𝗲𝗹 𝗖𝗼𝗻𝘀𝗶𝗴𝗹𝗶𝗼 𝗖𝗼𝗺𝘂𝗻𝗮𝗹𝗲 𝗱𝗲𝗹 𝟲 𝗴𝗶𝘂𝗴𝗻𝗼 𝟮𝟬𝟮𝟲 🏫

3 Jul 2026, 15:11 UTC384 views1 reactionsread 12 August 2026

🌳 𝗔𝗹𝗯𝗲𝗿𝗶 𝗽𝗲𝗿 𝗹𝗮 𝗣𝗶𝗮𝗻𝘂𝗿𝗮 𝗩𝗲𝗻𝗲𝘁𝗮 🌳 Ricordiamo 𝐥𝐚 𝐬𝐜𝐚𝐝𝐞𝐧𝐳𝐚 𝐝𝐞𝐥 𝟑𝟎 𝐬𝐞𝐭𝐭𝐞𝐦𝐛𝐫𝐞 per aderire al progetto.. Ogni nucleo familiare può richiedere gratuitamente fino a 10 piantine appartenenti a specie della flora spontanea del Veneto, caratteristiche dell’antico bosco di pianura. Il progetto "Alberi per la Pianura Veneta" (https://alberinpianura.it/iniziativa.html) è promosso dalla Regione Veneto e Veneto Agricoltura per fav

👍1

11 Jun 2026, 09:40 UTC460 views2 reactionsread 12 August 2026

8️⃣ 𝑨𝒑𝒑𝒓𝒐𝒗𝒂𝒛𝒊𝒐𝒏𝒆 𝒓𝒆𝒗𝒊𝒔𝒊𝒐𝒏𝒆 𝒏𝒐𝒏 𝒔𝒕𝒓𝒖𝒕𝒕𝒖𝒓𝒂𝒍𝒆 𝒆 𝒊𝒏𝒕𝒆𝒈𝒓𝒂𝒛𝒊𝒐𝒏𝒆 𝒂𝒅𝒅𝒆𝒏𝒅𝒖𝒎 𝒊𝒅𝒓𝒂𝒖𝒍𝒊𝒄𝒐 𝑶𝒔𝒔𝒆𝒓𝒗𝒂𝒕𝒐𝒓𝒊𝒐 𝒅𝒆𝒊 𝑪𝒊𝒕𝒕𝒂𝒅𝒊𝒏𝒊 𝒂𝒍 𝑷𝒊𝒂𝒏𝒐 𝒅𝒊 Il Sindaco spiega che l’adesione all’Osservatorio dei Cittadini prevede 16 attività, di cui 8 utili a completare il Piano di Protezione Civile. Il consigliere De Lazzari segnala errori e dati non aggiornati negli allegati e propone alcune integrazioni. Chiede inoltre tempi per l’avvio delle attività e d

1👌1

11 Jun 2026, 09:40 UTC379 views0 reactionsread 12 August 2026

𝗣𝘂𝗻𝘁𝗶 𝘀𝗮𝗹𝗶𝗲𝗻𝘁𝗶 𝗱𝗲𝗹 𝗖𝗼𝗻𝘀𝗶𝗴𝗹𝗶𝗼 𝗖𝗼𝗺𝘂𝗻𝗮𝗹𝗲 𝗱𝗲𝗹 𝟮𝟵 𝗮𝗽𝗿𝗶𝗹𝗲 𝟮𝟬𝟮𝟲 🏫 2️⃣ 𝑨𝒑𝒑𝒓𝒐𝒗𝒂𝒛𝒊𝒐𝒏𝒆 𝒓𝒆𝒏𝒅𝒊𝒄𝒐𝒏𝒕𝒐 𝒅𝒆𝒍𝒍𝒂 𝒈𝒆𝒔𝒕𝒊𝒐𝒏𝒆 𝒆𝒔𝒆𝒓𝒄𝒊𝒛𝒊𝒐 2025 Il Vicesindaco segnala un avanzo di circa 447.000 €, di cui oltre la metà vincolati, e sottolinea la necessità di completare gli investimenti e chiarire la gestione del teleriscaldamento. Il consigliere De Lazzari chiede spiegazioni su alcune mancate entrate, spese poco chiare e sull’uso dei residui,

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“ATTIVAMENTE POLVERARA” (@AttivamentePolverara), 446 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/AttivamentePolverara.

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.