Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝖼ꪮtt︩︪ɑgᧉׂ᷒ᰰ ⍴ꪱׅ֡ᧉ 𔓐 ‌᪲

Channel

𝖼ꪮtt︩︪ɑgᧉׂ᷒ᰰ ⍴ꪱׅ֡ᧉ 𔓐 ‌᪲

@starriyiepure

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

312subscribers

-17 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-1003511251236
TypeChannel
Username@starriyiepure
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/starriyiepure

Growth

312333322.57 August 2026 — 329 subscribers8 August 2026 — 329 subscribers16 August 2026 — 333 subscribers23 August 2026 — 328 subscribers30 August 2026 — 322 subscribers8 September 2026 — 316 subscribers15 September 2026 — 312 subscribers7 August 202615 September 2026
7 measurements spanning 39 days, net -17. 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 309–336 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 07:55312-4
8 Sept 2026, 02:22316-6
30 Aug 2026, 22:58322-6
23 Aug 2026, 08:44328-5
16 Aug 2026, 05:58333+4
8 Aug 2026, 07:18329no change
7 Aug 2026, 18:18329first reading

Engagement

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

What this channel posts

Video runtime
14s
Average length
14s

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

134 reactions across 9 posts, in 20 distinct kinds. The most used accounts for 26.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3526.1%
🌭139.70%
🦄128.96%
💘107.46%
🐳85.97%
🍓75.22%
🎄75.22%
💊53.73%
42.99%
❤‍🔥42.99%
🆒42.99%
🍾42.99%
🎉42.99%
👻42.99%
👾32.24%
💯32.24%
🌚21.49%
🎃21.49%
🎅21.49%
10.746%

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

Measured over the 9 most recent posts we hold, published 28 June 2026 to 30 July 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

30 Jul 2026, 13:20 UTC123 views14 reactionsread 8 August 2026
Photo

ㅤׄ 𝓦𝐡ֵ۫𝐚𝐭 𝐰𝐢𝐥𝐥 𝐲𝐨ֵֵ۫۫͟͟𝐮 𝐜𝐡𝐨𐇽𝐨ׅ𝐬𝐞 ? ׄ ㅤׄ 𝐂𝐡𝐨𝐜𝐨𝐥𝐚𝐭𝐞 𝐜𝐚𝐤⃪࡙𝐞 𝐰𝐢𝐭𝐡 𝐬𝐭𝐫𝐚𝐰𝐛𝐞𝐫𝐫𝐢𝐞𝐬 ㅤ࣪ ㅤׄ ㅤׄ 𝐎𐇽𑪍͟𝐑 𝅄 ㅤׄ 𝐒𝐰𝐞𝐞𝐭 𝐯𝐚𝐧𝐢᪾࡙𐇽𝐥𝐥𝐚 𝐜𝐨𝐨𝐤𝐢𝐞𝐬 ᷒᩹ㅤ

7🍓3💘21🐳1

19 Jul 2026, 14:22 UTC290 views18 reactionsread 8 August 2026
Video

━━━── ּ 𓈒 🍄 𓈒 ּ ──━━ ⃘^⃘᳟᪾ ิ‌ 𝒲𝑒𝗹𝗰𝗼𝗺𝝴ׄ 𝘁𝗼 𝗺𝗒 𝗰𝗵𝝰ׄ𝗻𝗻𝝴𝗹 ⃘^⃘᳟᪲ ⊹ 𝓜𝗒 𝗰𝗵𝝰ׄ𝗻𝗻𝝴𝗹 𝗼𝗳𝗳𝝴𝗿𝗌 𝗒𝗼𝘂 𑇒 : 𔓘 𝓒υׁׅ𝘁𝗲ׅ 𝗮ׅ𝗻𝗱‌ 𝕓𝗲ׅ𝗮ׅ𝘂ׄ𝘁𝝸๋𝗳𝕦ׄ𝕝 𝗻𝗮ׅ𝗺𝗲ׅ 𝗱‌𝗲ׅ𝗰ׅ𝗼ׄ𝕣ׅ𝗮ׅ𝘁𝝸๋𝗼ׄ𝗻𝘀 𔓘 𝒱𝗮ׅ𝕣ׅ𝝸๋𝗼ׄ𝘂ׄ𝘀 𝗮ׅ𝗰ׅ𝗰ׅ𝗼ׄ𝘂ׄ𝗻𝘁 𝗳𝗼ׄ𝕣ׅ𝗺𝗮ׅ𝘁𝘀 𝗮ׅ𝕣ׅ𝕣ׅ𝗮ׅ𝗻𝗴ׅ𝗲ׅ𝗱‌ 𝕓𝗒 𝗻𝗮ׅ𝗺𝗲ׅ, 𝗱‌𝗲ׅ𝘀𝗰ׅ𝕣ׅ𝝸๋𝗽𝘁𝝸๋𝗼ׄ𝗻, 𝝸๋𝗺𝗮ׅ𝗴ׅ𝗲ׅ𝘀, 𝗮ׅ𝗻𝗱‌ 𝘀𝗼ׄ𝗻𝗴ׅ𝘀 𔓘 𝒟𝝸๋𝘀𝘁𝝸๋𝗻𝗰ׅ𝘁𝝸๋𝘃‌𝗲ׅ 𝘀𝘆𝗺𝕓𝗼ׄ𝕝𝘀, 𝘀𝗲ׅ𝗽𝗮ׅ𝕣ׅ𝗮ׅ𝘁𝗼ׄ𝕣𝘀, 𝕝𝝸๋𝗻𝗲ׅ𝘀, 𝝸๋𝗺𝗮ׅ𝗴ׅ𝗲ׅ𝘀, 𝗮ׅ𝗻𝗱‌ 𝕝𝗼ׄ𝘁𝘀 𝗼ׄ𝗳 𝘁𝕙𝝸๋𝗻𝗴ׅ𝘀 𝓣𝕠 𝗼ׄ𝕣ׅ𝗱‌𝗲ׅ𝕣ׅ, 𝗰ׅ𝗼ׄ𝗻𝘁𝗮ׅ𝗰ׅ𝘁 𝗺𝗲ׅ 𝘃‌𝝸๋𝗮ׅ 𝘁𝕙𝗲ׅ 𝕓𝗼ׄ𝘁

