Telegram RegisterThe public register of Telegram
Telegram profile photo for ⋮ ⌗ ┆ 𝐄𝐮𝐰𝐫𝐢𝐤𝐚𝐧𝐚 𝐜𝐨𝐬𝐩𝐥𝐚𝐲. ୭ ˚. ᵎᵎ

Channel

⋮ ⌗ ┆ 𝐄𝐮𝐰𝐫𝐢𝐤𝐚𝐧𝐚 𝐜𝐨𝐬𝐩𝐥𝐚𝐲. ୭ ˚. ᵎᵎ

@EuwrikanaCosp

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

65subscribers

+2 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002791649281
TypeChannel
Username@EuwrikanaCosp
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live19 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/EuwrikanaCosp

Growth

626563.59 August 2026 — 63 subscribers10 August 2026 — 63 subscribers16 August 2026 — 64 subscribers23 August 2026 — 63 subscribers31 August 2026 — 62 subscribers10 September 2026 — 64 subscribers19 September 2026 — 65 subscribers9 August 202619 September 2026
7 measurements spanning 41 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 62–65 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 14:4265+1
10 Sept 2026, 13:0164+2
31 Aug 2026, 14:3362-1
23 Aug 2026, 15:5563-1
16 Aug 2026, 03:3464+1
10 Aug 2026, 03:4563no change
9 Aug 2026, 05:1763first reading

Engagement

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

What this channel posts

Video runtime
12s
Average length
12s

Measured directly from 1 video 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

91 reactions across 13 posts, in 9 distinct kinds. The most used accounts for 20.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 51973436013816445341920.9%
👀1819.8%
custom 51950537481577024051415.4%
custom 54450074015372625521112.1%
custom 529625585639492395377.69%
custom 533227822384785515666.59%
custom 537737488223964413766.59%
custom 547011420839164831166.59%
custom 524675111415345661044.40%

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

Measured over the 14 most recent posts we hold, published 18 July 2026 to 8 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

8 Aug 2026, 09:15 UTC25 views4 reactionsread 10 August 2026
Forwarded from @goMOVEchannelPhoto

Мы уже на ЮнаПати!🌟🌟

custom 51950537481577024051custom 51973436013816445341custom 52962558563949239531custom 54450074015372625521

7 Aug 2026, 20:38 UTC35 views6 reactionsread 10 August 2026

Posted without readable text

custom 51973436013816445342custom 52467511141534566101custom 52962558563949239531custom 53322782238478551561custom 53773748822396441371

6 Aug 2026, 09:42 UTC43 views4 reactionsread 10 August 2026
Sticker

Sticker, posted without a caption

custom 54701142083916483112custom 51950537481577024051custom 51973436013816445341

6 Aug 2026, 09:42 UTC36 views4 reactionsread 10 August 2026
Forwarded from @goMOVEchannelPhoto

🤩🤩🤩 //🎀nons на ЮнаПати!//🌟🌟 🌟🌟 — 🔤умаю в такой прекрасный день нам нужно сказать такую же новость. ✨✨✨ 🤩🤩 — 🔤очно! Новость у нас и вправду великолепная! 🤩🤩🤩 go Move! Будут присутствовать на ЮнаПати от начала и до конца. Будет ходить в Руи и Цукасе в официальном стиле. Будем важными бумажными. Будем рады пофоткаться и пообщаться! 🎈⭐

custom 51950537481577024052custom 51973436013816445341custom 54450074015372625521

31 Jul 2026, 21:21 UTC78 views9 reactionsread 10 August 2026

Косплеев не будет, меня раздавили 🌟

custom 51973436013816445343custom 52962558563949239533custom 51950537481577024051custom 53322782238478551561custom 53773748822396441371

31 Jul 2026, 21:20 UTC73 views8 reactionsread 10 August 2026
Forwarded from @kyrineperekyriPhoto

Всем привет, сегодня был на концерте

👀2custom 52467511141534566102custom 52962558563949239532custom 53773748822396441372

26 Jul 2026, 07:08 UTC104 views11 reactionsread 10 August 2026
Photo

Мы уже выдвинулись!

custom 51950537481577024057custom 54450074015372625522custom 54701142083916483112

24 Jul 2026, 18:48 UTC93 views7 reactionsread 10 August 2026

UPD UPD с нами будет Коленька! 🌟

custom 51973436013816445343custom 53322782238478551562custom 54450074015372625522

23 Jul 2026, 21:20 UTC107 views4 reactionsread 10 August 2026
Sticker

Sticker, posted without a caption

custom 54701142083916483112custom 51973436013816445341custom 54450074015372625521

23 Jul 2026, 20:38 UTC106 views9 reactionsread 10 August 2026

UPD Мы выступаем шестыми в третьем блоке! 🌟🌟

custom 51973436013816445344custom 54450074015372625522custom 51950537481577024051custom 53322782238478551561custom 53773748822396441371

22 Jul 2026, 20:53 UTC133 views14 reactionsread 10 August 2026
Photo

🌟👑🌟👑🌟👑🌟👑🌟👑🌟👑 🎀nons! 🎀aiii!! Буду присутствовать на Хоккайдо! 🌟 Будем выступать вместе с Вишей в Эму и Руи под номером ?? 🌟 Буду очень рада пообщаться и пофоткаться, всех люблю, увидимся! 🌟 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 Вк: @hokkaido_spb Тгк: @hokkaidofest

👀5custom 51973436013816445343custom 54450074015372625522custom 51950537481577024051custom 52467511141534566101custom 53322782238478551561custom 53773748822396441371

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“⋮ ⌗ ┆ 𝐄𝐮𝐰𝐫𝐢𝐤𝐚𝐧𝐚 𝐜𝐨𝐬𝐩𝐥𝐚𝐲. ୭ ˚. ᵎᵎ” (@EuwrikanaCosp), 65 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/EuwrikanaCosp.

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.