Uit de testen van het nieuwe systeem zien we toch nog het een en ander fout gaan. We werken hiervoor aan oplossingen. Wanneer dat opgelost is zullen de berichten ook weer in dit kanaal geplaatst worden. Tot die tijd moet je even de kanalen joinen die we hierboven hebben gestuurd.

Channel
Helikopters | 112Hub.nl
@helikopters
On this record: Growth · Engagement · Posts · Citations · Cite this entry
889subscribers
-18 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 | -1001221804263 |
|---|---|
| Type | Channel |
| Username | @helikopters |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/helikopters |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 02:55 | 889 | -11 |
| 28 Aug 2026, 20:56 | 900 | -5 |
| 14 Aug 2026, 16:34 | 905 | -1 |
| 8 Aug 2026, 05:47 | 906 | -1 |
| 7 Aug 2026, 06:00 | 907 | no change |
| 7 Aug 2026, 05:50 | 907 | first reading |
Engagement
20 posts held, back to 2 March 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 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 11 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
De verwachting is dat eind deze week, volgende week ergens de meldingen ook weer in deze groep gaan komen. Zoals het er nu uit ziet gaan we enkel de melding als een heli is vertrokken in deze groep delen. Wil je dus ook weten wanneer een heli land, of geannuleerd wordt dan zul je toch het kanaal van de heli zelf moeten volgen. Dit omdat het anders teveel meldingen in deze groep gaan worden.
Meldingen worden hier nu even tijdelijk niet gestuurd. Het aantal meldingen dat hier binnenkomt gaat fors omhoog omdat we niet meer alleen sturen wanneer een heli is gaan vliegen, maar ook wanneer een heli is geland. We hebben ook per Lifeliner een losse groep waar je alleen de meldingen van die Lifeliner krijgt. Linkjes: Algemeen kanaal (alle heli-meldingen): https://t.me/helikopters Lifeliner 1 (Amsterdam): htt…
Lifeliner 4 is airborne Call Sign: LIFELN4 Registration Number: PH-LLN Squawk Code: 6224
Lifeliner 2 is airborne Call Sign: LIFELN2 Registration Number: PH-UMC Squawk Code: 6222 To: Poeldijk Latest message 16.57u - A1 (DIA: ja) AMBU 17992 A256 Li - Kp de Poel Goes GOES bon 35014
Lifeliner 3 is airborne Call Sign: LIFELN3 Registration Number: PH-DOC Squawk Code: 6223 Latest message 16.22u - A1 Ambu 08993 - Schoolweg, Elst UT Rit 69661, regio 09
Lifeliner 1 is airborne Call Sign: LIFELN1 Registration Number: PH-MAA Squawk Code: 6221 Latest message 15.59u - A1 (Contact MKA, MMT) (DIA) 13991 Pastoor Gillisstraat 5121 Rijen 20572 regio 20
Lifeliner 4 is airborne Call Sign: LIFELN4 Registration Number: PH-LLN Squawk Code: 6224
Lifeliner 1 is airborne Call Sign: LIFELN1 Registration Number: PH-MAA Squawk Code: 6221 Latest message 15.59u - A1 (Contact MKA, MMT) (DIA) 13991 Pastoor Gillisstraat 5121 Rijen 20572 regio 20
Lifeliner 3 is airborne Call Sign: LIFELN3 Registration Number: PH-DOC Squawk Code: 6223 To: Barneveld Latest message 15.52u - A1 Ambu 08993 Valkseweg Barneveld Rit 69602 MKA GLM 07
Lifeliner 2 is airborne Call Sign: LIFELN2 Registration Number: PH-UMC Squawk Code: 6222 To: Zoetermeer Latest message 15.14u - A0 AMBU 17992 Roxenissestraat 2729GH Zoetermeer ZOETMR bon 34947
Lifeliner 1 is airborne Call Sign: LIFELN1 Registration Number: PH-MAA Squawk Code: 6221 To: Kudelstaart Latest message 14.00u - A1 13991 Kudelstaartseweg 1433 Kudelstaart 20524
Showing the 12 most recent of 20 posts we hold for @helikopters. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Helikopters | 112Hub.nl” (@helikopters), 889 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/helikopters.
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.