Telegram RegisterThe public register of Telegram
Telegram profile photo for Bergische Blaulichtnews

Channel

Bergische Blaulichtnews

@bergischeblaulichtnews

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

7,390subscribers

-148 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001276513324
TypeChannel
Username@bergischeblaulichtnews
DescriptionNews aus dem Bergischen Städtedreieck und dem nahen Umfeld. Fotos, Video und Infos zu allen brandaktuellen News und Ereignissen. Produkt von Oelbermann-Fotografie. Die gezeigten Bilder unterliegen, sofern nicht anders angegeben, dem Urheberrecht.
Created26 December 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/bergischeblaulichtnews

Topic

National news — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 the other topics.

Growth

7,3907,5387,4647 August 2026 — 7,538 subscribers7 August 2026 — 7,538 subscribers7 August 2026 — 7,537 subscribers10 August 2026 — 7,530 subscribers14 August 2026 — 7,521 subscribers20 August 2026 — 7,513 subscribers24 August 2026 — 7,505 subscribers27 August 2026 — 7,497 subscribers30 August 2026 — 7,490 subscribers3 September 2026 — 7,488 subscribers9 September 2026 — 7,481 subscribers13 September 2026 — 7,469 subscribers17 September 2026 — 7,461 subscribers25 September 2026 — 7,442 subscribers4 October 2026 — 7,440 subscribers10 October 2026 — 7,437 subscribers14 October 2026 — 7,426 subscribers17 October 2026 — 7,434 subscribers20 October 2026 — 7,426 subscribers23 October 2026 — 7,421 subscribers26 October 2026 — 7,414 subscribers29 October 2026 — 7,411 subscribers1 November 2026 — 7,405 subscribers5 November 2026 — 7,401 subscribers8 November 2026 — 7,392 subscribers13 November 2026 — 7,390 subscribers7 August 202613 November 2026
26 measurements spanning 98 days, net -148. 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 7,368–7,560 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
13 Nov 2026, 20:487,390-2
8 Nov 2026, 17:597,392-9
5 Nov 2026, 01:107,401-4
1 Nov 2026, 17:287,405-6
29 Oct 2026, 10:397,411-3
26 Oct 2026, 14:157,414-7
23 Oct 2026, 10:387,421-5
20 Oct 2026, 10:167,426-8
17 Oct 2026, 04:077,434+8
14 Oct 2026, 14:107,426-11
10 Oct 2026, 19:567,437-3
4 Oct 2026, 22:157,440-2
25 Sept 2026, 23:007,442-19
17 Sept 2026, 12:567,461-8
13 Sept 2026, 03:217,469-12
9 Sept 2026, 01:027,481-7
3 Sept 2026, 08:327,488-2
30 Aug 2026, 17:347,490-7
27 Aug 2026, 20:387,497-8
24 Aug 2026, 12:037,505first reading

Engagement

292 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 44 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.3%
avg views ÷ 7,390 subscribers
Avg views / post
1,720
136 posts measured
Reaction rate
1.10%
reactions ÷ views · ER floor
Posts in window
136
of 292 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held292 (5 August 2026 – 17 November 2026)
Views total233,944
Reactions total2,577
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 20:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈18,300
Videos
≈115
Links
≈1,330

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

5,614 reactions across 292 posts, in 7 distinct kinds. The most used accounts for 48.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😱2,70448.2%
🔥1,51026.9%
😡5449.69%
👍3225.74%
😢2554.54%
🐳2364.20%
☃430.766%

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 292 of the 292 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 5,614 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 292 most recent posts we hold, published 5 August 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 4 of 136 posts held from the last 30 days (2.94%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 20:20 UTC275 views5 reactionsread 17 November 2026

🚨 Wuppertal, Rauental: Wassereinbruch

🐳4😱1

17 Nov 2026, 20:06 UTC487 views9 reactionsread 17 November 2026

🚨 Wuppertal, Bahnstraße: Wassereinbruch

🐳8😱1

17 Nov 2026, 20:02 UTC608 views10 reactionsread 17 November 2026

🚨 Solingen, A46: Verkehrsunfall zwischen AS Haan-Ost und AK Sonnborn in FR Wuppertal

😱9🔥1

17 Nov 2026, 19:58 UTC668 views10 reactionsread 17 November 2026

🚨 Wuppertal, Loher Straße: Wassereinbruch

🐳9🔥1

17 Nov 2026, 19:57 UTC709 views10 reactionsread 17 November 2026

🚨 Wuppertal, Friedrich-Ebert-Straße: Wassereinbruch

🐳8🔥1😱1

17 Nov 2026, 19:55 UTC717 views9 reactionsread 17 November 2026

🚨 Solingen, Weyerstraße: Hilfeleistungseinsatz

😱7🔥1😢1

17 Nov 2026, 19:55 UTC733 views10 reactionsread 17 November 2026

🚨 Wuppertal, Berliner Straße: Wassereinbruch

🐳8🔥1😱1

17 Nov 2026, 19:55 UTC716 views11 reactionsread 17 November 2026

🚨 Wuppertal, Briller Straße: Wassereinbruch

🐳9🔥1😱1

17 Nov 2026, 19:50 UTC770 views12 reactionsread 17 November 2026

🚨 Wuppertal, Schellenbecker Straße: Wassereinbruch

🐳9😱2🔥1

17 Nov 2026, 19:49 UTC796 views12 reactionsread 17 November 2026

🚨 Wuppertal, Uellendahler Straße: Wassereinbruch

🐳9😱2🔥1

17 Nov 2026, 19:48 UTC785 views13 reactionsread 17 November 2026

🚨 Wuppertal, Steinbeck: Wassereinbruch

🐳10😱2🔥1

17 Nov 2026, 18:46 UTC≈1,080 views17 reactionsread 17 November 2026

++ Crash auf der A1 mit mehreren Fahrzeugen ++ Am Morgen des 17.11.2026 erreichten mehrere Notrufe die Feuer- und Rettungsleitstelle der Berufsfeuerwehr Remscheid. Es wurde ein Verkehrsunfall mit einem LKW und mehreren PKW auf der BAB 1 in Fahrtrichtung Köln gemeldet. Die Unfallstelle befand sich zwischen der Auffahrt Remscheid und der Raststätte Remscheid West und erstreckte sich über ca. 200 Meter. Es waren insges…

😱14👍3

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

Posts edited after publishing

@bergischeblaulichtnews edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 November 2026
Most recent edit
9 November 2026

Forward network

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

“Bergische Blaulichtnews” (@bergischeblaulichtnews), 7,390 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/bergischeblaulichtnews.

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.