Telegram RegisterThe public register of Telegram
Telegram profile photo for Яндекс PRO Путешествия | Чат

Supergroup

Яндекс PRO Путешествия | Чат

@yandex_travel_pro_chat

Has discussion group

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

1,080members

+0 since we began measuring on 6 August 2026

168 online right now

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001909500468
TypeSupergroup
Username@yandex_travel_pro_chat
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 October 2026
Last confirmed live5 November 2026
Measurements held23
Confirmed unchanged2 times, most recently 5 November 2026
On Telegramt.me/yandex_travel_pro_chat

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 7 October 2026 and assigned it the closest of 31 fixed categories, at 89% 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

1,0571,0971,0776 August 2026 — 1,080 members10 August 2026 — 1,087 members12 August 2026 — 1,089 members16 August 2026 — 1,093 members19 August 2026 — 1,097 members23 August 2026 — 1,095 members26 August 2026 — 1,097 members29 August 2026 — 1,095 members1 September 2026 — 1,090 members5 September 2026 — 1,092 members10 September 2026 — 1,080 members18 September 2026 — 1,069 members27 September 2026 — 1,057 members5 October 2026 — 1,069 members7 October 2026 — 1,069 members11 October 2026 — 1,062 members15 October 2026 — 1,067 members18 October 2026 — 1,073 members21 October 2026 — 1,071 members24 October 2026 — 1,074 members27 October 2026 — 1,076 members30 October 2026 — 1,082 members2 November 2026 — 1,080 members1,0806 August 20262 November 2026
23 measurements spanning 88 days. 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 1,051–1,103 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
2 Nov 2026, 12:551,080-2
30 Oct 2026, 19:291,082+6
27 Oct 2026, 13:271,076+2
24 Oct 2026, 05:311,074+3
21 Oct 2026, 09:411,071-2
18 Oct 2026, 02:561,073+6
15 Oct 2026, 01:191,067+5
11 Oct 2026, 16:411,062-7
7 Oct 2026, 18:111,069no change
5 Oct 2026, 13:351,069+12
27 Sept 2026, 06:561,057-12
18 Sept 2026, 06:151,069-11
10 Sept 2026, 09:591,080-12
5 Sept 2026, 15:001,092+2
1 Sept 2026, 07:581,090-5
29 Aug 2026, 15:371,095-2
26 Aug 2026, 05:581,097+2
23 Aug 2026, 04:361,095-2
19 Aug 2026, 15:481,097+4
16 Aug 2026, 09:031,093first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“Яндекс PRO Путешествия | Чат” (@yandex_travel_pro_chat), 1,080 members as measured 2 November 2026. Telegram Register, tgregister.com/channel/yandex_travel_pro_chat.

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.