Telegram RegisterThe public register of Telegram
Telegram profile photo for [PoZZievv|🌸]-art

Channel

[PoZZievv|🌸]-art

@poZZievv34

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

172subscribers

+31 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003793637851
TypeChannel
Username@poZZievv34
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/poZZievv34

Growth

141172156.57 August 2026 — 141 subscribers8 August 2026 — 141 subscribers14 August 2026 — 146 subscribers23 August 2026 — 145 subscribers30 August 2026 — 154 subscribers9 September 2026 — 164 subscribers18 September 2026 — 172 subscribers7 August 202618 September 2026
7 measurements spanning 41 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 136–177 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 04:59172+8
9 Sept 2026, 17:59164+10
30 Aug 2026, 23:04154+9
23 Aug 2026, 06:37145-1
14 Aug 2026, 19:26146+5
8 Aug 2026, 22:16141no change
7 Aug 2026, 17:15141first reading

Engagement

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

What this channel posts

Video runtime
19s
Average length
10s

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

Reaction mix

179 reactions across 10 posts, in 13 distinct kinds. The most used accounts for 22.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52920154308886088624122.9%
🍓2312.8%
2212.3%
custom 52695820350175718072011.2%
custom 52917652189788436172011.2%
🎉116.15%
💘105.59%
custom 529183216463408753595.03%
🎄73.91%
🙏63.35%
🦄42.23%
💋31.68%
🥰31.68%

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 10 of the 10 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 179 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 4 August 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.

Recent posts

8 Aug 2026, 21:30 UTC14 views4 reactionsread 8 August 2026
Photo

🌺 ИНТЕРАКТИВ 🌺 Небольшой интерактив с ассоциациями(✿❛◡❛) Включает в себя~ -Какая вы неко из nekoconne -Какая вы палитра цветов -Какой вы цветок -Какое вы украшение -Какая вы сладость "Что нужно для участия? " -быть подписаным на меня -написать под этим постом свой никнейм [ 6/15 ] (До пятнадцати участников) ⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆

💘21custom 52695820350175718071

8 Aug 2026, 12:21 UTC55 views14 reactionsread 8 August 2026
Photo

⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆ Следующее дуо снова на ваш выбор {🌸}~cinnamon x azuki! [Nekopara] #почеркушк #мунборд ⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆

custom 529201543088860886283custom 52695820350175718072🎄1

7 Aug 2026, 18:05 UTC85 views15 reactionsread 8 August 2026
Photo

⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆ {🌸}~happy birthday donut! ✧(。•̀ᴗ-)✧ [nekoconne] #видосик ⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆

6💋3💘2custom 52920154308886088622🎄1🥰1

7 Aug 2026, 09:11 UTC92 views23 reactionsread 8 August 2026
Photo

⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆ {🌸}~два чибика(которые держутся за ручки) и два мунборда! (≧∇≦)/ Если хотите, чтобы я сделал подобное с кем то ещë, то пишите в комментарии [Spokeishere] [Jumperwho] #почеркушк #мунборд ⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆

custom 52695820350175718077🍓6custom 52920154308886088624custom 52918321646340875352🎄1💘1🥰1custom 52917652189788436171

6 Aug 2026, 14:02 UTC98 views22 reactionsread 8 August 2026
Photo

⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆ {🌸}~Hazel! (✿❛◡❛) [Nekoconne] #почеркушк ⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆

🎉11🍓4custom 52920154308886088623custom 52695820350175718072🙏1custom 52917652189788436171

6 Aug 2026, 09:58 UTC104 views21 reactionsread 8 August 2026
Photo

⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆ {🌸}~скорее всего еë купальник будет без узоров т.к их слишком долго и сложно рисовать (๑•́ω•̀) [Hazel] [nekoconne] #скетчис

10🙏4🍓2custom 52917652189788436172💘1🥰1🦄1

5 Aug 2026, 14:37 UTC116 views21 reactionsread 8 August 2026
Photo

⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆ {🌸}~небольшой арт(?) с Judelow из магмы ˙˚ʚ(´◡`)ɞ˚˙ #почеркушк ⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆

custom 529201543088860886210🦄3🍓2💘2custom 52917652189788436172🎄1custom 52695820350175718071

5 Aug 2026, 10:17 UTC182 views20 reactionsread 8 August 2026
Photo

⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆ {🌸}~реквесты для~ @dA4mmy @ynimaruniblee #почеркушк #реквест ⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆

🍓7custom 52918321646340875353💘2custom 52695820350175718072custom 52917652189788436172custom 529201543088860886221🎄1

4 Aug 2026, 14:46 UTC131 views19 reactionsread 8 August 2026
Photo

⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆ {🌸}~It's me(๑˃̵ ᴗ ˂̵)و #видосик #почеркушк ⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆

custom 52917652189788436179custom 52695820350175718074custom 52918321646340875352custom 52920154308886088622🎄1🙏1

4 Aug 2026, 12:33 UTC136 views20 reactionsread 8 August 2026
Photo

⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆ {🌸}~tamamo cross ✧(。•̀ᴗ-)✧ [Umamusume] #почеркушк ⋆ ˚。⋆୨୧˚ ˚୨୧⋆。˚ ⋆

custom 529201543088860886210custom 52917652189788436173🍓2custom 529183216463408753521🎄1custom 52695820350175718071

Showing the 10 most recent of 10 posts we hold for @poZZievv34. 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 4 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.

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.

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.

“[PoZZievv|🌸]-art” (@poZZievv34), 172 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/poZZievv34.

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.