Telegram RegisterThe public register of Telegram
Telegram profile photo for P2000 Hollands-Midden

Channel

P2000 Hollands-Midden

@P2000R16

On this record: Growth · Engagement · Posts · Citations · Cite this entry

65subscribers

+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-1001518286072
TypeChannel
Username@P2000R16
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live3 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/P2000R16

Growth

646564.57 August 2026 — 65 subscribers10 August 2026 — 65 subscribers28 August 2026 — 64 subscribers3 September 2026 — 65 subscribers7 August 20263 September 2026
4 measurements spanning 27 days. 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 64–65 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 11:4065+1
28 Aug 2026, 02:4364-1
10 Aug 2026, 02:3265no change
7 Aug 2026, 15:1165first reading

Engagement

20 posts held, back to 9 August 2026the 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.

ERR · 30 days
10.5%
avg views ÷ 65 subscribers
Avg views / post
6.8
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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 9 August 2026
Posts held20 (9 August 20269 August 2026)
Views total136
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 02:32 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.

Recent posts

9 Aug 2026, 22:24 UTC1 viewsread 10 August 2026

Prio 2 A4 Re - Kp Ypenburg 47,8 x \'s-Gravenhage (SGRAVH) Bijzondere verkeerszaken 10-08-2026 00:24:18 / Politie Hollands-Midden / Verkeermanagementcentrale Rijkswaterstaat

9 Aug 2026, 22:05 UTC2 viewsread 10 August 2026

Prio 2 Shell Express van Berckelweg Noordwijk ZH (NDWKZH) Ongeval wegvervoer letsel 10-08-2026 00:05:57 / Politie Hollands-Midden / Persinformatie

9 Aug 2026, 21:40 UTC2 viewsread 10 August 2026

Prio 1 N206 Re - Ir. G. Tjalmaweg 16,6 Valkenburg ZH (VALKZH) Ongeval wegvervoer letsel 09-08-2026 23:40:22 / Politie Hollands-Midden / Persinformatie

9 Aug 2026, 20:51 UTC5 viewsread 10 August 2026

Prio 4 A4 Re 28,9 Leiderdorp (LEIDDP) Wegverkeer verkeersstremming (soort stremming: pechgeval) 09-08-2026 22:51:18 / Politie Hollands-Midden / Verkeermanagementcentrale Rijkswaterstaat

9 Aug 2026, 20:02 UTC7 viewsread 10 August 2026

P 2 BDH-02 Stank/hind. lucht (binnen) Nieuwstraat Boskoop 162234 09-08-2026 22:02:46 / Brandweer Hollands-Midden / Bemanning TS ploeg 1 (Boskoop) 16-2234 - Boskoop - Tankautospuit (TS)

9 Aug 2026, 20:00 UTC7 viewsread 10 August 2026

Prio 4 A12 Re 26,0 Waddinxveen (WADDXV) Wegverkeer verkeersstremming (soort stremming: pechgeval) 09-08-2026 22:00:11 / Politie Hollands-Midden / Verkeermanagementcentrale Rijkswaterstaat

9 Aug 2026, 19:23 UTC6 viewsread 10 August 2026

P 2 BDH-02 Brandgerucht Essendreef Gouderak 163631 09-08-2026 21:23:18 / Brandweer Hollands-Midden / Korpsalarm (Gouderak) 16-3631 - Gouderak - Tankautospuit (TS)

9 Aug 2026, 18:16 UTC7 viewsread 10 August 2026

P 1 BDH-03 Stank/hind. lucht (gaslucht) (binnen) Gladiolenstraat Lisse 169191 161130 09-08-2026 20:16:18 / Brandweer Hollands-Midden 16-1130 - Lisse - Tankautospuit (TS) 16-9191 - Regionaal - Dienstauto Officier van Dienst (DA-OVD)

9 Aug 2026, 17:54 UTC7 viewsread 10 August 2026

Prio 2 43.9 A20 Re Nieuwerkerk aan den IJssel (NWKKIJ) : 09-08-2026 19:54:03 / Politie Hollands-Midden / Verkeermanagementcentrale Rijkswaterstaat

9 Aug 2026, 17:45 UTC7 viewsread 10 August 2026

Prio 1 Concertweg Eisenhowerlaan Alphen aan den Rijn (ALPHRN) Ongeval wegvervoer letsel (meervoudig) 09-08-2026 19:45:50 / Politie Hollands-Midden / Persinformatie

9 Aug 2026, 17:41 UTC8 viewsread 10 August 2026

P 2 BDH-01 BR buiten Bronforel Leiden 164130 09-08-2026 19:41:42 / Brandweer Hollands-Midden 16-4130 - Leiden-Noord - Tankautospuit (TS)

9 Aug 2026, 17:02 UTC9 viewsread 10 August 2026

P 2 BDH-03 Dier te water N207 Re - Boskoopseweg 32,2 Alphen aan den Rijn 162233 09-08-2026 19:02:12 / Brandweer Hollands-Midden 16-2233 - Alphen aan den Rijn - Tankautospuit (TS)

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

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.

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

“P2000 Hollands-Midden” (@P2000R16), 65 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/P2000R16.

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.