Channel
@piko_life_aww
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
12subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002649200093 |
|---|---|
| Type | Channel |
| Username | @piko_life_aww |
| Description | А ось тут пишу вселякі дурниці про все на цьому світі 🌚 Посилання на інші мережі шукайте в закріпленому. Дякую за увагу 😘 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/piko_life_aww |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:46 | 12 | no change |
| 12 Aug 2026, 10:34 | 12 | first reading |
17 posts held, back to 2 August 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 17 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
45 reactions across 17 posts, in 2 distinct kinds. The most used accounts for 86.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 39 | 86.7% | |
| ❤🔥 | 6 | 13.3% |
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 17 of the 17 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 45 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 2 August 2026 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.
Взагалі, я задумувався, чому ШІ-музика мені настільки огидна, а вокалоїди, наприклад, дуже подобаються. Здавалося б: і там, і там - штучний голос. Але все ж вокалоїд - це інструмент, наприклад, як електрогітара або синтезатор. Людина керує цим інструментом і він допомагає висловити людині своє бачення, свій світ. А ось ШІ - це не інструмент. Це імітація живої людини. Причому ця імітація провалює мене в ту саму "зло…
❤2❤🔥1
А ще хтось з цього гурту переробив крінжово цю пісню через ШІ і назвали це "Рімейк" - жах-жах-жах. Мабуть той, хто має права на цю музику, думав "зараз залетить" - і, насправді, шанси були, бо зараз мода на 80-90 + ШІ. Щиро радий, що не вийшло.
❤2❤🔥1
Сиджу промиваю собі мізки "туц-туц" музикою, і ютуб підкидує це. Звучання таке, що я думав це якийсь прикол під 90-ті, а це реально пісня з 90-х🗿 Але загалом мені сподобалося.
❤2
https://music.youtube.com/watch?v=HjgTCZ3lV6k&si=Xaa5U7LaPh68xDoB
❤2
Мені здається, чи в Південній Кореї трошки переборщили з кількістю доріг? 😂
❤2❤🔥1
Photo, posted without a caption
❤2❤🔥1
Photo, posted without a caption
❤2
Ого написюкав... Але думаю ті хто зацікавлений в цьому питанні почитають. А ще пишіть у коментарях свою думку - мені вельми цікаво почитати.
❤3
Продовжую цю тему, бо все ще несеться про ці недолугі канали. Я зрозумів, що деякі люди справді доволі емоційно реагують на такі речі. Насправді, я доволі суб'єктивно поставився до цього питання, бо в моїх очах це купка ображених ідіотів, котрі нічого краще не знайшли, ніж зайнятися старою доброю токсичністю заради своїх "вищих" цілей чи то заради "емоцій" в штаніках. Але я вас сильно вкушу, якщо почую, що укр арт …
❤2
Там, до речі, якщо цікаво, з одним із каналів все закінчилося добре. Щось там перетерли - і тепер все добре. Шкільні розбірки - моє оціночне судження 🤭 Сподіваюся, в майбутньому їхні пости будуть менш емоційними й більше про дії.
❤2❤🔥1
Якщо збираєтесь колись ось так написати пост, то вже пишіть про дії, які потрібно людям зробити. В цій ситуації це, наприклад, кидати скарги на публікації з булінгом - це як мінімум. А то виглядає як популізм.
❤2
Я людина скептична. І ось вам приклад того, як насправді НЕ ТРЕБА писати про таких дуриків. Весь цей текст несе один посил - "Загроза. Ви можете бути наступними!" - але на ділі не каже, що людям із цим робити. І це так дивно. Як пернути в калюжу 🤭
❤2❤🔥1
Showing the 12 most recent of 17 posts we hold for @piko_life_aww. 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.
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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Тут живе Піко 🫦” (@piko_life_aww), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/piko_life_aww.
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.