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

Channel

Vivere Senigallia

@viveresenigallia

Has discussion group

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

5,639subscribers

-34 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001006851312
TypeChannel
Username@viveresenigallia
CreatedBetween 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live9 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/viveresenigallia

Growth

5,6395,6735,6565 August 2026 — 5,673 subscribers7 August 2026 — 5,669 subscribers9 August 2026 — 5,666 subscribers12 August 2026 — 5,662 subscribers16 August 2026 — 5,659 subscribers19 August 2026 — 5,667 subscribers22 August 2026 — 5,664 subscribers26 August 2026 — 5,654 subscribers30 August 2026 — 5,654 subscribers31 August 2026 — 5,655 subscribers9 September 2026 — 5,639 subscribers5 August 20269 September 2026
11 measurements spanning 34 days, net -34. 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 5,634–5,678 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 07:015,639-16
31 Aug 2026, 16:475,655+1
30 Aug 2026, 19:465,654no change
26 Aug 2026, 01:035,654-10
22 Aug 2026, 19:555,664-3
19 Aug 2026, 17:355,667+8
16 Aug 2026, 07:055,659-3
12 Aug 2026, 09:245,662-4
9 Aug 2026, 18:425,666-3
7 Aug 2026, 00:425,669-4
5 Aug 2026, 22:155,673first 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.

Forward network

Republished by

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

VS - Arcevia
@vs_Arcevia · 127
2 posts
VS - Castelleone di Suasa
@VS_Castelleone · 60
2 posts
VS - Corinaldo
@VS_Corinaldo · 119
2 posts
VS - Ostra
@VS_Ostra · 145
2 posts
VS - Ostra Vetere
@VS_Ostra_Vetere · 82
2 posts
VS - Serra de' Conti
@VS_Serra · 94
2 posts
Vivere Caltanissetta
@vivere_caltanissetta · 72
1 post
Vivere Malta
@vivere_malta · 28
1 post
Vivere News
@vivere_news · 384
1 post
Vivere Ragusa
@vivere_ragusa · 109
1 post
Vivere Alessandria
@viverealessandria · 35
1 post
Vivere Aosta
@vivereaosta · 58
1 post
Vivere Arezzo
@viverearezzo · 124
1 post
Vivere Avezzano
@vivereavezzano · 76
1 post
Vivere Bari
@viverebari · 313
1 post
Vivere Barletta
@viverebarletta · 47
1 post
Vivere Basilicata
@viverebasilicata · 66
1 post
Vivere Bergamo
@VivereBergamo · 233
1 post
Vivere Bolzano
@viverebolzano · 93
1 post
Vivere Brescia
@VivereBrescia · 140
1 post
Vivere Brindisi
@viverebrindisi · 76
1 post
Vivere Campobasso
@viverecampobasso · 44
1 post
Vivere Carbonia
@viverecarbonia · 33
1 post
Vivere Castelfranco Emilia
@viverecastelfranco · 64
1 post
Vivere Catanzaro
@viverecatanzaro · 106
1 post
Vivere Cento
@viverecento · 17
1 post
Vivere Chieti
@viverechieti · 87
1 post
Vivere Comacchio
@viverecomacchio · 43
1 post
Vivere Como
@viverecomo · 84
1 post
Vivere Corigliano Rossano
@viverecorigliano · 69
1 post
Vivere Cremona
@viverecremona · 33
1 post
Vivere Crotone
@viverecrotone · 86
1 post
Vivere Cuneo
@viverecuneo · 44
1 post
Vivere Enna
@vivereenna · 55
1 post
Vivere Faenza
@viverefaenza · 40
1 post
Vivere Fasano
@VivereFasano · 197
1 post
Vivere Ferrara
@vivereferrara · 120
1 post
Vivere Fidenza
@viverefidenza · 24
1 post
Vivere Firenze
@viverefirenze · 220
1 post
Vivere Foggia
@viverefoggia · 150
1 post
Vivere Giulianova
@viveregiulianova · 64
1 post
Vivere Imola
@vivereimola · 54
1 post
Vivere Imperia
@vivereimperia · 37
1 post
Vivere Lanciano
@viverelanciano · 49
1 post
Vivere L'Aquila
@viverelaquila · 89
1 post
Vivere Salento
@viverelecce · 217
1 post
Vivere Lodi
@viverelodi · 19
1 post
Vivere Lugo
@viverelugo · 26
1 post
Vivere Massa
@viveremassa · 20
1 post
Vivere Matera
@viverematera · 90
1 post
Vivere Mendrisio
@VivereMendrisio · 52
1 post
Vivere Milano
@viveremilano · 553
1 post
Vivere Monza
@VivereMonza · 98
1 post
Vivere Napoli
@viverenapoli · 648
1 post
Vivere Novara
@viverenovara · 76
1 post
Vivere Nuoro
@viverenuoro · 81
1 post
Vivere Oristano
@vivereoristano · 38
1 post
Vivere Osimo
@vivereosimo · 807
1 post
Vivere Padova
@viverepadova · 193
1 post
Vivere Paola
@viverepaola · 7
1 post
Vivere Pavia
@viverepavia · 51
1 post
Vivere Pescara
@viverepescara · 272
1 post
Vivere Pistoia
@viverepistoia · 48
1 post
Vivere Pordenone
@viverepordenone · 67
1 post
Vivere Potenza
@viverepotenza · 93
1 post
Vivere Prato
@vivereprato · 79
1 post
Vivere Puglia
@viverepuglia · 214
1 post
Vivere Recanati e Porto Recanati
@vivererecanati · 429
1 post
Vivere Salerno
@viveresalerno · 170
1 post
Vivere San Marino
@VivereSanMarino · 79
1 post
Vivere Sassari
@viveresassari · 142
1 post
Vivere Savona
@viveresavona · 72
1 post
Vivere Siena
@viveresiena · 58
1 post
Vivere Siracusa
@viveresiracusa · 117
1 post
Vivere Sondrio
@viveresondrio · 22
1 post
Vivere Sulmona
@viveresulmona · 31
1 post
Vivere Taranto
@viveretaranto · 176
1 post
Vivere Teramo
@vivereteramo · 102
1 post
Vivere Trapani
@viveretrapani · 135
1 post
Vivere Trento
@viveretrento · 135
1 post
Vivere Treviso
@viveretreviso · 159
1 post
Vivere Trieste
@viveretrieste · 110
1 post
Vivere Varese
@viverevarese · 77
1 post
Vivere Vasto
@viverevasto · 49
1 post
Vivere Venezia
@viverevenezia · 201
1 post
Vivere Verbania
@vivereverbania · 35
1 post
Vivere Verona
@vivereverona · 289
1 post
Vivere Vibo Valentia
@viverevibo · 60
1 post
Vivere Vicenza
@viverevicenza · 137
1 post
VJ - Chiaravalle
@vj_Chiaravalle · 103
1 post

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

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

“Vivere Senigallia” (@viveresenigallia), 5,639 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/viveresenigallia.

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.