Telegram RegisterThe public register of Telegram
Telegram profile photo for Spartak_kartina Картины Спартака

Channel

Spartak_kartina Картины Спартака

@spartak_kartina

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

108subscribers

-2 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-1001423917444
TypeChannel
Username@spartak_kartina
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live14 September 2026
Measurements held3
Confirmed unchanged4 times, most recently 14 September 2026
On Telegramt.me/spartak_kartina

Growth

1081101097 August 2026 — 110 subscribers9 August 2026 — 110 subscribers22 August 2026 — 108 subscribers7 August 202622 August 2026
3 measurements spanning 15 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 108–110 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 09:17108-2
9 Aug 2026, 07:17110no change
7 Aug 2026, 10:33110first reading

Engagement

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

What this channel posts

Video runtime
1m 30s
Average length
15s

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

70 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 45.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3245.7%
👍2941.4%
🔥912.9%

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

Measured over the 13 most recent posts we hold, published 5 January 2023 to 25 May 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 May 2026, 07:57 UTC77 views4 reactionsread 9 August 2026
Video

Стадион, трибуны, эмоции - в формате модульной картины 🔴⚪️

🔥4

29 Jul 2025, 13:30 UTC210 views3 reactionsread 9 August 2026
Video

🔴⚪️ СЕЙЧАС БУДЕТ МЯСО Картина для тех, кто идёт до конца. Наш фирменный кабан - символ силы, дерзость и духа Спартака. В наличии. Пиши в личку.

👍3

25 Jul 2025, 10:54 UTC208 views6 reactionsread 9 August 2026
Photo

Картина с красно-белой легендой 🔴⚪️

6

16 Jul 2025, 18:30 UTC245 views4 reactionsread 9 August 2026
Video

Совсем скоро возобновится сезон и мы вернёмся на наш родной стадион! 🔴⚪️ И вновь будем болеть и верить в чемпионство! Вперёд Спартак! ❤️🤍

4

24 Feb 2025, 19:25 UTC434 views4 reactionsread 9 August 2026
Photo

С детства за Спартак ❤️🤍

4

21 Sept 2024, 16:09 UTC677 views4 reactionsread 9 August 2026
Photo

Хоккейный Спартак мы тоже любим ❤️🤍

4

30 Apr 2023, 06:11 UTC819 views14 reactionsread 9 August 2026
Video

Самая любимая картина 😍

👍8🔥51

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

“Spartak_kartina Картины Спартака” (@spartak_kartina), 108 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/spartak_kartina.

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.