Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝑆ℎ𝑢𝑛𝑐ℎ𝑎𝑘𝑖... 🍃

Channel

𝑆ℎ𝑢𝑛𝑐ℎ𝑎𝑘𝑖... 🍃

@Shunchaki_prosto_tak

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

31subscribers

+1 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1002705128606
TypeChannel
Username@Shunchaki_prosto_tak
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live3 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/Shunchaki_prosto_tak

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 30 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

283129.514 August 2026 — 30 subscribers15 August 2026 — 30 subscribers30 August 2026 — 28 subscribers18 September 2026 — 29 subscribers3 October 2026 — 31 subscribers14 August 20263 October 2026
5 measurements spanning 50 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 28–31 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 23:0231+2
18 Sept 2026, 06:1929+1
30 Aug 2026, 09:4428-2
15 Aug 2026, 09:4830no change
14 Aug 2026, 14:4630first reading

Engagement

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

What this channel posts

Video runtime
5m 21s
Average length
36s

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

34 reactions across 14 posts, in 5 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 5332798632150196717514.7%
custom 533473816207165801938.82%
custom 544943727375602599238.82%
custom 544971469428360817838.82%

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 14 of the 20 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 20 most recent posts we hold, published 30 May 2026 to 3 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

3 Aug 2026, 18:53 UTC11 views2 reactionsread 14 August 2026

дунëда шундай тотли не'матлар бор сиз килган таом шу не'матлар ичида енг тотлисидур 🤍

🕊1custom 53327986321501967171

25 Jul 2026, 23:04 UTC20 views3 reactionsread 14 August 2026
Video

😁😆😁🦦🌥

🕊1custom 53327986321501967171custom 54494372737560259921

25 Jul 2026, 22:57 UTC18 views3 reactionsread 14 August 2026
Photo

келила😋

🕊1custom 53327986321501967171custom 54494372737560259921

25 Jul 2026, 22:55 UTC16 views3 reactionsread 14 August 2026
Photo

😍

🕊1custom 53327986321501967171custom 54494372737560259921

13 Jul 2026, 03:17 UTC29 views2 reactionsread 14 August 2026

Мен тугилдим😂

custom 53347381620716580192

10 Jul 2026, 19:10 UTC31 views3 reactionsread 14 August 2026
Video

Биринчи марта ош килдим 😅

🕊1custom 53327986321501967171custom 53347381620716580191

14 Jun 2026, 14:56 UTC59 views4 reactionsread 14 August 2026

إن أعظم الخسارة في خسارة الجنة، وأما الناس فإنهم بأنون ويذهبون. Eng katta yo'qotish Jannatni yo'qotishdir va odamlarga kelsak, ular kelib-ketadilar...

🕊2custom 54497146942836081782

12 Jun 2026, 00:40 UTC80 viewsread 14 August 2026

Ехтимол чарчадим ëрук дунëдан Ехтимол хаваслар умримни еди. Кочада кулганча колин берганлар Ортимдан "Бу одам болмайди" деди...

12 Jun 2026, 00:35 UTC76 viewsread 14 August 2026

Кимгадир ачиниш керак болса Факат оз иймонимга ачиндим Тилда бору амалда ëк Жасадимга ачиндим...

Showing the 12 most recent of 20 posts we hold for @Shunchaki_prosto_tak. 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.

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 3 October 2026 — this entry's latest reading, not the date you are reading this.

“𝑆ℎ𝑢𝑛𝑐ℎ𝑎𝑘𝑖... 🍃” (@Shunchaki_prosto_tak), 31 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/Shunchaki_prosto_tak.

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.