
Channel
Алёна Кривко
@YBIPYrPWqY4zN2Qy
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,658subscribers
+28 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001525415307 |
|---|---|
| Type | Channel |
| Username | @YBIPYrPWqY4zN2Qy |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/YBIPYrPWqY4zN2Qy |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 15:36 | 3,658 | -8 |
| 10 Nov 2026, 20:28 | 3,666 | -9 |
| 7 Nov 2026, 11:40 | 3,675 | -6 |
| 4 Nov 2026, 17:30 | 3,681 | +2 |
| 1 Nov 2026, 21:37 | 3,679 | -6 |
| 29 Oct 2026, 20:11 | 3,685 | -4 |
| 26 Oct 2026, 23:00 | 3,689 | -1 |
| 24 Oct 2026, 08:54 | 3,690 | +1 |
| 21 Oct 2026, 01:21 | 3,689 | -3 |
| 18 Oct 2026, 03:15 | 3,692 | -1 |
| 14 Oct 2026, 21:04 | 3,693 | -7 |
| 11 Oct 2026, 04:35 | 3,700 | -9 |
| 4 Oct 2026, 21:57 | 3,709 | +108 |
| 25 Sept 2026, 21:20 | 3,601 | -4 |
| 17 Sept 2026, 13:19 | 3,605 | -9 |
| 13 Sept 2026, 13:38 | 3,614 | -7 |
| 9 Sept 2026, 23:00 | 3,621 | +2 |
| 7 Sept 2026, 13:49 | 3,619 | no change |
| 4 Sept 2026, 15:38 | 3,619 | -9 |
| 1 Sept 2026, 10:23 | 3,628 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@lenel_ya · 40,425
Telegram ranks this channel #20 of 76 here — alongside 75 others — read 29 August 2026
@marisha_deboshir · 39,802
Telegram ranks this channel #68 of 82 here — alongside 81 others — read 30 August 2026
@zhivotovvladimir · 105,103
Telegram ranks this channel #68 of 82 here — alongside 81 others — read 15 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total, of which the 3 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“Алёна Кривко” (@YBIPYrPWqY4zN2Qy), 3,658 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/YBIPYrPWqY4zN2Qy.
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.