Telegram RegisterThe public register of Telegram
Telegram profile photo for Avia _Bilet ✈️

Channel

Avia _Bilet ✈️

@arzonturizmm

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

178subscribers

+12 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-1002279084527
TypeChannel
Username@arzonturizmm
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 October 2026
Measurements held4
Confirmed unchanged2 times, most recently 12 October 2026
On Telegramt.me/arzonturizmm

Topic

Travel — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Growth

1661781727 August 2026 — 166 subscribers8 August 2026 — 166 subscribers17 September 2026 — 175 subscribers2 October 2026 — 178 subscribers7 August 20262 October 2026
4 measurements spanning 56 days, net +12. 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 164–180 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 17:17178+3
17 Sept 2026, 20:15175+9
8 Aug 2026, 16:01166no change
7 Aug 2026, 18:45166first reading

Engagement

20 posts held, back to 5 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 1 page 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

18 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1266.7%
🔥316.7%
👏211.1%
👍15.56%

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 12 of the 20 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 5 July 2026 to 7 August 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

7 Aug 2026, 06:09 UTC554 views1 reactionsread 8 August 2026

🕋✨ CENTRUM HOLIDAYS bilan UMRA ZIYORATI ✨🕋 🤲 Muqaddas safarga biz bilan yo'l oling! 🛫 Reys sanalari 📅 11.08 📅 18.08 📅 25.08 🏨 Mehmonxonalar 🌿 Madina – Mirage Taiba Hotel 🕋 Makka – Diyar Al Orouba Hotel 🚶 Masjidul Haramgacha atigi 950 metr Standart paketga kiradi: ✈️ Aviachipta 🛂 Viza 🏨 Mehmonxonada joylashish 🍽️ Madinada 2 mahal ovqat 🍽️ Makkada 3 mahal ovqat 🚌 Transport xizmati 👳 Tajribali va ilmli elikboshi hamr…

❤1

1 Aug 2026, 17:40 UTC247 viewsread 8 August 2026

MED SKD C6-3038 MED-SKD 02AUG 07:10 - 15:20 +998900037339 @mukhammadali_1234

29 Jul 2026, 09:17 UTC314 viewsread 8 August 2026

TAS MED TAS. ONE WAY 30JUL F3-9235 TAS 12:10 MED 16:40 13AUG F3-9234 MED 02:10 TAS 10:30 📞+998900037339 @mukhammadali_1234

27 Jul 2026, 10:58 UTC357 viewsread 8 August 2026

🛩🛩🛩🛩🛩🛩🛩🛩🛩🛩 🔤🔤🔤 🔤🔤🔤 30.07.2026 HY 5339 TOSHKENT - MEDINA 13:00 - 17:00 ✈️✈️✈️✈️✈️✈️ 🔤🔤🔤 🔤🔤🔤 01.08.2026 HY 337 TASHKENT— JIDDA 08:10 13:00 📞+998900037339 🌐@mukhammadali_1234

23 Jul 2026, 11:57 UTC472 viewsread 8 August 2026

🔤🔤🔤🔤🔤🔤🔤 ✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️ 30-07-2026 MED 06:00 TAS 13:30 📞+998900037339 🌐@mukhammadali_1234

19 Jul 2026, 20:48 UTC672 viewsread 8 August 2026

✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️ 🔤🔤🔤🔤🔤 21JUL C6321 TAS2310 JED 0400 +1 05AUG C6322 JED 22:50 TAS 07:30 🔥🔥🔥🔥🔥🔥🔥🔥🔥 🔤🔤🔤🔤🔤🔤 📞+998900037339 🌐@mukhammadali_1234

18 Jul 2026, 11:31 UTC348 viewsread 8 August 2026

🔤🔤🔤🔤🔤🔤🔤 ✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️ 22JUL C6322 JED 22:50 TAS 07:30 📞+998900037339 🌐@mukhammadali_1234

17 Jul 2026, 17:23 UTC310 viewsread 8 August 2026

🔤🔤🔤🔤🔤🔤 ✈️✈️✈️✈️✈️✈️✈️✈️ ✈️18 JUL TAS 15:00 MED 19:30 1️⃣4️⃣0️⃣💲 📞+998900037339 🌐@mukhammadali_1234

16 Jul 2026, 09:47 UTC427 viewsread 8 August 2026

🇺🇿🇺🇿🇺🇿🇺🇿🇺🇿🇺🇿🇺🇿🇺🇿 ✈️✈️✈️✈️✈️✈️ 23.07 HY5340 MED18:55-TAS 02:35 🇺🇿🇺🇿🇺🇿🇺🇿🇺🇿🇺🇿🇺🇿🇺🇿 25.07 HY338 JED14:30-TAS23:00 📞+998900037339 🌐@mukhammadali_1234

15 Jul 2026, 06:32 UTC659 views1 reactionsread 8 August 2026

🔤🔤🔤🔤🔤🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤3️⃣💲5️⃣ 17 JUL TAS 7:00 MED 11:206️⃣🔤🔤 🔤🔤🔤0️⃣🔤👆👆👆 18 JUL TAS 15:00 MED 19:30 30 JUL MED 5:00 TAS 13:30 20 JUL TAS 15:00 MED 19:30 03 AVG MED 5:00 TAS 13:30 📞+998900037339 🌐@mukhammadali_1234

❤1

13 Jul 2026, 09:00 UTC176 views1 reactionsread 8 August 2026

✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️ 🔤🔤🔤🔤🔤🔤🔤🔤🔤 14.07.2026 F39233 🔤🔤🔤🔤🔤🔤 ✈️ 03:15 - 07:45 Qaytish: 28.07.2026 F39232 ✈️17:00 – 01:20. ✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️ 📞+998900037339 🌐@mukhammadali_1234

❤1

10 Jul 2026, 09:36 UTC776 views1 reactionsread 8 August 2026

✈️✈️✈️✈️✈️✈️✈️✈️✈️✈️ 🔤🔤🔤🔤🔤🔤🔤🔤🔤 14JUL C6321 TAS2310 JED 0400 +1 29JUL C6322 JED 22:50 TAS 07:30 17JUL C6-3019 TAS 04:30 JED 09:20 01AUG C6-3020 JED 04:10 TAS 12:50 20JUL C6-3019 TAS 06:20 JED 11:10 04AUG C6-3020 JED 06:00 TAS 14:40 24JUL C6-3019 TAS 04:30 JED 09:20 08AUG C6-3020 JED 04:10 TAS 12:50 27JUL C6-3019 TAS 06:20 JED 11:10 11AUG C6-3020 JED 06:00 TAS 14:40 31JUL C6-3019 TAS 04:30 JED 09:20 15AUG C6-302…

❤1

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

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

“Avia _Bilet ✈️” (@arzonturizmm), 178 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/arzonturizmm.

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.