Telegram RegisterThe public register of Telegram
Telegram profile photo for • Юлина Пасека •

Channel

• Юлина Пасека •

@phelkina_life

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

10subscribers

+1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1004353673115
TypeChannel
Username@phelkina_life
Created4 August 2026measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live18 September 2026
Measurements held3
Confirmed unchanged6 times, most recently 18 September 2026
On Telegramt.me/phelkina_life

Growth

9109.512 Aug 2026, 03:17 — 9 subscribers12 Aug 2026, 12:18 — 9 subscribers12 Aug 2026, 12:46 — 10 subscribers12 Aug 2026, 03:1712 Aug 2026, 12:46
3 measurements taken within a single day, net +1. 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 9–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:4610+1
12 Aug 2026, 12:189no change
12 Aug 2026, 03:179first reading

Engagement

17 posts held, back to 4 August 2026the 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 17 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
250.0%
🍓250.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 2 of the 17 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 4 August 2026 to 10 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

10 Aug 2026, 13:22 UTC6 viewsread 12 August 2026
Photo

🐝 Взяла эклеров в итоге. Возьму парочку и за работу. Остальное на чай с Игорем

10 Aug 2026, 12:06 UTC8 viewsread 12 August 2026
Photo

🐝 От ноутбука уже глаза болят. Решила выйти с Мико на прогулку. Может, на обратном дороге возьму пирожное себя и Игоря порадовать. А там обратно за работу

9 Aug 2026, 16:40 UTC10 viewsread 12 August 2026
Photo

🐝 Игорь пытается на спор достать игрушку из автомата. У него так и не вышло, конечно же

9 Aug 2026, 16:14 UTC10 viewsread 12 August 2026
Photo

🐝 Вышли за вкусняшками к фильму. Продукты бы по хорошему тоже взять надо

9 Aug 2026, 06:47 UTC10 viewsread 12 August 2026
Photo

🐝 Села с утра немного поработать, пока Игорь ещё спит. Я не думала, что материал собрать настолько проблематично... Ребят, если у кого-то есть не шакальные фото Чумного Доктора, то я буду рада, если поделитесь

8 Aug 2026, 17:52 UTC10 viewsread 12 August 2026
Photo

🐝 Угадайте, кого я вытащила в парк аттракционов

8 Aug 2026, 09:55 UTC11 viewsread 12 August 2026

🐝 Пицца, кстати, вышла вкусной. Но у меня лучше

8 Aug 2026, 08:48 UTC11 viewsread 12 August 2026
Photo

🐝 Теперь он решил попробовать сделать свою пиццу. Посмотрим, что получится p.s. форму я лепила, вы что думаете, она у Игоря такой аккуратной бы вышла?

7 Aug 2026, 16:31 UTC12 viewsread 12 August 2026
Photo

🐝 Готовлюсь встречать Игоря с работы. Представляю, как устал бедный с этими допросами. Будет ему вознаграждение от меня ♡

7 Aug 2026, 07:50 UTC15 viewsread 12 August 2026

🐝 Но это ещё не конец расследования. У меня есть некоторые мысли относительно Чумного Доктора, но к этому нужно собрать материал и перепроверить информацию. Позже выложу ещё такой пост и полноценное видео. Ждите, мои дорогие

7 Aug 2026, 07:47 UTC16 viewsread 12 August 2026

Как продвигается расследование по теракту на банкете Каштанина? На данный момент известно, что в деле замешано далеко не одно лицо. К сожалению, на данный момент полиция даже не может сказать, сколько их именно. Помимо группировки Цзянь, на банкете точно присутствовал Чумной Доктор и его союзники. Остановимся подробнее, почему полиция так считает. Помимо свидетельств Кирилла Макарова, давайте вспомним последний

5 Aug 2026, 15:47 UTC15 views2 reactionsread 12 August 2026
Photo

🐝 Немного пообщалась со стражами порядка. Узнала разное для репортажа по делу о теракте на банкете Каштанина. Пока ничего не расскажу, извините. Ждите, когда выложу полный объём информации ♡

2

Showing the 12 most recent of 17 posts we hold for @phelkina_life. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“• Юлина Пасека •” (@phelkina_life), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/phelkina_life.

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.