27 Feb 2025, 19:52 UTC414 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:52:50 PM Channel: @NYPD_Highway Credit @TheScannerLine
Channel
TSL - NYPD Highway
@NYPD_Highway
On this record: Growth · Engagement · Posts · Citations · Cite this entry
178subscribers
-2 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 | -1001889621471 |
|---|---|
| Type | Channel |
| Username | @NYPD_Highway |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 22 August 2026 |
| On Telegram | t.me/NYPD_Highway |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:36 | 178 | -2 |
| 8 Aug 2026, 13:01 | 180 | no change |
| 7 Aug 2026, 09:32 | 180 | first reading |
Engagement
20 posts held, back to 27 February 2025 — 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 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 27 February 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
27 Feb 2025, 19:52 UTC414 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:52:24 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:51 UTC413 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:51:48 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:51 UTC404 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:51:03 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:50 UTC356 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:50:30 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:50 UTC224 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:50:18 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:49 UTC196 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:49:29 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:49 UTC173 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:49:03 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:48 UTC145 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:48:52 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:47 UTC131 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:47:46 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:47 UTC109 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:47:28 PM Channel: @NYPD_Highway Credit @TheScannerLine
27 Feb 2025, 19:47 UTC100 viewsread 8 August 2026
Voice message
401--NYPD Highway 02/27/2025 02:47:22 PM Channel: @NYPD_Highway Credit @TheScannerLine
Showing the 12 most recent of 20 posts we hold for @NYPD_Highway. 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.
Citation-graph rank
Citation-graph rank — 214,077 of 1,602,887entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“TSL - NYPD Highway” (@NYPD_Highway), 178 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/NYPD_Highway.
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.