Channel
@starfall_cos
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
237subscribers
+1 since we began measuring on 3 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001945590231 |
|---|---|
| Type | Channel |
| Username | @starfall_cos |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 October 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/starfall_cos |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 22:38 | 237 | +1 |
| 3 Oct 2026, 19:22 | 236 | no change |
| 3 Oct 2026, 18:47 | 236 | first reading |
17 posts held, back to 25 September 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.
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. It is computed over the 15 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 October 2026 |
|---|---|
| Posts held | 17 (25 September 2026 – 3 October 2026) |
| Views total | 1,762 |
| Reactions total | 198 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Oct 2026, 19: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.
Measured directly from 2 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.
198 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 27.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 55 | 27.8% | |
| custom 5294346047647153545 | 34 | 17.2% | |
| custom 5294313947061581380 | 32 | 16.2% | |
| custom 5294202041688684170 | 25 | 12.6% | |
| ❤🔥 | 18 | 9.09% | |
| custom 5296410135915162971 | 10 | 5.05% | |
| custom 5294157369733839170 | 6 | 3.03% | |
| custom 5294301268318124754 | 6 | 3.03% | |
| 💋 | 6 | 3.03% | |
| 🥰 | 6 | 3.03% |
Custom emoji. 6 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 15 of the 17 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 198 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 25 September 2026 to 3 October 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.
🍨 🍋🍋🍋🍋 🍨 Поймали за поеданием вкусностей... Но нельзя же уволить за это такого милого ушастого официанта?! 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🍨Фотограф - Letta Lo #фотосессии #алиенстейдж #Лука
custom 52943460476471535457custom 52943139470615813804custom 52942020416886841703❤2
Любимая подружка🩷 Боже, этот парик не гофрировался
custom 52964101359151629712❤🔥1custom 52943012683181247541custom 52943139470615813801
Флирт не сработал, поэтому пришлось сделать закос на ее/его любимого персонажа 🙁
❤4💋4custom 52942020416886841703❤🔥1
🤩🤩⭐️⭐️⭐️ ⭐️⭐️⭐️⭐️ 🤩🤩 Бжд-куколка Хун Хун-эра в руках принца - это тоже моя работа. Буду рада, если поделитесь в комментариях своими творческими работами вне косплея😉 🍒🍒🍒🍒🍒🍒🍒🍒🍒🍒🍒🍒 Ph - Letta Lo #фотосессии #благословениенебожителей #СеЛянь
❤🔥9❤8🥰6💋1custom 52942020416886841701
Вы так поддерживаете мои коспланы😠 Это правда очень ценно
custom 52941573697338391703❤2❤🔥2
Ещё одна проблема, я в таких косплеях боюсь показаться смешной. Особенно меня с ботинок выносит, они в жизни редко выглядят нормально...
❤6custom 52943139470615813804custom 52943460476471535454❤🔥1
Я так косо смотрю на этого Шута... Очень хочу закосплеить, знаю, кому предложить коллаб, но, чёрт, времени нет!!! Сейчас в приоритете Столас и малыш Грегори #новости
❤8custom 52943460476471535458custom 52943012683181247545❤🔥1
Скоро-скоро будут новые фотошки, обещаю
custom 52964101359151629715custom 52943139470615813803
Это вот отсюда
Заслужили^^ Сон с шести до восьми того стоил #новости
❤7custom 52943460476471535451
Также к видео будет важное пояснение🦊 Я пришла на меро со штативом, чтобы поснимать для тик ток (в том числе обрывки дефиле), и ко мне подошли с просьбой отснять одну девочку (впоследствии моего спец. призёра). У ребят не было для этого штатива (это цитата) Я сняла красавицу на видео, но, выходя на награждение ко мне, она не подозревала, что в её подарке такой же штатив, который использовала я Эх.. Я люблю дарить …
custom 52943139470615813805custom 52943460476471535454custom 52942020416886841702
До меня дошло видео с награждения🐱 Огромное спасибо за него Эмми Дот И, наверное, надо чаще выходить на сцену, а то есть неуверенность в силу неопытности 🔹 #новости
custom 52943460476471535454custom 52943139470615813803custom 52942020416886841702
Showing the 12 most recent of 17 posts we hold for @starfall_cos. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Какие косплеи ждёте?
The shares total 123%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 17 most recent posts we hold, published 25 September 2026 to 3 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“Создано из звёзд” (@starfall_cos), 237 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/starfall_cos.
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.