Channel
@StarklyStar
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
352subscribers
+255 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002325928233 |
|---|---|
| Type | Channel |
| Username | @StarklyStar |
| Description | ⏜︵︵⏜︵︵⏜︵ Ⲃⲥя Ⳙⲏⲫⲁ ⲃ ⳅⲁⲕⲣⲉⲡⲉ Ⲗⲥ :: @ryletik_nam ⏜︵︵⏜︵︵⏜︵ |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 10 |
| On Telegram | t.me/StarklyStar |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 the other topics.
@StarklyStar was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 22:22 | 352 | +77 |
| 8 Oct 2026, 02:16 | 275 | +19 |
| 28 Sept 2026, 05:00 | 256 | +49 |
| 11 Sept 2026, 15:56 | 207 | +15 |
| 3 Sept 2026, 00:36 | 192 | +53 |
| 27 Aug 2026, 16:24 | 139 | +34 |
| 14 Aug 2026, 17:48 | 105 | +3 |
| 9 Aug 2026, 10:01 | 102 | no change |
| 8 Aug 2026, 04:20 | 102 | +5 |
| 7 Aug 2026, 08:02 | 97 | first reading |
25 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 2 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 25 (18 July 2026 – 6 November 2026) |
| Views total | 581 |
| Reactions total | 123 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 22:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
491 reactions across 24 posts, in 13 distinct kinds. The most used accounts for 23.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 114 | 23.2% | |
| 🍓 | 83 | 16.9% | |
| 🦄 | 58 | 11.8% | |
| custom 5206669611763794389 | 43 | 8.76% | |
| 💘 | 39 | 7.94% | |
| custom 5206510629254364870 | 31 | 6.31% | |
| custom 5343807578222646159 | 31 | 6.31% | |
| 🌭 | 19 | 3.87% | |
| 💋 | 19 | 3.87% | |
| custom 5294452562836080082 | 18 | 3.67% | |
| 🔥 | 17 | 3.46% | |
| 🥰 | 17 | 3.46% | |
| 🍌 | 2 | 0.407% |
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 24 of the 25 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 491 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 18 July 2026 to 6 November 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.
Telegram’s own ‘edited’ marker: 0 of 5 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🎞️🎞️🟣🌟🌟🌟 🌟🌟🌟🌟🟣🎞️🎞️ 🗝🗝🗝🗝🗝🗝🗝🗝🗝🗝🗝🗝🗝 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 𝄄꛱ 𝄄꛱ — 【✏️нᴇ ɜᴀхᴏᴛᴇᴧᴏᴄь нᴀᴩиᴄᴏʙᴀᴛь ᴋуᴋᴏᴧьнᴏᴇ ᴏɸᴏᴩʍᴧᴇниᴇ дᴧя ᴀдᴏᴨᴛᴏʙ, ᴋᴀᴋ ʙᴀʍ? 🎀】 ุ๋╰꯭▬ׂ────▭๋───▬ׂ ˓𓄹 ࣪˖╮⭐️ 𓏲⭐️ᬄᰱᯮཻུ༅ #арт ₊𓏲 ๋࣭╭ִ╭ִ───────▬ׂ▭๋─╯ ┊┊⏝🌃⏝ 🤩 ┊𖥔 ִֶ ִֶָ — Буду рада реакциям 𖥔𓈒 ִֶָ ° и репостам🤩 ࿙࿚ ࿙࿚ ࿙࿚ ࿙࿚ ࿙࿚ ࿙࿚ ࿙࿚ ࿙࿚ ࿙࿚࿙࿚ ࿙࿚ ࿙࿚ ࿙࿚ ࿙࿚
custom 534380757822264615916custom 520651062925436487010custom 520666961176379438910custom 52944525628360800822
🤩 🤩🤩🤩🤩💛🤩🤩🤩 💕 1—@sirena_auctions 2—@ErisCat3 3—@cat_ts7 4—@Kiss_Touch_Ash 5—@qquyeuq 6—@pidganorka 7—@Nenelinsi 8—@aaCHUmaa 9—@vionnika 10—@Raya_Dragon26arts
custom 520666961176379438913custom 53438075782226461599custom 52944525628360800828
💜💜💜💜💜💜💜💜 ➿➿➿➿➿➿➿➿ 👣🌅🌅🌅🌅🌅🌅🌅🗣 ࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛࿙⃛࿚⃛ 🅰️одписаться на организаторов: 1 @Lokritsyababe 🎊 2 @Vidrator_ebat 3 @Kari_sans 4 @manulwassala 5 @StarklyStar 🌈 6 @Byelshi 🪧Репост поста в тгк ✨ 🪧🪧Кинуть 1-2 арта с юзом канала через @ 🪧 ➿➿➿➿➿➿➿➿➿➿➿➿➿ 🪧ДД до 10 ноября 🍪
custom 52065106292543648707custom 52066696117637943895custom 53438075782226461594
👣
custom 52066696117637943894custom 53438075782226461592
🤩 🤩🤩🤩🤩💛🤩🤩🤩 💕 1—@lifiska 2—@RunarisArt 3—@Mayd_Vortex 4—@shunieart 5—@moxitoj 6—@lotososiska 7—@bread_pikmi 8—@zaporchik228 9—@sapphire_com11 10—@tor7u
custom 520651062925436487014custom 520666961176379438911custom 52944525628360800828
Posted without readable text
🦄7❤2
- новый прайс лист !! 🤩
💘6
- продлеваю рест +- на месяц. у меня сейчас проблемы со здоровьем и с личной жизнью. сил сейчас рисовать нету. посты будут но редко , мне нужно отдохнуть от всего и разобраться со здоровьем.😞 простите
❤19
- спасибо вам за 100 подписчиков 🥰
❤12💘4🔥3🦄1
чібікі 👀
🥰14❤8🦄7💋1
одна из страничек для моего прайс листа готова ^^
🍓10🔥5💋2💘1
напоминаю
🦄5
Showing the 12 most recent of 25 posts we hold for @StarklyStar. 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.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“₊˚⊹ ⋆ 𝐒𝓽𝓪𝓻𝓴𝓵𝔂 ✨𝐒𝒕𝒂𝒓 °｡ ⋆” (@StarklyStar), 352 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/StarklyStar.
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.