Telegram RegisterThe public register of Telegram
Telegram profile photo for AVIAKASSA | ANOR AVIA✈️

Channel

AVIAKASSA | ANOR AVIA✈️

@Aviakassa_AnorAvia

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

84,620subscribers

-16,041 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002006585559
TypeChannel
Username@Aviakassa_AnorAvia
Description🏝 Bizning xizmatlar: ✈️ Aviachiptalar 🚂 Poezd chiptalari 🏝 Turizm & sayohat xizmatlari 🪪 Viza olish xizmatlari 🔎 Deport tekshirish va muddatini aniqlash 📞 Tel: 772505070 | 773002070 ✅ Tezkor va ishonchli xizmat!
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/Aviakassa_AnorAvia

Topic

Travel — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Aviakassa_AnorAvia/18821 · this entry4 Aug 2026, 02:01 UTC@AnorAvia_Aviakassa/15514 Aug 2026, 04:02 UTC1.002.0 hours
@AnorAvia_Aviakassa/15545 Aug 2026, 02:01 UTC@Aviakassa_AnorAvia/18823 · this entry5 Aug 2026, 02:01 UTC1.00under a minute
@AnorAvia_Aviakassa/15575 Aug 2026, 07:56 UTC@Aviakassa_AnorAvia/18825 · this entry5 Aug 2026, 07:56 UTC1.00under a minute
@AnorAvia_Aviakassa/15595 Aug 2026, 17:10 UTC@Aviakassa_AnorAvia/18826 · this entry5 Aug 2026, 17:10 UTC1.00under a minute
@AnorAvia_Aviakassa/15606 Aug 2026, 02:01 UTC@Aviakassa_AnorAvia/18827 · this entry6 Aug 2026, 02:01 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@AnorAvia_Aviakassa5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (50)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 3 August 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @Aviakassa_AnorAvia — which is this entry. That is a statement about our reading window, not a claim of authorship.

Views per post sit far below this size band

187 average views per post against 84,620 subscribers — an engagement rate of 0.221%. Across the 342 registered channels in the same cohort — 31,645–99,897 subscribers, posting mainly in Belarusian — the middle half sit between 5.85% and 26.5%, with a median of 13.4%.

What this was computed from
Window30 days (24 August 2026 23 September 2026)
Posts measured129 of 129 published in the window (129 exact, 0 rounded by Telegram)
Views totalled24,072
Mature posts only0.23% over 122 posts read at least 24h after publication
Subscribers84,620 measured 18 September 2026
Cohortb31623:bel · 342 channels · p10 2.73% · p25 5.85% · p50 13.4% · p75 26.5% · p90 43.5%
Position in cohort0.880th percentile · 1/59 the cohort median
Uncertainty±0.034% of the figure, from Telegram’s rounding
Post languageBelarusian · 88.9% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_source · err_low, last confirmed 23 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

80,139101,70190,9207 August 2026 — 100,661 subscribers7 August 2026 — 100,566 subscribers8 August 2026 — 99,629 subscribers9 August 2026 — 98,825 subscribers10 August 2026 — 98,007 subscribers11 August 2026 — 97,046 subscribers13 August 2026 — 96,698 subscribers14 August 2026 — 100,605 subscribers16 August 2026 — 101,701 subscribers17 August 2026 — 100,635 subscribers18 August 2026 — 99,789 subscribers19 August 2026 — 99,196 subscribers20 August 2026 — 98,760 subscribers21 August 2026 — 98,337 subscribers23 August 2026 — 97,501 subscribers24 August 2026 — 96,482 subscribers25 August 2026 — 95,739 subscribers26 August 2026 — 95,233 subscribers27 August 2026 — 94,667 subscribers28 August 2026 — 93,491 subscribers29 August 2026 — 92,354 subscribers30 August 2026 — 91,356 subscribers31 August 2026 — 90,886 subscribers1 September 2026 — 89,948 subscribers2 September 2026 — 89,047 subscribers4 September 2026 — 87,861 subscribers7 September 2026 — 85,687 subscribers10 September 2026 — 83,228 subscribers12 September 2026 — 81,857 subscribers14 September 2026 — 80,139 subscribers15 September 2026 — 87,031 subscribers18 September 2026 — 84,620 subscribers84,6207 August 202618 September 2026
32 measurements spanning 41 days, net -16,041. 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 76,905–104,935 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
18 Sept 2026, 02:4084,620-2,411
15 Sept 2026, 20:5987,031+6,892
14 Sept 2026, 06:5680,139-1,718
12 Sept 2026, 15:5681,857-1,371
10 Sept 2026, 12:0183,228-2,459
7 Sept 2026, 08:0085,687-2,174
4 Sept 2026, 14:0287,861-1,186
2 Sept 2026, 21:2689,047-901
1 Sept 2026, 22:4789,948-938
31 Aug 2026, 21:4590,886-470
30 Aug 2026, 20:2691,356-998
29 Aug 2026, 17:5692,354-1,137
28 Aug 2026, 17:5893,491-1,176
27 Aug 2026, 15:5794,667-566
26 Aug 2026, 18:4495,233-506
25 Aug 2026, 22:1295,739-743
24 Aug 2026, 21:5396,482-1,019
23 Aug 2026, 10:2897,501-836
21 Aug 2026, 18:1898,337-423
20 Aug 2026, 15:2398,760first reading

