Telegram RegisterThe public register of Telegram
Telegram profile photo for 🛫 БИЛЕТЫ ИЗ РОССИИ

Channel

🛫 БИЛЕТЫ ИЗ РОССИИ

@tickets_from_russia

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

363subscribers

-5 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-1001581257701
TypeChannel
Username@tickets_from_russia
CreatedBetween 1 August 2021 and 20 October 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 15 September 2026
On Telegramt.me/tickets_from_russia

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 22 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

363368365.57 August 2026 — 368 subscribers8 August 2026 — 368 subscribers16 August 2026 — 366 subscribers23 August 2026 — 364 subscribers8 September 2026 — 363 subscribers7 August 20268 September 2026
5 measurements spanning 32 days, net -5. 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 362–369 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 00:37363-1
23 Aug 2026, 07:08364-2
16 Aug 2026, 07:13366-2
8 Aug 2026, 07:14368no change
7 Aug 2026, 07:48368first reading

Engagement

20 posts held, back to 20 October 2022the 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 24 October 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Oct 2022, 09:47 UTC≈1,700 viewsread 7 August 2026

#меньше20к #меньше6ч #прямой Откуда: #Сочи (#AER) Куда: #Ереван (#EVN) Дата отправления: 2022/10/23 21:50 Время в пути: 1ч Купить за 15285

24 Oct 2022, 09:47 UTC≈1,690 viewsread 7 August 2026

#меньше20к #меньше6ч #прямой Откуда: #Сочи (#AER) Куда: #Ереван (#EVN) Дата отправления: 2022/10/25 20:30 Время в пути: 1ч Купить за 12490

24 Oct 2022, 09:47 UTC≈1,670 viewsread 7 August 2026

#меньше20к #меньше6ч #прямой Откуда: #Сочи (#AER) Куда: #Ереван (#EVN) Дата отправления: 2022/10/22 21:00 Время в пути: 1ч Купить за 15285

24 Oct 2022, 09:46 UTC≈1,570 viewsread 7 August 2026

#меньше20к #меньше6ч #прямой Откуда: #Сочи (#AER) Куда: #Ереван (#EVN) Дата отправления: 2022/10/23 04:00 Время в пути: 1ч Купить за 10375

24 Oct 2022, 09:46 UTC≈1,330 viewsread 7 August 2026

#меньше20к #меньше6ч #прямой Откуда: #Сочи (#AER) Куда: #Ереван (#EVN) Дата отправления: 2022/10/23 20:30 Время в пути: 1ч Купить за 15285

24 Oct 2022, 09:46 UTC≈1,180 viewsread 7 August 2026

#меньше20к #меньше6ч #прямой Откуда: #Сочи (#AER) Куда: #Ереван (#EVN) Дата отправления: 2022/10/21 22:10 Время в пути: 1ч Купить за 15766

20 Oct 2022, 06:22 UTC≈1,110 viewsread 7 August 2026

#меньше20к #меньше12ч Откуда: #Казань (#KZN) Куда: #Стамбул (#IST) Дата отправления: 2022/10/21 03:10 Время в пути: 8ч Пересадок: 1 Купить за 15310

20 Oct 2022, 06:22 UTC964 viewsread 7 August 2026

#меньше40к #меньше6ч #прямой Откуда: #Москва (#ZIA) Куда: #Алматы (#ALA) Дата отправления: 2022/10/22 08:25 Время в пути: 4ч Купить за 21170

20 Oct 2022, 06:21 UTC876 viewsread 7 August 2026

#меньше40к #меньше12ч Откуда: #Сочи (#AER) Куда: #Ташкент (#TAS) Дата отправления: 2022/10/20 14:15 Время в пути: 11ч Пересадок: 1 Купить за 33933

20 Oct 2022, 06:21 UTC769 viewsread 7 August 2026

#меньше20к #меньше6ч #прямой Откуда: #Москва (#SVO) Куда: #Анталья (#AYT) Дата отправления: 2022/10/20 14:55 Время в пути: 5ч Купить за 8824

20 Oct 2022, 06:20 UTC687 viewsread 7 August 2026

#меньше20к #меньше12ч Откуда: #СанктПетербург (#LED) Куда: #Ереван (#EVN) Дата отправления: 2022/10/20 14:45 Время в пути: 10ч Пересадок: 1 Купить за 13272

20 Oct 2022, 06:20 UTC614 viewsread 7 August 2026

#меньше40к #меньше6ч #прямой Откуда: #Москва (#SVO) Куда: #Стамбул (#IST) Дата отправления: 2022/10/20 14:05 Время в пути: 5ч Купить за 20797

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

“🛫 БИЛЕТЫ ИЗ РОССИИ” (@tickets_from_russia), 363 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/tickets_from_russia.

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.