Telegram RegisterThe public register of Telegram
Telegram profile photo for СВОБОДА АРТ

Channel

СВОБОДА АРТ

@svobodaart_el

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

168subscribers

-2 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-1001425883713
TypeChannel
Username@svobodaart_el
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live18 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/svobodaart_el

Growth

168171169.510 August 2026 — 170 subscribers10 August 2026 — 170 subscribers25 August 2026 — 171 subscribers1 September 2026 — 170 subscribers18 September 2026 — 168 subscribers10 August 202618 September 2026
5 measurements spanning 39 days, net -2. 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 168–171 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 13:21168-2
1 Sept 2026, 23:06170-1
25 Aug 2026, 21:37171+1
10 Aug 2026, 12:45170no change
10 Aug 2026, 12:32170first reading

Engagement

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

What this channel posts

Video runtime
47s
Average length
16s

Measured directly from 3 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

22 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5411224056370307360836.4%
custom 5425078044614225205836.4%
custom 5222099685501593500313.6%
custom 5253820857955941349313.6%

Custom emoji. Every row above is a 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 3 of the 3 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 22 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 3 most recent posts we hold, published 20 April 2026 to 5 June 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 Jun 2026, 17:18 UTC166 views7 reactionsread 10 August 2026
Photo

30 мая мы оформили фото•зону и селфи•зеркало для фестиваля сообщества «PROженщин». Наш проект назывался «цветы». 🌹🌸 👨‍🍼 Спонсоры и организаторы доверили нам эту задачу, и мы с ней справились. Масштабные цветы для фотосессий мы создали вручную, результат гостей и организаторов впечатлит. Признаться, нас тоже 🥀 Да-да, мы видели как много прекрасных женщин фотографировались с большим удовольствием ;)

custom 54112240563703073603custom 54250780446142252053custom 52220996855015935001

18 May 2026, 08:26 UTC98 views8 reactionsread 10 August 2026
Photo

приветствуем вас 🤲🦪 Мы завершили проект по оформлению вечеринки «куролесье». В этот раз, нужно было придумать концептуальный декор на тему «рассвет». Мы исходили из темы и нашего в данный момент полюбившегося материала. Наши абстрактные формы, напоминающие облака отлично вписались в дизайн интерьера пространства и придали вечеру атмосферы.

custom 54250780446142252054custom 52220996855015935002custom 54112240563703073602

20 Apr 2026, 12:35 UTC114 views7 reactionsread 10 August 2026
Photo

завершили проект для стоматологический клиники Dr.Plombir. получилось красиво и качественно, на целый летний сезон. у нас есть личные каналы, где вы можете посмотреть и почитать более подробно об этом декораторском проекте. Welcome ✨🤲🌸 https://t.me/alinushkamuse https://t.me/ansivia_art

custom 52538208579559413493custom 54112240563703073603custom 54250780446142252051

Showing the 3 most recent of 3 posts we hold for @svobodaart_el. 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

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.

“СВОБОДА АРТ” (@svobodaart_el), 168 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/svobodaart_el.

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.