4 Aug 2025, 14:11 UTCviews —
AviaMonitor pinned «Ми тепер працюємо тут - https://t.me/AviaEfir»
Channel
AviaMonitor
@AviaMonitor1
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Declared links · Cite this entry
84subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002012749781 |
|---|---|
| Type | Channel |
| Username | @AviaMonitor1 |
| Description | Канал авіація — https://t.me/aviaOM Канал моніторинг — https://t.me/AviaMonitor2 Підтримати канали — https://www.privat24.ua/send/17wdh. |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/AviaMonitor1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 17:31 | 84 | no change |
| 8 Aug 2026, 03:16 | 84 | first reading |
Engagement
20 posts held, back to 5 July 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 4 August 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈606
- Videos
- ≈38
- Links
- ≈5,860
Lifetime counters from Telegram’s own channel header, read 9 August 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
4 Aug 2025, 14:11 UTC194 viewsread 9 August 2026
Ми тепер працюємо тут - https://t.me/AviaEfir
4 Aug 2025, 06:38 UTC198 viewsread 9 August 2026
Відбій по МіГ-31К;
4 Aug 2025, 05:56 UTC202 viewsread 9 August 2026
🚨 ТРИВОГА 🚨 У повітрі ⚠️ МіГ-31К
2 Aug 2025, 15:45 UTC201 viewsread 9 August 2026
Відбій по МіГ-31К;
2 Aug 2025, 15:19 UTC177 viewsread 9 August 2026
🚨 ТРИВОГА 🚨 У повітрі ⚠️ МіГ-31К
30 Jul 2025, 13:19 UTC151 viewsread 9 August 2026
Відбій по МіГ-31К;
30 Jul 2025, 12:56 UTC125 viewsread 9 August 2026
🚨 ТРИВОГА 🚨 У повітрі ⚠️ МіГ-31К
28 Jul 2025, 05:49 UTC123 viewsread 9 August 2026
🚨 ТРИВОГА 🚨 У повітрі ⚠️ МіГ-31К
28 Jul 2025, 04:53 UTC114 viewsread 9 August 2026
🚨 ТРИВОГА 🚨 У повітрі ⚠️ МіГ-31К
27 Jul 2025, 20:14 UTC105 viewsread 9 August 2026
✈️ Зліт бортів Ту-95мс з аеродрому "Оленья" Мурманської області, рф. Кількість та курс уточнюємо.
25 Jul 2025, 11:04 UTC99 viewsread 9 August 2026
Відбій по МіГ-31К;
Showing the 12 most recent of 20 posts we hold for @AviaMonitor1. 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 — 1,215,996 of 1,548,671entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
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.
Declared links
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association— we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
privat24.ua
https://www.privat24.ua/send/17wdh.
https://www.privat24.ua/send/17wdh.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“AviaMonitor” (@AviaMonitor1), 84 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/AviaMonitor1.
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.