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

Channel

P2000 Gelderland-Midden

@P2kGelderlandMidden

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

75subscribers

-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-1001532654330
TypeChannel
Username@P2kGelderlandMidden
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live7 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 7 September 2026
On Telegramt.me/P2kGelderlandMidden

Growth

747775.57 August 2026 — 77 subscribers9 August 2026 — 77 subscribers15 August 2026 — 76 subscribers22 August 2026 — 74 subscribers30 August 2026 — 75 subscribers757 August 202630 August 2026
5 measurements spanning 23 days, net -2. 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 74–77 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 15:4875+1
22 Aug 2026, 23:0774-2
15 Aug 2026, 19:0576-1
9 Aug 2026, 20:1777no change
7 Aug 2026, 15:2177first 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
17.0%
avg views ÷ 75 subscribers
Avg views / post
12.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 total255
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 20:17 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, 20:05 UTC2 viewsread 9 August 2026

P 2 BON-04 BR berm/bosschage Erasmusstate Ede 079035 09-08-2026 22:05:29 / Brandweer Gelderland-Midden 07-9035 - Regionaal - Tankautospuit (TS)

9 Aug 2026, 18:25 UTC7 viewsread 9 August 2026

P 3 BON-04 Wateroverlast Jansplaats Arnhem 073631 09-08-2026 20:25:35 / Brandweer Gelderland-Midden 07-3631 - Arnhem-Noord - Tankautospuit (TS)

9 Aug 2026, 18:23 UTC8 viewsread 9 August 2026

P 2 BON-02 Buitensluiting St. Gangulphusplein Arnhem 073751 09-08-2026 20:23:43 / Brandweer Gelderland-Midden 07-3751 - Arnhem-Zuid - Hoogwerker (HW)

9 Aug 2026, 18:16 UTC10 viewsread 9 August 2026

P 2 BON-02 Buitensluiting (deur openen) St. Gangulphusplein Arnhem 073731 09-08-2026 20:16:33 / Brandweer Gelderland-Midden 07-3731 - Arnhem-Zuid - Tankautospuit (TS)

9 Aug 2026, 17:48 UTC10 viewsread 9 August 2026

P 3 BON-01 Dienstverlening Eldenseweg Arnhem 073631 09-08-2026 19:48:37 / Brandweer Gelderland-Midden 07-3631 - Arnhem-Noord - Tankautospuit (TS)

9 Aug 2026, 17:23 UTC12 viewsread 9 August 2026

P 2 BON-02 Stormschade Peutweg Barneveld 071741 09-08-2026 19:23:07 / Brandweer Gelderland-Midden 07-1741 - Barneveld (Beekstraat) - Tankautospuit Natuurbrandbestrijding (TST-NB)

9 Aug 2026, 16:00 UTC13 viewsread 9 August 2026

P 2 BON-05 Stormschade Oude Oosterbeekseweg Doorwerth 073451 09-08-2026 17:59:59 / Brandweer Gelderland-Midden / Bemanning HW (Doorwerth) 07-3451 - Doorwerth - Hoogwerker (HW)

9 Aug 2026, 15:49 UTC14 viewsread 9 August 2026

P 2 BON-05 Stormschade Oude Oosterbeekseweg Doorwerth 073441 09-08-2026 17:49:39 / Brandweer Gelderland-Midden / Bemanning TS (Doorwerth) 07-3441 - Doorwerth - Tankautospuit Natuurbrandbestrijding (TST-NB)

9 Aug 2026, 15:46 UTC12 viewsread 9 August 2026

P 2 BON-02 BR berm/bosschage Ruitenberglaan Arnhem 073631 09-08-2026 17:46:24 / Brandweer Gelderland-Midden 07-3631 - Arnhem-Noord - Tankautospuit (TS)

9 Aug 2026, 14:32 UTC12 viewsread 9 August 2026

P 3 BON-02 Contact MKB (OVD-B) Arnhemseweg Zevenaar 075097 09-08-2026 16:31:59 / Brandweer Gelderland-Midden / Alarmcode (OvD Oost) 07-5097 - Regionaal - Dienstauto Officier van Dienst Oost (DA-OVD)

9 Aug 2026, 13:41 UTC14 viewsread 9 August 2026

Aanrijding letsel Camping Het Lorkenbos Zuid Mosselsepad Otterlo 604699 09-08-2026 15:41:28 / Politie Gelderland-Midden / Persinformatie

9 Aug 2026, 12:52 UTC16 viewsread 9 August 2026

P 2 Herbezet./kazerneren (herbezetting) Kazerne Arnhem Zuid Groningensingel Arnhem 09-08-2026 14:52:50 / Brandweer Gelderland-Midden

Showing the 12 most recent of 20 posts we hold for @P2kGelderlandMidden. 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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“P2000 Gelderland-Midden” (@P2kGelderlandMidden), 75 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/P2kGelderlandMidden.

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.