Engagement

188 posts held, back to 3 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 96 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.221%
avg views ÷ 84,620 subscribers
Avg views / post
187
129 posts measured
Reaction rate
0.916%
reactions ÷ views · ER floor
Posts in window
129
of 188 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. It is computed over the 20 of 129 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 September 2026
Posts held188 (3 August 202622 September 2026)
Views total24,072
Reactions total28
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Sept 2026, 23:23 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.

What this channel posts

Photos
8,760
Videos
760
Links
3,230

Lifetime counters from Telegram’s own channel header, read 22 September 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.

Video runtime
4m 33s
Average length
20s

Measured directly from 14 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

33 reactions across 21 posts, in 4 distinct kinds. The most used accounts for 51.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1751.5%
927.3%
👏412.1%
🥰39.09%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 25 of the 188 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 33 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 188 most recent posts we hold, published 3 August 2026 to 22 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

22 Sept 2026, 13:27 UTC36 views1 reactionsread 22 September 2026
Photo

🇺🇿SAMARQAND → IZMIR🇹🇷 ✈️ 24-26-SENTYABR SAMARQAND → IZMIR 🧳 BAGAJLI — 3 300 000 so‘m ✅ Bagaj: 20 kg + Qo‘l yuki: 7 kg ✈️ 28-SENTYABR SAMARQAND → IZMIR 🧳 BAGAJLI — 4 830 000 so‘m ✅ Bagaj: 20 kg + Qo‘l yuki: 7 kg ❌ Qo‘shimcha to‘lovlar yo‘q! 🎫 Biletni sotib olish uchun:👇 ✍️ @AnorAvia 📞 +998-77-250-50-70 Telegram / WhatsApp 🔎 Boshqa reyslar narxini bilish uchun ham bizga yozing👆

👍1

22 Sept 2026, 13:27 UTC28 viewsread 22 September 2026
Photo

🇺🇿TOSHKENT → ANTALIYA🇹🇷 ✈️ 24-27-28-30-SENTYABR TOSHKENT → ANTALIYA 🧳 BAGAJLI — 2 500 000 so‘m ✅ Bagaj: 20 kg + Qo‘l yuki: 8 kg ❌ Qo‘shimcha to‘lovlar yo‘q! 🎫 Biletni sotib olish uchun:👇 ✍️ @AnorAvia 📞 +998-77-250-50-70 Telegram / WhatsApp 🔎 Boshqa reyslar narxini bilish uchun ham bizga yozing👆

22 Sept 2026, 13:27 UTC22 viewsread 22 September 2026
Photo

