Telegram RegisterThe public register of Telegram
Telegram profile photo for кучерявый пи́шке

Channel

кучерявый пи́шке

@curlypishke

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

1,309subscribers

-31 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001964778740
TypeChannel
Username@curlypishke
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/curlypishke

Growth

1,3081,3401,3247 August 2026 — 1,340 subscribers7 August 2026 — 1,340 subscribers11 August 2026 — 1,339 subscribers14 August 2026 — 1,333 subscribers17 August 2026 — 1,332 subscribers20 August 2026 — 1,331 subscribers23 August 2026 — 1,329 subscribers26 August 2026 — 1,330 subscribers29 August 2026 — 1,323 subscribers1 September 2026 — 1,317 subscribers4 September 2026 — 1,316 subscribers10 September 2026 — 1,308 subscribers13 September 2026 — 1,309 subscribers1,3097 August 202613 September 2026
13 measurements spanning 37 days, net -31. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,303–1,345 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 20:211,309+1
10 Sept 2026, 03:411,308-8
4 Sept 2026, 12:581,316-1
1 Sept 2026, 09:081,317-6
29 Aug 2026, 04:551,323-7
26 Aug 2026, 05:181,330+1
23 Aug 2026, 15:461,329-2
20 Aug 2026, 06:121,331-1
17 Aug 2026, 15:581,332-1
14 Aug 2026, 07:081,333-6
11 Aug 2026, 08:441,339-1
7 Aug 2026, 22:221,340no change
7 Aug 2026, 15:571,340first reading

Engagement

19 posts held, back to 25 July 2026the 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 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2s
Average length
2s

Measured directly from 1 video 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.

Reaction mix

814 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 44.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
36544.8%
💔14617.9%
🔥9011.1%
🤣8610.6%
😢455.53%
🥰394.79%
🤪253.07%
🤝182.21%

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 19 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 814 reactions 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 25 July 2026 to 6 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.

Recent posts

5 Aug 2026, 23:12 UTC370 views37 reactionsread 7 August 2026
Photo

Photo, posted without a caption

20🥰11🔥6

4 Aug 2026, 13:32 UTC399 views38 reactionsread 7 August 2026
Video message

Video message, posted without a caption

26🔥9🤪3

4 Aug 2026, 10:45 UTC426 views32 reactionsread 7 August 2026

Я в шоке, у меня до сих пор есть хейтеры!

🔥257

4 Aug 2026, 10:29 UTC426 views54 reactionsread 7 August 2026

Ну, с чем-то я согласна, но это поверхностный вывод о человеке, который делится только тем, что считает нужным. Я занималась организацией похорон, и это дало мне понять, что я способна решать серьезные вопросы при необходимости. Не было такой необходимости, о чем я и писала. В остальном так-то мы не знакомы. Я, может, и паразит, и для вас такие отношения неприемлемы, но очень странно меня за это оскорблять. Я никому

37🤝11🔥5💔1

4 Aug 2026, 10:18 UTC407 views19 reactionsread 7 August 2026

Сколько я наблюдая,вывод однозначный, сначала на шее отца были,теперь на шее "мужа",сама ничего не добилась и не сможешь,инфантильность 1000 из 10,толку от тебя 0.Позаботиться о семье не сможешь, ты не равноценный партнёр, а обычный паразит.

🤪11🤣5🔥2😢1

4 Aug 2026, 01:45 UTC432 views30 reactionsread 7 August 2026
Photo

Вспомнилось, что я писала об этом 10 лет назад)

30

4 Aug 2026, 01:38 UTC430 views39 reactionsread 7 August 2026

После смерти папы пробила сильная ностальгия. Вспоминаю детство и школу, пожалуй, самые насыщенные и светлые годы моей жизни. Задумываюсь о том, что останется, если меня не станет также неожиданно. Так сложилось, что моя по-настоящему взрослая жизнь, в том числе благодаря тому, что папа избавил нас от многих забот, начинается именно сейчас. Только вот я совершенно не могу представить, какой она будет дальше. У меня

32🤝4🥰3

4 Aug 2026, 00:49 UTC417 views8 reactionsread 7 August 2026
Photo

🥺💔 (знать бы ещё кто это был)

🤣6💔2

4 Aug 2026, 00:43 UTC417 views8 reactionsread 7 August 2026
Photo

Коллеги, не упустите шанс… такая легенда пропала… Ещё во времена жизни в Норильске мы с подружкой вели там дневники, проходили и составляли тесты, я даже писала фанфики 🤫 Хорошее было время. Рылась в своей почте и попались сообщения о добавлении в друзья каких-то пользователей. Перешла по ссылке, а там такое. Жалко!

💔8

3 Aug 2026, 15:00 UTC494 views23 reactionsread 7 August 2026
Video message

Video message, posted without a caption

22🤣1

Showing the 12 most recent of 19 posts we hold for @curlypishke. 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.

Cite this entry

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 13 September 2026 — this entry's latest reading, not the date you are reading this.

“кучерявый пи́шке” (@curlypishke), 1,309 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/curlypishke.

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.