Telegram RegisterThe public register of Telegram
Telegram profile photo for Внутри туризма #сновавтеме

Channel

Внутри туризма #сновавтеме

@tourismSakhKuril

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

126subscribers

-8 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001318734531
TypeChannel
Username@tourismSakhKuril
Created13 January 2020 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live12 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/tourismSakhKuril

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

1261361316 August 2026 — 134 subscribers7 August 2026 — 136 subscribers8 August 2026 — 136 subscribers15 August 2026 — 135 subscribers24 August 2026 — 133 subscribers10 September 2026 — 132 subscribers18 September 2026 — 131 subscribers4 October 2026 — 129 subscribers13 October 2026 — 131 subscribers20 October 2026 — 128 subscribers4 November 2026 — 127 subscribers12 November 2026 — 126 subscribers6 August 202612 November 2026
12 measurements spanning 98 days, net -8. 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 125–138 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 23:06126-1
4 Nov 2026, 04:48127-1
20 Oct 2026, 12:15128-3
13 Oct 2026, 19:27131+2
4 Oct 2026, 09:20129-2
18 Sept 2026, 20:56131-1
10 Sept 2026, 08:20132-1
24 Aug 2026, 05:08133-2
15 Aug 2026, 14:15135-1
8 Aug 2026, 23:32136no change
7 Aug 2026, 04:56136+2
6 Aug 2026, 19:56134first reading

Engagement

1 post held, back to 13 January 2020 — 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 1 post for this entry, the most recent from 13 January 2020. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 1 most recent of 1 post we hold for @tourismSakhKuril. 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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“Внутри туризма #сновавтеме” (@tourismSakhKuril), 126 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/tourismSakhKuril.

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.