Channel
@pikitych
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
71subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002681783210 |
|---|---|
| Type | Channel |
| Username | @pikitych |
| Description | здарова Аватарка: @bunya_puck |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/pikitych |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 23:31 | 71 | no change |
| 8 Aug 2026, 20:01 | 71 | first reading |
19 posts held, back to 23 June 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 8 August 2026 |
|---|---|
| Posts held | 19 (23 June 2026 – 8 August 2026) |
| Views total | 739 |
| Reactions total | 126 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 23:31 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 9 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.
Measured directly from 3 videos 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.
294 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 29.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5208553852571258146 | 86 | 29.3% | |
| custom 6203821830889801334 | 47 | 16.0% | |
| custom 5283148771553714735 | 44 | 15.0% | |
| custom 5201957835071578006 | 38 | 12.9% | |
| custom 5372965329511139384 | 31 | 10.5% | |
| custom 5454092060527181056 | 26 | 8.84% | |
| custom 5465515977749836039 | 22 | 7.48% |
Custom emoji. Every row above is a 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 18 of the 19 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 294reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 23 June 2026 to 8 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.
У меня куча комплексов #Глазастик@pikitych
custom 52831487715537147355custom 52019578350715780063custom 62038218308898013342custom 52085538525712581461custom 53729653295111393841custom 54540920605271810561custom 54655159777498360391
Я покидаю Россию друзья всем пока завтра мене тут не будет вот прощальный Ко́та #Скетч@pikitych #Объём@pikitych
custom 52085538525712581469custom 52019578350715780064custom 52831487715537147354custom 53729653295111393843custom 54540920605271810561custom 54655159777498360391custom 62038218308898013341
Это мое обещание на 13 мен лав мен? Это адопт ставки принимаются в коммы
custom 62038218308898013347custom 52019578350715780061custom 52831487715537147351custom 54655159777498360391
Вот оно чудовище я его уже презирать начинаю Все я больше не покажу наверное его до окончания работы И вот посты снова уходят в забытьё всем пока 👋 #Глазастик@pikitych
custom 62038218308898013349custom 52085538525712581465custom 54540920605271810564custom 53729653295111393842custom 52019578350715780061custom 52831487715537147351custom 54655159777498360391
Channel photo updated
Мы сидим тута, вдвоем тута сидим тута
custom 52831487715537147351
❤️ Ещё заказек для @pikitych Рисовала для админа из шопа где я работаю, у меня не было права ошибиться ⛓ Вот ещё прикол ээ, эту комишку я нарисовала на ноуте, ну помните да что у меня планшет хлопнулся, вот и рисую на гп, И ЭТО КАПЕЦ, ноут у меня в принципе не свежак, а тут ещё и прога очень часто зависала и вылитала, благо крита файлы сохраняет😘 но я всё равно больше ждала прогрузки чем рисовала И у меня в какой-то …
custom 52085538525712581466custom 53729653295111393844custom 54540920605271810564custom 52831487715537147351custom 62038218308898013341
Это другое говно новое не старое это другое новое маскот милпис хауса шопа новое #Скетч@pikitych #Глазастик@pikitych
custom 53729653295111393847custom 52085538525712581464custom 52019578350715780062custom 52831487715537147351custom 54540920605271810561
Я просто может не появлюсь в ближайшее время ребят правда плохо мне
custom 52019578350715780067
Оказывается ставить якоря при риггинге очень полезно Я правда наобум делаю без какого-то смысла в движениях от этого он такой странный лол урод фу 👸 ☁️Плюс я погрязла в арк на планшете и не могу оттуда вылезти ☁️И еще плюс я устала рисовать я не знаю у меня какая-то апатия очередная #Процесс@pikitych #Глазастик@pikitych
custom 52085538525712581466custom 53729653295111393843custom 54540920605271810563custom 52019578350715780062custom 52831487715537147351custom 54655159777498360391custom 62038218308898013341
Я его запорола и мне стыдно Еще я не рисую потому что задрочу в динозавров поэтому знайте что случилось если меня долго не будет Аук сжечь #Лайновый@pikitych
custom 54655159777498360398custom 52085538525712581465custom 52019578350715780062custom 52831487715537147352custom 54540920605271810562custom 53729653295111393841custom 62038218308898013341
#Процесс@pikitych
custom 520855385257125814613custom 52831487715537147352custom 54540920605271810562
Showing the 12 most recent of 19 posts we hold for @pikitych. 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 — 490,688 of 1,336,469entries 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 7 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Даблунчики Пикитучо” (@pikitych), 71 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/pikitych.
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.