Telegram RegisterThe public register of Telegram
Telegram profile photo for BM2222 News

Channel

BM2222 News

@bm2222support

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

1,053subscribers

+2 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-1001317568296
TypeChannel
Username@bm2222support
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live25 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/bm2222support

Growth

1,0511,0531,0527 August 2026 — 1,051 subscribers8 August 2026 — 1,051 subscribers10 August 2026 — 1,053 subscribers16 August 2026 — 1,052 subscribers19 August 2026 — 1,051 subscribers23 August 2026 — 1,052 subscribers25 August 2026 — 1,053 subscribers7 August 202625 August 2026
7 measurements spanning 18 days, net +2. 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,051–1,053 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 17:241,053+1
23 Aug 2026, 04:041,052+1
19 Aug 2026, 09:141,051-1
16 Aug 2026, 18:061,052-1
10 Aug 2026, 17:361,053+2
8 Aug 2026, 00:191,051no change
7 Aug 2026, 20:271,051first reading

Engagement

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

Reaction mix

125 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 38.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👏4838.4%
👌3427.2%
2419.2%
🙏64.80%
💯43.20%
😭43.20%
🎉21.60%
🆒10.8%
👎10.8%
😢10.8%

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 125reactions 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 15 September 2025 to 21 June 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

21 Jun 2026, 20:56 UTC806 views3 reactionsread 8 August 2026

https://www.dmrbrescia.it/registrazione-e-verifica-annuale-id-dmr-sito-di-radioid/

👌3

20 Jun 2026, 16:06 UTC755 views6 reactionsread 8 August 2026

Community Note: RadioID Annual ID Verification https://radioid.net/

👌51

19 Jun 2026, 20:22 UTC944 views2 reactionsread 8 August 2026

https://www.dmrbrescia.it/ritardo-tempi-visualizzazione-dati-dashboard-principale-brandmeister/

2

19 Jun 2026, 19:34 UTC992 views1 reactionsread 8 August 2026

https://wiki.brandmeister.network/index.php/Italy#Ritardo_dei_tempi_di_visualizzazione_dei_dati_nella_dashboard_principale_di_BrandMeister

1

17 Jun 2026, 22:55 UTC≈1,280 viewsread 8 August 2026

https://news.brandmeister.network/new-annual-verification-process-by-radioid-net/

21 Mar 2026, 17:44 UTC≈2,610 views11 reactionsread 8 August 2026

L’attivazione del servizio AirSecurity consente di proteggere velocemente e facilmente il tuo ID DMR da usi illeciti, consentendo un accesso limitato nel tempo nella rete DMR di BM, tramite l’utilizzo del tuo ID DMR. Questa funzione è facoltativa e puoi attivarla o disattivarla tramite la Dashboard di BM. https://www.dmrbrescia.it/utilizzo-gestione-servizio-airsecurity-totp-brandmeister/

👏63👌1💯1

25 Jan 2026, 09:36 UTC≈2,380 views10 reactionsread 8 August 2026

PERCHÉ È IMPORTANTE PRATICARE UNA CORRETTA IPA: Un corretto IPA riduce gli errori di trasmissione, soprattutto durante le interruzioni di corrente, quando le radio funzionano con segnali deboli delle batterie durante le operazioni di soccorso in caso di calamità. Una lettera sbagliata può fare la differenza tra la vita e la morte. Ad esempio, durante l'eruzione del Monte Pinatubo del 1991, un singolo errore IPA nel

👏53👌2

25 Jan 2026, 09:36 UTC≈1,600 views4 reactionsread 8 August 2026

Traduzione in Italiano della pagina ufficiale SCOPO: Per dimostrare la portata internazionale del DMR. Per fornire una rete per l'interazione (anche solo per effettuare check-in) con radioamatori al di fuori dell'area locale e di un gruppo di interesse specifico (la maggior parte delle reti è limitata a una o entrambe queste tipologie). Oltre a condurre una trasmissione mondiale del TG91 del sabato, il nostro altr

4

24 Jan 2026, 21:46 UTC≈1,070 viewsread 8 August 2026

BM World Wide Check-In Join us every Saturday 16:00 UTC on Talk Group 91 on the Brandmeister Network. The World Wide Check-In is now LIVE! https://www.worldwidecheckin.net/index.php Hosted by: OH2DND with YL3IM With VU3EFZ standing by

6 Jan 2026, 16:34 UTC≈1,710 views16 reactionsread 8 August 2026

Da alcuni giorni il Team di BM2222 ha installato la nuova versione stabile del software di BrandMeister (versione 20260102-111204), che aggiunge nuove compatibilità al nostro sistema DMR con le ultimissime funzionalità previste per i dispositivi Hytera PoC, che da qualche settimana sono state sviluppate e sperimentate sulle varie versioni Beta di BM Core. https://www.dmrbrescia.it/come-connettere-i-propri-dispositivi

👌9👏52

2 Jan 2026, 12:30 UTC≈2,160 views14 reactionsread 8 August 2026

Installata nuova versione BrandMeister compatibile con le ultimissime funzionalità PoC: BrandMeister 20260102-111204

👏94👌1

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

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

“BM2222 News” (@bm2222support), 1,053 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/bm2222support.

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.