🇺🇿TOSHKENT → ANQARA🇹🇷 ✈️ 24-25-SENTYABR TOSHKENT → ANQARA 🎒 BAGAJSIZ — 2 750 000 so‘m ✅ Qo‘l yuki: 4 kg 🧳 BAGAJLI — 3 330 000 so‘m ✅ Bagaj: 20 kg + Qo‘l yuki: 8 kg ✈️ 28-29-SENTYABR TOSHKENT → ANQARA 🎒 BAGAJSIZ — 2 530 000 so‘m ✅ Qo‘l yuki: 4 kg 🧳 BAGAJLI — 3 320 000 so‘m ✅ Bagaj: 20 kg + Qo‘l yuki: 8 kg ❌ Qo‘shimcha to‘lovlar yo‘q! 🎫 Biletni sotib olish uchun:👇 ✍️ @AnorAvia 📞 +998-77-250-50-70 Telegram / W

22 Sept 2026, 13:27 UTC23 viewsread 22 September 2026
Photo

✈️ O‘ZBEKISTONDAN ISTANBULGA ARZON AVIACHIPTALAR 🔥 Eng qulay narxlar: 📍 TOSHKENT → ISTANBUL 💰 2 900 000 so‘m 📍 SAMARQAND → ISTANBUL 💰 4 450 000 so‘m 📍 FARG‘ONA → ISTANBUL 💰 3 350 000 so‘m 📍 TERMIZ → ISTANBUL 💰 3 000 000 so‘m 📍 BUXORO → ISTANBUL 💰 3 560 000 so‘m 📍 URGANCH → ISTANBUL 💰 4 200 000 so‘m ❌ Qo‘shimcha to‘lovlar yo‘q! 🎫 Biletni sotib olish uchun:👇 ✍️ @AnorAvia 📞 +998-77-250-50-70 Telegram / WhatsAp

22 Sept 2026, 13:05 UTC38 viewsread 22 September 2026
Photo

✅ ISHONCHLI VA ARZON BILET QIDIRAYABSIZMI? BEMALOL BIZGA MUROJAAT QILISHINGIZ MUMKIN; ✅ BIZDA DUNYONING BARCHA SHAXARLARIGA BORISH VA QAYTISH UCHUN BILETLAR BOR; ✅ BILETLARNI NAQD PUL YOKI PUL O'TKAZISH YO'LLARI BILAN ONLINE SOTIB OLISHINGIZ MUMKIN; ✅ DOIMIY MIJOZLARGA, 3/4/5 KISHI VA OILAVIYLARGA CHEGIRMA BOR. 🕐 Bilet sotib olish uchun👇 ✍️ @AnorAvia 📞 +998-77-250-50-70 Telegram / WhatsApp 💳 To‘lovlar: Click|Pa

22 Sept 2026, 04:02 UTC65 viewsread 22 September 2026
Photo

❌@AVIA_KASSAM ❌ @mahmud_travel ❌@avia_kassa_olimjon 😡 Shu mashenniklardan bilet so'rayotganlar extiyot bo'linglar! Juda ko'pchilikni aldab pulini olib bilet tashlab bermayapti. Kanal gruppalariga ham bizni - ANOR AVIA xabar rasmlarimizni qōyib odamlarni ishontirayabdi. Bilet sotib olayotganda albatta video orqali telefon qilib kōrishib gaplashib keyin bilet sotib olinglar. ‼️ Arzon narxlarga ishonib xaromxo'r mashen

22 Sept 2026, 02:01 UTC82 viewsread 22 September 2026
Photo

✈️ Aviachiptalarni qachon arzon sotib olish mumkin? 📌 Aviachiptani arzonroq olish uchun aniq bir hafta kunini kutishdan ko‘ra, oldindan qidirish muhimroq. ✅ Yaqin va qisqa yo‘nalishlar: uchishdan taxminan 1–3 oy oldin. ✅ Xalqaro yo‘nalishlar: odatda 2–5 oy oldin. ✅ Yoz, Yangi yil, Ramazon hayiti va bayram kunlari: 3–6 oy oldin olish ma’qul. ✅ Uchishga 7–10 kun qolganida narxlar ko‘pincha qimmatlashadi, ayniqsa M

21 Sept 2026, 07:46 UTC140 views2 reactionsread 22 September 2026
Photo

