Channel
@pornohabkoritsa
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
9subscribers
-1 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002775161820 |
|---|---|
| Type | Channel |
| Username | @pornohabkoritsa |
| Created | 20 August 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/pornohabkoritsa |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 20:57 | 9 | -2 |
| 3 Sept 2026, 09:29 | 11 | +1 |
| 13 Aug 2026, 03:26 | 10 | no change |
| 12 Aug 2026, 09:01 | 10 | first reading |
16 posts held, back to 20 August 2025 — 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 16 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
100 reactions across 8 posts, in 20 distinct kinds. The most used accounts for 18.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5276172563549032962 | 18 | 18.0% | |
| custom 5341308568681336577 | 8 | 8.00% | |
| custom 6302928295734286327 | 8 | 8.00% | |
| custom 5215439844787906963 | 7 | 7.00% | |
| custom 5298905623583287855 | 7 | 7.00% | |
| custom 5305647171754824317 | 5 | 5.00% | |
| custom 5307733980399835871 | 5 | 5.00% | |
| custom 5413560625953545488 | 5 | 5.00% | |
| 🍓 | 5 | 5.00% | |
| 🍾 | 5 | 5.00% | |
| custom 5278353745510436981 | 4 | 4.00% | |
| custom 5341605441115822486 | 4 | 4.00% | |
| custom 5431628526870622260 | 4 | 4.00% | |
| custom 5299009548906953203 | 3 | 3.00% | |
| custom 5377860119054811374 | 3 | 3.00% | |
| 💘 | 3 | 3.00% | |
| custom 5449694769930336920 | 2 | 2.00% | |
| 🕊 | 2 | 2.00% | |
| custom 5341524386492995361 | 1 | 1.00% | |
| custom 5341703160211721110 | 1 | 1.00% |
Custom emoji. 16 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 8 of the 16 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 100 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 20 August 2025 to 11 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.
💕💕💕🌟🌟🌟🌟🌟💕💕💕 💕✨ 🎀isha's playlist 🤩 🥹🐾 🐾🥹I'm just piece of cake 🤩🤩
custom 52761725635490329623custom 52154398447879069632custom 52783537455104369812custom 53056471717548243172custom 53413085686813365772custom 53778601190548113742custom 54316285268706222602custom 53077339803998358711
Sticker, posted without a caption
♡ . . . нацуки задалась вопросом . . . кто же всё-таки её соулмейт ? . . . ➪ это же . . . @hannawq0 ! ( 176 гс ) #rules ; @hottest_irl
custom 52989056235832878554custom 52761725635490329623custom 53413085686813365773custom 52154398447879069631custom 52990095489069532031custom 53415243864929953611custom 53417031602117211101custom 63029282957342863271
Sticker, posted without a caption
𝘫𝘶𝘴𝘵 𝘮𝘰𝘯𝘪𝘬𝘢. 🌟🌟
Shares as published. No per-option vote count is published by Telegram, so none is shown.
custom 52989056235832878553custom 52761725635490329622custom 63029282957342863272custom 52154398447879069631custom 52990095489069532031custom 53413085686813365771custom 54316285268706222601custom 54496947699303369201
Sticker, posted without a caption
🤩𝘰 𝘺𝘰𝘶 𝘢𝘤𝘤𝘦𝘱𝘵 𝘮𝘺 𝘤𝘰𝘯𝘧𝘦𝘴𝘴𝘪𝘰𝘯 ? 🎁
Shares as published. No per-option vote count is published by Telegram, so none is shown.
custom 52761725635490329623custom 54135606259535454882custom 52154398447879069631custom 53056471717548243171custom 53077339803998358711custom 53416054411158224861custom 54316285268706222601custom 63029282957342863271
Sticker, posted without a caption
ㅤ ㅤㅤㅤ𝘴𝘢-𝘺𝘰-𝘯𝘢-𝘳𝘢 . 🌟🌟
custom 52761725635490329622custom 63029282957342863272custom 52990095489069532031custom 53416054411158224861custom 54135606259535454881
Sticker, posted without a caption
🔥𝘪𝘴𝘩𝘢 𝘪𝘴 . . .
Shares as published. No per-option vote count is published by Telegram, so none is shown.
custom 52761725635490329622custom 52783537455104369811custom 53077339803998358711custom 53413085686813365771custom 53416054411158224861custom 54135606259535454881custom 54496947699303369201custom 63029282957342863271
Sticker, posted without a caption
Showing the 12 most recent of 16 posts we hold for @pornohabkoritsa. 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.
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
𝘫𝘶𝘴𝘵 𝘮𝘰𝘯𝘪𝘬𝘢. 🌟🌟
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🤩𝘰 𝘺𝘰𝘶 𝘢𝘤𝘤𝘦𝘱𝘵 𝘮𝘺 𝘤𝘰𝘯𝘧𝘦𝘴𝘴𝘪𝘰𝘯 ? 🎁
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🔥𝘪𝘴𝘩𝘢 𝘪𝘴 . . .
Shares as published. No per-option vote count is published by Telegram, so none is shown.
who are you . . ?? 🌟
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 16 most recent posts we hold, published 20 August 2025 to 11 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“риша info” (@pornohabkoritsa), 9 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/pornohabkoritsa.
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.