🌭5🦄4🍓21❤‍🔥1🎄1🎉1👾1

14 Jul 2026, 02:09 UTC363 views16 reactionsread 8 August 2026

ㅤㅤ 🥜 𝖾𝗏𝖾𝗋𝗒 𝗍𝗂𝗆𝖾 𝖨 𝗌𝖾𝖾 𝖸𝗈𝗎 ㅤㅤㅤㅤㅤㅤㅤㅤ𝖨 𝖫𝗈𝗏𝖾 𝖸𝗈𝗎 𝗆𝗈𝗋𝖾 ☕️ㅤㅤㅤㅤㅤㅤㅤㅤ ㅤㅤㅤㅤㅤ◜ℬ𝓎 𝗌𝗁𝗂𝗋𝗈ㅤㅤㅤㅤㅤㅤㅤ ㅤㅤㅤㅤㅤ ㅤ 𐚁 𝗍𝖺𝗉 𝗍𝖺𝗉 𝗍𝗈 𝖲𝖾𝖾 𝗍𝗁𝗂𝗌 𝗉𝗁𝗈𝗍𝗈 𓍯 ㅤ𝖽𝗈𝗇'𝗍 𝖿𝗈𝗋𝗀𝖾𝗍 ㅤ𝗍𝗈 ㅤ𝗀𝗂𝗏𝖾 𝗋𝖾𝖼 ִֶָ ⭒

92💘2🌭1💊1🦄1

13 Jul 2026, 03:51 UTC348 views15 reactionsread 8 August 2026
Photo

𝖡𝗒 𝖲𝗁𝗂𝗋𝘰︩ 𝄒𝄒ㅤ゛𖹭 ⸂ 𝗉𝗂𝗇𝗄︐ 🧊 ⸃ ‌︵⏜𑁥౿ 𝂈 𝗚𝖾𝗍 𝗙𝗂𝗅𝖾𝗌 ٬٬ ☁️𝄶

4🐳3💘2❤‍🔥1🎅1🎉1👻1👾1

10 Jul 2026, 14:26 UTC350 views16 reactionsread 8 August 2026
Photo

𝖡𝗒 𝖲𝗁𝗂𝗋𝘰︩ 𝄒𝄒ㅤ゛𖹭 ⸂ 𝗏𝗂𝗈𝗅𝖾𝗍︐ ☂ ⸃ ‌︵⏜𑁥౿ 𝂈 𝗚𝖾𝗍 𝗙𝗂𝗅𝖾𝗌 ٬٬ ☁️𝄶

🌭53💘2🍓1🎄1🎅1👻1💯1

9 Jul 2026, 03:56 UTC338 views13 reactionsread 8 August 2026
Photo

𝖡𝗒 𝖲𝗁𝗂𝗋𝘰︩ 𝄒𝄒ㅤ゛𖹭 ⸂ 𝖯𝗂𝗇𝗄︐ 🩰 ⸃ ‌︵⏜𑁥౿ 𝂈 𝗚𝖾𝗍 𝗙𝗂𝗅𝖾𝗌 ٬٬ ☁️𝄶

4❤‍🔥2🎃2🍾1🐳1👻1💊1🦄1

1 Jul 2026, 13:18 UTC417 views16 reactionsread 8 August 2026
Photo

ㅤ‌ㅤ‌ʾʿ ‌ ︵ֺ︵ ֺᚐ ݁𝜗𝜚 ݁ ᚐ ׅ ‌ ︵ֺ︵ㅤ‌ʾʿ ㅤ‌𓈒 ˒˓ 𝖩ꫀ᪲𝗅𝗅𝗒𝖼𝖺𝗍𝗌 𓈒 🫐 ಣ ݃ ‌꒱‌ ˒˓ ꉹ 𝖽𝖺𝗋𝗄𝖻𝗅𝗎𝖾⠀ ׂ ۫ ೀ ֹ ㅤ‌ㅤ‌࿚⃜ ࿙ྀི⃜࿚⃜࿙⃜ ࿙❀  ࣪ ࿚⃜࿙ྀི⃜࿚⃜ ࿙⃜ ּ ㅤִꉹ ִ ࣪ #𝑳ɑɖყ_𝖲𝗁𝗂𝗋𝗈𝗒𝖺𝖺𝗇 🍡ᮢ ᷒ᰰ ᜔ֹ ᭡ ㅤ‌ㅤ‌ㅤ‌ㅤ‌ㅤ‌ㅤ‌ㅤ‌⌣⌣

6🆒4💊2🌚1🐳1👾1🦄1

28 Jun 2026, 14:24 UTC436 views14 reactionsread 8 August 2026
File

𓄼 ۫ 🦎ᨩ ׂ 𓈒

🎄5🍾321🌭1🐳1🦄1

28 Jun 2026, 10:24 UTC420 views12 reactionsread 8 August 2026
File

᮫ ݂ ▒⃞𔕬 ׂ

🎉2🦄2🌚1🌭1🍓1🐳1👻1💊1

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

Mentions

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

“𝖼ꪮtt︩︪ɑgᧉׂ᷒ᰰ ⍴ꪱׅ֡ᧉ 𔓐 ‌᪲” (@starriyiepure), 312 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/starriyiepure.

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.