Telegram RegisterThe public register of Telegram
Telegram profile photo for gwinny | тату | Краснодар💜

Channel

gwinny | тату | Краснодар💜

@gwitattoo

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

33subscribers

+1 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002333724219
TypeChannel
Username@gwitattoo
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live2 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 2 September 2026
On Telegramt.me/gwitattoo

Growth

323332.510 August 2026 — 32 subscribers11 August 2026 — 32 subscribers25 August 2026 — 33 subscribers10 August 202625 August 2026
3 measurements spanning 15 days, net +1. 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 32–33 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 05:4733+1
11 Aug 2026, 02:3232no change
10 Aug 2026, 14:4932first reading

Engagement

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

Reaction mix

34 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 58.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2058.8%
custom 5361644869460696284617.6%
🍓411.8%
custom 536202796336363211412.94%
12.94%
👾12.94%
🦄12.94%

Custom emoji. 2 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 9 of the 12 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 12 most recent posts we hold, published 8 April 2025 to 11 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

15 May 2025, 15:07 UTC522 views4 reactionsread 11 August 2026
Photo

Сегодня ходила на МК по грейвршу. До этого не бралась практически за подобную технику ,из-за переживаний что напортачу ,но вышло даже хорошо Всё-таки не зря ходила в художественную школу,гораздо проще понять построение теней ,бликов и светотени . Тот кто говорит ,что татумастеру не обязательно уметь рисовать ,тот просто сам не умеет 😎

custom 53616448694606962842🍓1custom 53620279633636321141

8 May 2025, 18:21 UTC417 views4 reactionsread 11 August 2026
Photo

Я не пропала 👍 Сегодня продолжили забивать ногу

custom 53616448694606962844

11 Apr 2025, 17:11 UTC391 viewsread 11 August 2026

В ближайшее время будет два классных проекта👾 Постараюсь поснимать для вас контента 💜✨

8 Apr 2025, 14:43 UTC339 views3 reactionsread 11 August 2026

Сегодня сделали чудесного дракончика для второй победительницы конкурса 💜✨

3

8 Apr 2025, 14:43 UTC325 views8 reactionsread 11 August 2026
Photo

Photo, posted without a caption

51👾1🦄1

Showing the 12 most recent of 12 posts we hold for @gwitattoo. 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“gwinny | тату | Краснодар💜” (@gwitattoo), 33 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/gwitattoo.

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.