Telegram RegisterThe public register of Telegram
Telegram profile photo for Pit the skywatcher✈️

Channel

Pit the skywatcher✈️

@pit_skywatcher

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

14,643subscribers

-505 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001366661270
TypeChannel
Username@pit_skywatcher
Descriptionwir schauen mal, was am Himmel so los ist. Kommentare zu den Flügen: https://comments.bot/thread/pe-s-wFd_ Mediathek: https://t.me/pit_mediathek/2 Meldestelle / Kontakt: @PitSkywatcher [email protected]
Created8 December 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/pit_skywatcher

Topic

Science — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 the other topics.

Growth

14,64315,14814,895.56 August 202611 November 2026
65 measurements spanning 97 days, net -505. 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 14,567–15,224 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
11 Nov 2026, 16:1714,643-16
9 Nov 2026, 23:2014,659-6
8 Nov 2026, 15:1614,665-7
7 Nov 2026, 10:0814,672-5
6 Nov 2026, 12:2614,677-3
5 Nov 2026, 11:1614,680-8
4 Nov 2026, 11:0514,688-10
3 Nov 2026, 11:4014,698-1
2 Nov 2026, 14:0014,699-4
1 Nov 2026, 16:2514,703-5
31 Oct 2026, 14:0914,708-6
30 Oct 2026, 15:3014,714-4
29 Oct 2026, 15:0114,718-5
28 Oct 2026, 11:2714,723-4
27 Oct 2026, 08:1614,727-6
26 Oct 2026, 05:3014,733-7
25 Oct 2026, 02:0114,740-2
23 Oct 2026, 23:5614,742-6
23 Oct 2026, 03:2714,748-5
22 Oct 2026, 06:5614,753first reading

Engagement

18 posts held, back to 11 July 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 72 pages 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 18 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
≈11,800
Videos
≈158
Links
≈7,770

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

9 Aug 2026, 16:41 UTC≈3,110 viewsread 27 August 2026
Forwarded from @pit_mediathekPhoto

Durch die Abschaltung des Teilchenbeschleuniger LHC (Large Hadron Collider) des CERN am 29.06.2026 bin ich darauf aufmerksam geworden. Es gibt den sogenannten Mandela-Effekt, bei dem sich das VW-Logo in der Erinnerung vieler Menschen angeblich verändert hat. In dieser Welt sind das V und das W voneinander getrennt. Viele erinnern sich jedoch daran, dass das früher nicht so war. Interessant ist, dass im Film „Zurück …

14 Jul 2026, 18:47 UTC≈9,360 viewsread 12 November 2026
Photo

Das #DLR heute über der #Eifel. 🤔 https://globe.adsbexchange.com/?icao=3d526b,3d7cc7&lat=50.810&lon=6.216&zoom=10.5&showTrace=2026-07-14

14 Jul 2026, 18:44 UTC≈8,450 viewsread 12 November 2026
Photo

#GFD führte heute einen Parallelflug am #Truppenübungsplatz #Munster durch. https://globe.adsbexchange.com/?icao=3cd069&lat=53.921&lon=12.236&zoom=7.0&showTrace=2026-07-14

14 Jul 2026, 18:42 UTC≈16,700 viewsread 12 November 2026
Photo

Hier die heutigen Parallelflüge rund um #Rügen. https://globe.adsbexchange.com/?icao=3e29df,3d089a&lat=54.441&lon=13.181&zoom=9.3&showTrace=2026-07-14

12 Jul 2026, 17:55 UTC≈5,880 viewsread 12 November 2026
Photo

#Österreich: Parallelflug heute bei #Innsbruck. https://globe.adsbexchange.com/?icao=49d666&lat=47.981&lon=11.352&zoom=7.7&showTrace=2026-07-12

12 Jul 2026, 17:53 UTC≈4,290 viewsread 12 November 2026
Photo

Parallelflug rund um den #Truppenübungsplatz #Grafenwöhr. 🤔 https://globe.adsbexchange.com/?icao=3e46e5&lat=48.184&lon=14.064&zoom=8.0&showTrace=2026-07-12

12 Jul 2026, 17:50 UTC≈4,140 viewsread 12 November 2026
Photo

Parallelflug heute bei #Aschaffenburg. https://globe.adsbexchange.com/?icao=3e29df&lat=50.098&lon=9.252&zoom=9.5&showTrace=2026-07-12

12 Jul 2026, 17:48 UTC≈3,360 viewsread 12 November 2026
Photo

Erneuter Parallelflug heute über #Saarbrücken. https://globe.adsbexchange.com/?icao=4b10f7&lat=49.377&lon=6.874&zoom=8.6&showTrace=2026-07-12

12 Jul 2026, 17:47 UTC≈2,750 viewsread 12 November 2026
Photo

Parallelflug heute zwischen #Köln und #Düsseldorf. https://globe.adsbexchange.com/?icao=45da01&lat=51.255&lon=5.601&zoom=7.0&showTrace=2026-07-12

12 Jul 2026, 17:46 UTC≈2,820 viewsread 12 November 2026
Photo

Hier die heutigen Parallelflüge über #Belgien und den #Niederlanden. https://globe.adsbexchange.com/?icao=39c90d,39bc88,485844,45e5b3,4a9d2e,459dd3,adab29,485844&lat=51.533&lon=5.508&zoom=7.3&showTrace=2026-07-12

12 Jul 2026, 17:42 UTC≈3,780 viewsread 12 November 2026
Photo

Hier die heutigen Parallelflüge über der #Ostsee, rund um #Hamburg und zwischen #Osnabrück und #Braunschweig / #Salzgitter. https://globe.adsbexchange.com/?icao=45e613,3d089a,3d4dcd,4b10f6&lat=53.295&lon=10.175&zoom=7.0&showTrace=2026-07-12

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 3 registered channels — 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Alles was du zum Leben brauchst
@AlleswasduzumLebenbrauchst · 29,210
Telegram ranks this channel #48 of 67 here — alongside 66 others — read 8 September 2026
Kai Brenner - Per Du mit dem Leben😃
@kaibrenner · 42,004
Telegram ranks this channel #54 of 72 here — alongside 71 others — read 29 August 2026
Lichtweiser
@lichtweiser · 46,623
Telegram ranks this channel #65 of 69 here — alongside 68 others — read 27 August 2026
⚛️🦁 Gesund im Ganzen
@Loewentatze · 33,511
Telegram ranks this channel #67 of 68 here — alongside 67 others — read 4 September 2026
fuf media - Freiheit denken
@fufmedia · 54,560
Telegram ranks this channel #67 of 71 here — alongside 70 others — read 23 August 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Pit the skywatcher✈️” (@pit_skywatcher), 14,643 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/pit_skywatcher.

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.