умене день рождения
❤🔥3❤2

Channel
@pchelichkap
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
314subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002142163790 |
|---|---|
| Type | Channel |
| Username | @pchelichkap |
| Created | 14 January 2024 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/pchelichkap |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 17:52 | 314 | +4 |
| 8 Aug 2026, 07:46 | 310 | no change |
| 7 Aug 2026, 19:57 | 310 | first reading |
11 posts held, back to 20 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 | 11 (20 July 2026 – 4 August 2026) |
| Views total | 1,679 |
| Reactions total | 177 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 07:46 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.
177 reactions across 11 posts, in 12 distinct kinds. The most used accounts for 29.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 52 | 29.4% | |
| ❤🔥 | 37 | 20.9% | |
| custom 5469655033438029870 | 25 | 14.1% | |
| custom 5197353978022625749 | 14 | 7.91% | |
| custom 5811952115769154909 | 14 | 7.91% | |
| 😭 | 11 | 6.21% | |
| 💘 | 8 | 4.52% | |
| 🔥 | 7 | 3.95% | |
| 🍓 | 6 | 3.39% | |
| 🎉 | 1 | 0.565% | |
| 🙏 | 1 | 0.565% | |
| 🤩 | 1 | 0.565% |
Custom emoji. 3 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 11 of the 11 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 177reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 20 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.
умене день рождения
❤🔥3❤2
🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 Мой ребеночек сегодня отмечает день рождения!! Как же быстро растут детишки....😭 Давайте поздравим её и пожелаем чего-нибудь хорошего 🤩 А у нас планируется что-то совместное..что-то очень интересное..... 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 #shitpost #bday
❤🔥3custom 54696550334380298702🎉1
🤩 🌟🌟🌟🌟🌟🌟🌟🌟 🤩 Сегодня, наверное, будет САМОЕ необычное и неожиданное событие за всю историю моей косплей-деятельности....🤩🤩 И так........... 🥑🧦🌰🧦©️❗️ 🤩15-го августа я буду присутствовать на Seoul Comic World 2026 в Ильсане 😊😊...... В полностью новом косплее на Рагату! Да, я целиком переделываю ее костюм. Парик, платье, пуговица..все будет абсолютно новым!!🌟 В дни до этого прекрасного события будет…
❤11❤🔥5custom 51973539780226257494🔥2💘1🤩1
Вкидываю и убегаю..🌟 С этой чудесной фоткой еще и пост будет скоро!!! Типография ONLINE очень радует, спасибо ребятам за скорость 🤩 Скоро будут на руках! ;) #shitpost
❤8custom 51973539780226257493custom 58119521157691549092💘1custom 54696550334380298701
🤍⭐️⭐️⭐️⭐️🤩🤩🤩🤩⭐️⭐️⭐️⭐️🤍 🫶🫶🫶🫶🫶🌟🫶–🫶🫶🫶🫶 🪦🪦🪦🤩🤩🤩🤩🤩🤩🤩🤩🪦🪦🪦 В этот день настала очень важная дата..😚 💽💽Сегодня, 27.07, день 💽💽 рождения у моей любимой девушки❗️❗️❗️ Вместе мы прошли огонь и воду, помогали друг другу в тяжелых периодах, а главное, что бы не происходило - мы оставались рядом 😀😀 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 Я безумно ценю тебя, любимый мой. Хоть я уже все и сказала тебе лично, но тех слов точно не хватит…
❤🔥13❤8🍓6💘4custom 58119521157691549092🙏1custom 51973539780226257491custom 54696550334380298701
🤩 🤩🤩🤩🤩🤩🤩🤩🤩 🤩 😭К сожалению, Акамару я пропускаю..так много дел навалилось, что недосып уже убивает, XD)) Нооо..это не значит, что контента не будет!! В скором времени я расскажу вам кое-что оооочень интересное, косплеев и интересного лайфа будет безумно много 🤩🤩 #shitpost
😭11custom 54696550334380298703❤1
[ 🌟🌟🌟🌟🌟🌟🌟🌟 ] ☕️™️🌰🐸☝️☝️☝️ Не жравши, не спавши, но зато весело!!💘 Максимально крутое мероприятие, в випке так вообще как дома) Много пофоткалась у фотографов, а также, жду фоточки с Эпик Кона. Хочу сделать пост как можно быстрее 🤩 Хоть я и безумно устала, но с радостью пойду завтра на Акамару!! Спасибо моему любимому партнеру - Икичу, конечно же. Без него было бы намного хуже 💘 [ 🌟🌟🌟🌟🌟🌟🌟🌟 ] #cosplay #crk #even
custom 54696550334380298709custom 58119521157691549095custom 51973539780226257493❤1
Мэджик не щадит никого..🤩🤩 🌟🌟🌟🌟🌟 А мы тут с Люмой!! 💓 #cosplay #event #crk
❤10🔥5custom 54696550334380298704
🌟🌟Что-то я совсем 🌟🌟забегалась и забыла про воскресенье.. 🌟 🥑🧦🌰🧦©️🌟 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 Благодаря конкурсу Вилушки, я буду гулять на Акамару в компании Люмы! И, раскрываю вам свой новый косплей..Саммер из Рика и Морти!! Сама не ожидала, что закосплею эту даму..все решили за меня, хехе 🤩 Как раз-таки на Акамару увидите как она выйдет) С кем увидимся?🤩🤩🤩🤩 П.с: сверху есть еще один анонс на…
❤7❤🔥3custom 54696550334380298703💘2
Posted without readable text
❤🔥5❤2custom 54696550334380298701custom 58119521157691549091
~ Итоги розыгрыша Несмотря на все ”приколы” , настало времечко подвести итоги!! Результаты розыгрыша: 1. Верочка (@Vera_VK) 2. МИНИ РЕСТただいま🍮𝒑𝒄𝒉𝒆𝒍𝒌𝒂࿔‧ ֶָ֢˚˖𐦍˖˚ֶָ֢ ‧࿔#𝘪𝘬𝘪𝘤𝘩𝘬𝘪𝘴𝘴𝘦𝘳 #𝙬𝙞𝙣𝙙𝙮31𝙞𝙧𝙡 (@whyp4h3lka) 3. 15:26 (@Firefly_025) Если в этот раз удача была не на вашей стороне, не расстраивайтесь, ведь скоро с одним магазинчиком проведем еще розыгрыш, а пока можете попытать удачу в конкурсе на билеты на Акамару у Шерлок
❤🔥5custom 58119521157691549094custom 51973539780226257493❤2custom 54696550334380298701
Showing the 11 most recent of 11 posts we hold for @pchelichkap. 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.
Citation-graph rank — 368,377 of 1,480,944entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 2 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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“ᴘᴄʜᴇʟᴋᴀ'ꜱ ᴍᴇᴍᴏɪʀꜱ🧁” (@pchelichkap), 314 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/pchelichkap.
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.