Channel
@politiehelikopters
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
169subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001734279176 |
|---|---|
| Type | Channel |
| Username | @politiehelikopters |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/politiehelikopters |
Other / unclassifiable — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 12:41 | 169 | +2 |
| 31 Aug 2026, 14:45 | 167 | +1 |
| 23 Aug 2026, 16:48 | 166 | +1 |
| 16 Aug 2026, 13:55 | 165 | +1 |
| 8 Aug 2026, 16:31 | 164 | no change |
| 7 Aug 2026, 06:01 | 164 | first reading |
20 posts held, back to 7 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 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
08-08-2026 18:03 Politiehelikopter 03 geland Callsign: ZXP03 Registratie: PH-PXC Vluchtduur: 1u 55 min Teruggekeerd naar Amsterdam Airport Schiphol event=landed | avg=111.4mph | src=api | call=? | base=no | log=departed,landed | pts=1062 | r=62ff45c6
08-08-2026 16:08 Politiehelikopter 03 vertrokken Callsign: ZXP03 Registratie: PH-PXC Vertrokken vanaf Amsterdam Airport Schiphol event=departed | log=departed | pts=5 | r=62ff45c6
08-08-2026 13:56 Politiehelikopter 01 geland Callsign: ZXP01 Registratie: PH-PXA Vluchtduur: 1u 1 min Teruggekeerd naar Vliegbasis Volkel event=landed | avg=118.2mph | src=api | call=? | base=no | log=departed,landed | pts=697 | r=a66f3b53
08-08-2026 12:55 Politiehelikopter 01 vertrokken Callsign: ZXP01 Registratie: PH-PXA Vertrokken vanaf Overasselt event=departed | log=departed | pts=9 | r=a66f3b53
08-08-2026 11:37 Politiehelikopter 01 geland Callsign: ZXP01 Registratie: PH-PXA Vluchtduur: 2u 3 min Van Vliegbasis Volkel naar Overasselt event=landed | avg=107.4mph | src=api | call=? | base=no | log=departed,landed | pts=1417 | r=205e3170
08-08-2026 09:34 Politiehelikopter 01 vertrokken Callsign: ZXP01 Registratie: PH-PXA Vertrokken vanaf Vliegbasis Volkel event=departed | log=departed | pts=8 | r=205e3170
07-08-2026 22:09 Politiehelikopter 02 geland Callsign: ZXP02 Registratie: PH-PXB Vluchtduur: 1u 15 min Van Aalsmeer naar Amsterdam Airport Schiphol event=landed | avg=112.6mph | src=api | call=? | base=no | log=departed,circling,landed | pts=865 | r=f3fdb7d0
07-08-2026 20:54 Politiehelikopter 02 cirkeling Callsign: ZXP02 Registratie: PH-PXB Van Aalsmeer naar Hoevelaken event=circling | log=departed,circling | pts=511 | r=f3fdb7d0
07-08-2026 20:54 Politiehelikopter 02 vertrokken Callsign: ZXP02 Registratie: PH-PXB Vertrokken vanaf Aalsmeer event=departed | log=departed | pts=8 | r=f3fdb7d0
07-08-2026 17:13 Politiehelikopter 02 geland Callsign: ZXP02 Registratie: PH-PXB Vluchtduur: 50 min 23 sec Van Poederoijen naar Aalsmeer event=landed | avg=94.1mph | src=api | call=? | base=no | log=departed,landed | pts=583 | r=ce4524b0
07-08-2026 16:23 Politiehelikopter 02 vertrokken Callsign: ZXP02 Registratie: PH-PXB Vertrokken vanaf Poederoijen event=departed | log=departed | pts=9 | r=ce4524b0
07-08-2026 16:20 Politiehelikopter 02 geland Callsign: ZXP02 Registratie: PH-PXB Vluchtduur: 1u 4 min Van Amsterdam Airport Schiphol naar Alblasserdam Melding A1 AMBU 17146 Minister Donkerstraat 3119RE Schiedam SCHIDM bon 122447 event=landed | avg=92.5mph | src=api | call=? | base=no | log=departed,circling,landed | pts=744 | r=0c276f1a
Showing the 12 most recent of 20 posts we hold for @politiehelikopters. 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.
Named by 1 registered channel — 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.
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.
“Politiehelikopers | 112Hub.nl” (@politiehelikopters), 169 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/politiehelikopters.
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.