✈️ O‘ZBEKISTONDAN SOCHIGA ARZON AVIACHIPTALAR ✈️ 22-25-29-SENTYABR TOSHKENT → SOCHI 🎒 BAGAJSIZ — 1 950 000 so‘m ✅ Qo‘l yuki: 8 kg 🧳 BAGAJLI — 2 200 000 so‘m ✅ Bagaj: 23 kg + Qo‘l yuki: 8 kg ✈️ 26-SENTYABR NAMANGAN → SOCHI 🎒 BAGAJSIZ — 2 550 000 so‘m ✅ Qo‘l yuki: 8 kg 🧳 BAGAJLI — 2 750 000 so‘m ✅ Bagaj: 23 kg + Qo‘l yuki: 8 kg ✈️ 22-24-29-SENTYABR SAMARQAND → SOCHI 🎒 BAGAJSIZ — 1 620 000 so‘m ✅ Qo‘l yuki: 5

👍2

21 Sept 2026, 07:23 UTC132 views2 reactionsread 22 September 2026
Photo

✈️ O‘ZBEKISTONDAN MOSKVAGA ARZON AVIACHIPTALAR 🔥 Eng qulay narxlar: 📍 TOSHKENT → MOSKVA 💰 1 060 000 so‘m 📍 SAMARQAND → MOSKVA 💰 890 000 so‘m 📍 ANDIJON → MOSKVA 💰 1 550 000 so‘m 📍 FARG‘ONA → MOSKVA 💰 1 150 000 so‘m 📍 NAMANGAN → MOSKVA 💰 1 490 000 so‘m 📍 BUXORO → MOSKVA 💰 1 700 000 so‘m ❌ Qo‘shimcha to‘lovlar yo‘q! 🎫 Biletni sotib olish uchun:👇 ✍️ @AnorAvia 📞 +998-77-250-50-70 Telegram / WhatsApp 🔎 Boshqa re

👍1🥰1

21 Sept 2026, 04:02 UTC126 views3 reactionsread 22 September 2026
Photo

❌@AVIA_KASSAM ❌ @mahmud_travel ❌@avia_kassa_olimjon 😡 Shu mashenniklardan bilet so'rayotganlar extiyot bo'linglar! Juda ko'pchilikni aldab pulini olib bilet tashlab bermayapti. Kanal gruppalariga ham bizni - ANOR AVIA xabar rasmlarimizni qōyib odamlarni ishontirayabdi. Bilet sotib olayotganda albatta video orqali telefon qilib kōrishib gaplashib keyin bilet sotib olinglar. ‼️ Arzon narxlarga ishonib xaromxo'r mashen

👍2👏1

21 Sept 2026, 04:01 UTC103 viewsread 22 September 2026
Photo

❗️ MUHIM OGOHLANTIRISH 🇷🇺Rossiyaga kirish uchun faqat zapret yo‘qligi yetarli bo‘lmasligi mumkin. Safardan oldin quyidagilarni ham tekshiring: ✅ Pasportning amal qilish muddati ✅ Aviachiptadagi ism-familiya ✅ Migratsiya qoidalari ✅ Qarzdorlik va jarimalar ✅ Patent yoki registratsiya holati ✅ Reyestrga kiritilgan-kiritilmagani Hujjatdagi bitta harf xatosi ham aeroportda muammo tug‘dirishi mumkin. Safarga puxta ta

21 Sept 2026, 02:01 UTC124 views5 reactionsread 22 September 2026
Photo

✈️ MOSKVAGA UCHMOQCHI BO‘LGANLARGA FOYDALI MASLAHATLAR! 🇷🇺 ✅ 1. Pasportingizni tekshiring Pasport muddati tugamagan, yirtilmagan va ma’lumotlari aniq ko‘rinadigan bo‘lishi kerak. ✅ 2. RuID orqali ariza yuboring. Xozircha ixtiyoriy! Rossiyaga vizasiz kiruvchilar safardan oldin ruID ilovasi orqali kirish arizasini to‘ldirishi kerak. Ariza odatda safardan 72 soat oldin, favqulodda holatda esa kamida 4 soat oldin yubori

👍5

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

Posts edited after publishing

@Aviakassa_AnorAvia edited 6 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
25 August 2026
Most recent edit
20 September 2026

Mentions

Named by 4 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.

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

“AVIAKASSA | ANOR AVIA✈️” (@Aviakassa_AnorAvia), 84,620 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Aviakassa_AnorAvia.

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.