Telegram RegisterThe public register of Telegram
Telegram profile photo for Vivere Brindisi

Channel

Vivere Brindisi

@viverebrindisi

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

75subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001371073076
TypeChannel
Username@viverebrindisi
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live12 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/viverebrindisi

Growth

757675.56 August 2026 — 76 subscribers9 August 2026 — 76 subscribers12 September 2026 — 75 subscribers6 August 202612 September 2026
3 measurements spanning 37 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 75–76 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 15:3675-1
9 Aug 2026, 21:0276no change
6 Aug 2026, 22:5476first reading

Engagement

20 posts held, back to 21 April 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 3 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 Aug 2026, 11:12 UTC18 viewsread 9 August 2026
Photo

Vaccini, Lacerenza (Asl Foggia): "Anti-Hpv in centri di screening e anche con il camper" https://vivere.me/g1aq

29 Jul 2026, 20:32 UTC30 viewsread 9 August 2026
Photo

Crollo in un cantiere a Mesagne, un morto e un ferito https://vivere.me/gZwz

29 Jul 2026, 12:17 UTC32 viewsread 9 August 2026
Photo

Crollo in un cantiere a Mesagne, un morto e un ferito https://vivere.me/gZqA

15 Jul 2026, 08:20 UTC36 viewsread 9 August 2026
Forwarded from @viveresenigallia

Tutte le notizie in tempo reale su Telegram 🇮🇹 Italia | 🇪🇺 Europa | 🇸🇲 San Marino | 🇲🇹 Malta 🗞 PIEMONTE E VAL D'AOSTA 🦓 Torino | 🏔 Aosta 📰 Le altre città 🗞 LIGURIA 🚢 Genova |Sanremo 📰 Le altre città 🗞 LOMBARDIA 🥂 Milano |🍸 Saronno |Cologno 📰 Le altre città 🗞 TICINO 🏦 Lugano |🫕 Mendrisio 🍫 Bellinzona |🌰 Locarno 🗞 TRENTINO-ALTO ADIGE 🍏 Trento |🚡 Bolzano 🗻 Merano |🔔 Rovereto 🗞 VENETO 🏝 Treviso |😇 Pado

14 Jul 2026, 07:36 UTC34 viewsread 9 August 2026
Photo

Perché le fotografie estive sono sempre le più belle https://vivere.me/gWKY

7 Jul 2026, 10:40 UTC47 viewsread 9 August 2026
Photo

Ricci (Eni): Brindisi è "una grande riconversione industriale" https://vivere.me/gVG6

6 Jul 2026, 20:08 UTC44 viewsread 9 August 2026
Photo

Decaro: "Con la prima pietra del polo di Brindisi nuova stagione industriale" https://vivere.me/gVCs

6 Jul 2026, 20:08 UTC36 viewsread 9 August 2026
Photo

Ricci (Eni): "Polo di Brindisi operativo a tappe, prima sezione in esercizio a metà 2027" https://vivere.me/gVCp

6 Jul 2026, 20:08 UTC34 viewsread 9 August 2026
Photo

Urso: "Prima pietra per far diventare Brindisi polo della transizione" https://vivere.me/gVCo

6 Jul 2026, 20:00 UTC38 viewsread 9 August 2026
Photo

Al via a Brindisi il cantiere per il nuovo polo di Eni per le batterie stazionarie https://vivere.me/gVCm

18 Jun 2026, 14:24 UTC57 viewsread 9 August 2026
Photo

Latiano: inneggiava alla jihad, arrestato 30enne palestinese https://vivere.me/gSkT

4 Jun 2026, 17:04 UTC75 viewsread 9 August 2026
Photo

Confindustria Nautica, a Borgo Egnazia l'assemblea dei soci https://vivere.me/gPOP

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

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

“Vivere Brindisi” (@viverebrindisi), 75 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/viverebrindisi.

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.