Telegram RegisterThe public register of Telegram
Telegram profile photo for Анастасия Лешукова

Channel

Анастасия Лешукова

@rg_krsk

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

32subscribers

-788 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-1003887928815
TypeChannel
Username@elizarun
Created13 March 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/rg_krsk

Topic

Other / unclassifiable — 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 1 October 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.

Previous handles

@rg_krsk was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@rg_krsk
held 11 August 2026 – 11 August 2026

Growth

14821417.57 August 2026 — 820 subscribers7 August 2026 — 820 subscribers8 August 2026 — 821 subscribers11 August 2026 — 821 subscribers12 August 2026 — 819 subscribers17 September 2026 — 14 subscribers1 October 2026 — 21 subscribers12 October 2026 — 32 subscribers327 August 202612 October 2026
8 measurements spanning 66 days, net -788. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 11:0432+11
1 Oct 2026, 11:5621+7
17 Sept 2026, 11:3914-805
12 Aug 2026, 00:23819-2
11 Aug 2026, 20:00821no change
8 Aug 2026, 02:14821+1
7 Aug 2026, 07:46820no change
7 Aug 2026, 07:38820first reading

Engagement

5 posts held, back to 13 March 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 2 pages 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 5 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

26 Jul 2026, 11:21 UTC384 viewsread 11 August 2026

Основной канал тут https://t.me/+2i-AD5LPy3kwYzky

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

“Анастасия Лешукова” (@rg_krsk), 32 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/rg_krsk.

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.