26 Jul 2026, 18:06 UTC42 views10 reactionsread 9 August 2026
Photo
Ближайшие занятие в Музее 16 августа в 13:00 Готовимся к Яблочному Спасу! Билеты: https://vdnh.ru/events/3697/
❤4custom 52943065940775677654custom 54630116252692248342
Channel
ПИШУ КРАСИВО
@pishykrasivo
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
130subscribers
+2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001538783735 |
|---|---|
| Type | Channel |
| Username | @pishykrasivo |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/pishykrasivo |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 19:58 | 130 | +1 |
| 10 Sept 2026, 22:40 | 129 | +1 |
| 1 Sept 2026, 16:28 | 128 | -1 |
| 25 Aug 2026, 03:03 | 129 | -1 |
| 16 Aug 2026, 17:45 | 130 | +2 |
| 9 Aug 2026, 01:46 | 128 | no change |
| 8 Aug 2026, 03:18 | 128 | first reading |
Engagement
4 posts held, back to 12 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 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 4 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 34s
- Average length
- 34s
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
34 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 23.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5465545608729225469 | 8 | 23.5% | |
| custom 5294306594077567765 | 7 | 20.6% | |
| custom 5463011625269224834 | 7 | 20.6% | |
| ❤ | 4 | 11.8% | |
| 🥰 | 3 | 8.82% | |
| custom 5226795218627479975 | 2 | 5.88% | |
| ❤🔥 | 2 | 5.88% | |
| 😍 | 1 | 2.94% |
Custom emoji. 4 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 are Telegram’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 4 of the 4 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 34 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 12 July 2026 to 26 July 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
12 Jul 2026, 09:15 UTC74 views8 reactionsread 9 August 2026
Photo
Photo, posted without a caption
custom 54655456087292254693custom 52267952186274799752custom 54630116252692248342❤🔥1
12 Jul 2026, 09:15 UTC53 views8 reactionsread 9 August 2026
Photo
Photo, posted without a caption
custom 54630116252692248343custom 52943065940775677652custom 54655456087292254692❤🔥1
12 Jul 2026, 09:14 UTC51 views8 reactionsread 9 August 2026
Photo
https://t.me/pishykrasivo/641 Этой красотой хочется делиться! В свободное окно в конце сентября приглашаю готовую команду новичков и бывалых (семьи, друзья, коллеги - 8 человек - 4 каюты) в арт- яхтинг по маршруту на выбор: Турция Греция Черногория Почему арт, а не просто яхтинг? Название появилось с легкой руки известного московского искусствоведа и галеристки, моей подруги и компаньонки, Анны Вихровой. Арт- ма…
🥰3custom 54655456087292254693😍1custom 52943065940775677651
Showing the 4 most recent of 4 posts we hold for @pishykrasivo. 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.
Forward network
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.
Mentions
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“ПИШУ КРАСИВО” (@pishykrasivo), 130 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/pishykrasivo.
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.