7 Aug 2026, 15:59 UTCviews —
София Грекова-Прохоренко/sofia.pro pinned «»
Channel
София Грекова-Прохоренко/sofia.pro
@SofiaGPro
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
152subscribers
-2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001647173557 |
|---|---|
| Type | Channel |
| Username | @SofiaGPro |
| Created | Between 1 December 2021 and 31 May 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 9 September 2026 |
| On Telegram | t.me/SofiaGPro |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 15:23 | 152 | -1 |
| 23 Aug 2026, 18:49 | 153 | -1 |
| 8 Aug 2026, 19:01 | 154 | no change |
| 8 Aug 2026, 15:30 | 154 | first reading |
Engagement
5 posts held, back to 29 July 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 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 5 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 5s
- Average length
- 5s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
60 reactions across 3 posts, in 11 distinct kinds. The most used accounts for 30.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5260489700921069829 | 18 | 30.0% | |
| 🕊 | 9 | 15.0% | |
| custom 5260621238589477226 | 8 | 13.3% | |
| ❤ | 8 | 13.3% | |
| 🔥 | 7 | 11.7% | |
| custom 5260448314616205866 | 3 | 5.00% | |
| custom 5257999779530559956 | 2 | 3.33% | |
| custom 5260728668606450735 | 2 | 3.33% | |
| 🗿 | 1 | 1.67% | |
| 😨 | 1 | 1.67% | |
| 😱 | 1 | 1.67% |
Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 3 of the 5 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 60 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 29 July 2026 to 7 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
7 Aug 2026, 15:58 UTC31 views10 reactionsread 8 August 2026
Posted without readable text
custom 52604483146162058663custom 52606212385894772263❤2custom 52579997795305599562
Signed Sofia Grekova-Prokhorenko
2 Aug 2026, 14:04 UTC64 views27 reactionsread 8 August 2026
Photo
Эта работа наиболее точно отражает моё сегодняшнее состояние Я словно упала в глубокую шахту внутрь себя и брожу по заброшенным шурфам и штольням в поисках призрачного блеска на гранях. Собираю себя часть за частью. Отделяю ценное от устаревшего и бесполезного. Мне нравится подолгу бывать одной. Много времени провожу в мастерской. Пока бесцельно. Просто думаю и ищу без всяких ожиданий. Иногда мне нужно общение и я…
custom 526048970092106982918🔥7🗿1😱1
Signed Sofia Grekova-Prokhorenko
29 Jul 2026, 11:23 UTC85 views23 reactionsread 8 August 2026
Photo
Выгорание Последний месяц моих сил хватает только на то, чтобы подняться, умыться, поесть и смотреть в стену, пытаясь разглядеть себя Обычно я отслеживаю у себя загорание красной лампочки и стараюсь дать себе передышку. Но в этом году так не получилось. Дел и взятых обязательств оказалось слишком много: крупная персональная выставка за 3 месяца, работа в архивах над магистерской, выступления с лекциями, руководств…
🕊9❤6custom 52606212385894772265custom 52607286686064507352😨1
Signed Sofia Grekova-Prokhorenko
29 Jul 2026, 11:23 UTC79 viewsread 8 August 2026
Photo
Photo, posted without a caption
Signed Sofia Grekova-Prokhorenko
Showing the 5 most recent of 5 posts we hold for @SofiaGPro. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“София Грекова-Прохоренко/sofia.pro” (@SofiaGPro), 152 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/SofiaGPro.
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.