Bestelbus in Geesteren verwoest door brand https://www.112tubbergen.nl/bestelbus-in-geesteren-verwoest-door-brand/

Channel
112Tubbergen.nl
@tubbergen112
On this record: Growth · Engagement · Posts · Cite this entry
21subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001298231987 |
|---|---|
| Type | Channel |
| Username | @tubbergen112 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/tubbergen112 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 11:55 | 21 | +1 |
| 24 Aug 2026, 00:28 | 20 | -1 |
| 11 Aug 2026, 14:46 | 21 | no change |
| 7 Aug 2026, 23:59 | 21 | first reading |
Engagement
20 posts held, back to 18 July 2022 — the 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 25 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Aanrijding met letsel op de Veendijk in Mander https://www.112tubbergen.nl/aanrijding-met-letsel-op-de-veendijk-in-mander/
Auto aangetroffen in sloot langs Uelserweg in Mander, bestuurder ontbreekt https://www.112tubbergen.nl/auto-aangetroffen-in-sloot-langs-uelserweg-in-mander-bestuurder-ontbreekt/
Forse schade bij ongeval in Fleringen https://www.112tubbergen.nl/forse-schade-bij-ongeval-in-fleringen/
Schuurbrand in Albergen https://www.112tubbergen.nl/schuurbrand-in-albergen/
Ravage na ernstig ongeval in Reutum https://www.112dinkelland.nl/ravage-na-ernstig-ongeval-in-reutum/
Motorrijder gewond na aanrijding met automobilist in Fleringen https://www.112tubbergen.nl/motorrijder-gewond-na-aanrijding-met-automobilist-in-fleringen/
Uitslaande brand in loods Vasse | www.112Tubbergen.nl https://www.112tubbergen.nl/uitslaande-brand-in-loods-vasse/
Schade bij aanrijding in Reutum https://www.112tubbergen.nl/schade-bij-aanrijding-in-reutum/
Ongeval tussen twee automobilisten op N343 in Reutum https://www.112tubbergen.nl/ongeval-tussen-twee-automobilisten-op-n343-in-reutum/
Ongeval met meerdere voertuigen in Reutum, persoon naar het ziekenhuis https://www.112tubbergen.nl/ongeval-met-meerdere-voertuigen-in-reutum-persoon-naar-het-ziekenhuis/
🚨Nieuws🚨 18-jarige man uit Tubbergen omgekomen bij ongeval in Geesteren https://www.112tubbergen.nl/18-jarige-man-uit-tubbergen-omgekomen-bij-ongeval-in-geesteren/
Showing the 12 most recent of 20 posts we hold for @tubbergen112. 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“112Tubbergen.nl” (@tubbergen112), 21 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/tubbergen112.
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.