Telegram RegisterThe public register of Telegram
Telegram profile photo for Classic UC Shop

Channel

Classic UC Shop

@UcClassicShop

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

61subscribers

-22 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-1002408373190
TypeChannel
Username@UcClassicShop
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live2 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/UcClassicShop

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 87% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

6183727 August 2026 — 83 subscribers8 August 2026 — 82 subscribers9 August 2026 — 82 subscribers16 August 2026 — 77 subscribers24 August 2026 — 75 subscribers1 September 2026 — 72 subscribers9 September 2026 — 70 subscribers18 September 2026 — 64 subscribers2 October 2026 — 61 subscribers7 August 20262 October 2026
9 measurements spanning 56 days, net -22. 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 58–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 19:5861-3
18 Sept 2026, 16:5764-6
9 Sept 2026, 19:3970-2
1 Sept 2026, 04:0472-3
24 Aug 2026, 20:1675-2
16 Aug 2026, 17:5777-5
9 Aug 2026, 18:1782no change
8 Aug 2026, 14:5782-1
7 Aug 2026, 19:0383first reading

Engagement

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

Reaction mix

25 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 44.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52741245899983035831144.0%
custom 5273893177160396650728.0%
custom 5357253183796189805520.0%
custom 527373486037089696914.00%
custom 535952515277629596914.00%

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

Measured over the 19 most recent posts we hold, published 28 March 2026 to 16 April 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

16 Apr 2026, 15:14 UTC72 viewsread 9 August 2026

Короче у меня отклеился стикер на котором держался кулер, сейчас я заказал новые, но нашёл временный выход

12 Apr 2026, 05:29 UTC84 viewsread 9 August 2026

Христос Воскресе! Желаю всем хорошего праздника

10 Apr 2026, 16:01 UTC≈1,570 viewsread 9 August 2026
Photo

TDM 13 Апреля в 21:00 по мск Команда 1/1 Призовой фонд 60 UC 1 место 60 ☝️Важно зачисление только 🃏 на аккаунта который участвовал #турнир Нажмите на # турнир чтобы сообщить о участии и отправить 🃏

7 Apr 2026, 19:52 UTC≈1,410 views3 reactionsread 9 August 2026

ℹ️Из-за проблем со связью регионах РФ у некоторых сегодня не работал интернет ⏳поэтому этому турнир буде перенесён на один из следующих дней в опросе ☝️На следующие дни 8,9,10 августа опрос в ТГК по турнирам опрос будет завершён 8 апреля в 00:01 по мск

custom 53572531837961898053

4 Apr 2026, 07:56 UTC≈1,750 views9 reactionsread 9 August 2026
Photo

TDM 7 Апреля в 21:00 по мск Команда 1/1 Призовой фонд 120 UC 1 место 60 2 место 60 ☝️Важно зачисление только 🃏 на аккаунта который участвовал #турнир Нажмите на # турнир чтобы сообщить о участии и отправить свой 🃏 ⏳⏳⏳⏳⏳⏳⏳⏳⏳⏳⏳⏳ Уже сегодня ⏳⏳⏳⏳⏳⏳⏳⏳⏳⏳⏳⏳

custom 52741245899983035835custom 52738931771603966502custom 53572531837961898052

4 Apr 2026, 04:08 UTC≈1,390 views6 reactionsread 9 August 2026

Мне запустить тдм турнир? ✅-да ❌-нет ⏳-можно а зачем

custom 52741245899983035835custom 53595251527762959691

4 Apr 2026, 04:01 UTC≈1,410 views3 reactionsread 9 August 2026

60 UC Участников: 6 Призовых мест: 1 Дата розыгрыша: 12:00, 06.04.2026 MSK (завершён) Победители розыгрыша: 1. Wirtyozzz

custom 52738931771603966503

1 Apr 2026, 09:26 UTC≈1,400 viewsread 9 August 2026

📌Даты Событий и кейсов за Апрельские деньки 03.04➡️Х-Костюмы 08.04➡️Ивент с Фараоном 10.04➡️Рулетка с Питомцами 17.04➡️А18 Bonus Pass 24.04➡️Новый Золото

31 Mar 2026, 18:20 UTC≈1,410 views2 reactionsread 9 August 2026

60 UC Участников: 5 Призовых мест: 1 Дата розыгрыша: 12:00, 02.04.2026 MSK (завершён) Победители розыгрыша: 1. Aza - 599ok9

custom 52738931771603966502

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

“Classic UC Shop” (@UcClassicShop), 61 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/UcClassicShop.

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.