Channel
@PyHeKcore
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
225subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003862217227 |
|---|---|
| Type | Channel |
| Username | @PyHeKcore |
| Description | предложка для постов: https://t.me/PyHeKcore_bot |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/PyHeKcore |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 03:02 | 225 | no change |
| 6 Aug 2026, 23:17 | 225 | first reading |
20 posts held, back to 16 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 20 (16 July 2026 – 4 August 2026) |
| Views total | 7,093 |
| Reactions total | 430 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 03:02 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
430 reactions across 20 posts, in 11 distinct kinds. The most used accounts for 18.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5470123279362595609 | 81 | 18.8% | |
| 🦄 | 72 | 16.7% | |
| custom 5199629481760813914 | 60 | 14.0% | |
| 👀 | 50 | 11.6% | |
| custom 5465391896144683363 | 44 | 10.2% | |
| custom 5192834615865285537 | 39 | 9.07% | |
| custom 5303108704348957716 | 37 | 8.60% | |
| custom 5447372090271362963 | 21 | 4.88% | |
| custom 5393129964742663838 | 13 | 3.02% | |
| custom 5195408740089615092 | 11 | 2.56% | |
| 🤷♀ | 2 | 0.465% |
Custom emoji. 8 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 areTelegram’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 20 of the 20 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 430reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 16 July 2026 to 4 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.
вкину вам спойлер вместе со мной будут... гельмо, альцест, рунек, ники, неркин(я надеюсь) и секби из старых саппортов. все ваши любимые
custom 53031087043489577162custom 54701232793625956091
Signed 𝓷•ms
надп сделать переоформу 😭
custom 51928346158652855375
Signed 𝓷•ms
https://t.me/PyHeKcore_bot есть предложка для постов, тк я занятой меловек, то свои идеи не успеваю реализовать, но ваши я могу всегда выложиьь
custom 530310870434895771610custom 54701232793625956098
Signed 𝓷•ms
канал отделяется от основной сетки, подробностей не будет, но я продолжу работу сразу после того как освобожусь от дел 😺
custom 519962948176081391411custom 54701232793625956097
Signed 𝓷•ms
мы все просрали
custom 547012327936259560916👀9custom 51996294817608139147custom 51928346158652855373custom 51954087400896150921custom 53931299647426638381custom 54473720902713629631
Signed 𝓷•ms
🌟🌟дᴀ,я ᴛᴩу ᴋинн ᴩунᴇᴋᴀ и… и мой алфедов кинни много для меня значит 🦷@kinncoremineshield @PyHeKcore🦷
custom 53031087043489577169custom 54701232793625956094custom 54473720902713629633custom 51996294817608139142custom 54653918961446833632
Signed 𝓷•ms
🌟🌟дᴀ,я ᴛᴩу ᴋинн ᴩунᴇᴋᴀ и… и мой алфедов кинни готов поставить ВСЕ ради свободы 🦷@kinncoremineshield @PyHeKcore🦷
🦄5custom 53031087043489577162custom 53931299647426638382custom 54653918961446833632custom 54701232793625956092
Signed 𝓷•ms
🌟🌟дᴀ,я ᴛᴩу ᴋинн ᴩунᴇᴋᴀ и… Я ГОТОВ ПОДДЕРЖАТЬ СВОЕГО алфедов кинни!!! 🦷@kinncoremineshield @PyHeKcore🦷
custom 51996294817608139146custom 54701232793625956094custom 54473720902713629633custom 54653918961446833631
Signed 𝓷•ms
🌟🌟дᴀ,я ᴛᴩу ᴋинн ᴩунᴇᴋᴀ и… наши с алфедов кинни особенности делают нас ближе 🦷@kinncoremineshield @PyHeKcore🦷
custom 53031087043489577169custom 51928346158652855377custom 54701232793625956096custom 54653918961446833633custom 53931299647426638382custom 54473720902713629632
Signed 𝓷•ms
елки
custom 51996294817608139148
Signed 𝓷•ms
ПЕЙРИНГ НА ИВЕНТ
The shares total 152%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
custom 519962948176081391411custom 53931299647426638382custom 54473720902713629632custom 51928346158652855371
Signed 𝓷•ms
руоши на этом канале запретный плод
custom 519283461586528553711custom 54473720902713629634👀2custom 51954087400896150922custom 51996294817608139142
Signed 𝓷•ms
Showing the 12 most recent of 20 posts we hold for @PyHeKcore. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
ПЕЙРИНГ НА ИВЕНТ
The shares total 152%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 20 most recent posts we hold, published 16 July 2026 to 4 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.
Citation-graph rank — 170,261 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 4 registered channels — 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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“серега PyHeK core” (@PyHeKcore), 225 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/PyHeKcore.
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.