Максимально не удобно вас просить но подпишитесь на блог пожалуйста 👉🏻👈🏻 спасибки заранее
custom 53665510664374968861

Channel
@OnlyMyKimChae
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
171subscribers
+0 since we began measuring on 28 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003723837571 |
|---|---|
| Type | Channel |
| Username | @OnlyMyKimChae |
| Description | love place for Kim Chaewon — best leader 🐯 own — mari/mariia/masha |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/OnlyMyKimChae |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Sept 2026, 04:22 | 171 | no change |
| 28 Sept 2026, 03:47 | 171 | first reading |
13 posts held, back to 27 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 9 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 13 (27 September 2026 – 27 September 2026) |
| Views total | 4,234 |
| Reactions total | 173 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Sept 2026, 04: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 28 September 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.
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.
173 reactions across 9 posts, in 11 distinct kinds. The most used accounts for 19.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5366551066437496886 | 34 | 19.7% | |
| custom 5397754291605776562 | 32 | 18.5% | |
| custom 5454070370942360833 | 30 | 17.3% | |
| custom 5267028960427933486 | 27 | 15.6% | |
| custom 5397643309650848241 | 17 | 9.83% | |
| custom 5451766361506226117 | 10 | 5.78% | |
| custom 5398038339267895822 | 8 | 4.62% | |
| custom 5397778502336424082 | 6 | 3.47% | |
| custom 5397718669147023469 | 5 | 2.89% | |
| custom 5366067191126961913 | 3 | 1.73% | |
| custom 5397794024348231797 | 1 | 0.578% |
Custom emoji. Every row above is a 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 9 of the 13 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 173 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 27 September 2026 to 27 September 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.
Максимально не удобно вас просить но подпишитесь на блог пожалуйста 👉🏻👈🏻 спасибки заранее
custom 53665510664374968861
Доброй всем ночи , спасибо за ваш сегодняшний актив и анон тайм , было безумно приятно с вами общаться 🫶🏻. Если хотите следить за мной более активно заходите в мой блог с рж и в приватку , а также в чат общения , буду рада видеть всех вас там 🤍
custom 53665510664374968866
чат общения от Chae Chae
И не забывайте пожалуйста про реакции , потыкайте отсюда 👉🏻👈🏻
custom 54540703709423608334
ܓ IG Story ⊹ ݁ . 27 . 09
custom 54540703709423608335custom 53977542916057765624custom 53976433096508482413custom 53977785023364240821
tysm 😽🤎
custom 53976433096508482413custom 53977785023364240822custom 53977940243482317971
Буду рада реакциям и вашему мнению в комментариях 😽🫶🏻
Posted without readable text
custom 536655106643749688627custom 539775429160577656215custom 545407037094236083313custom 53660671911269619133custom 53976433096508482413custom 53977186691470234693custom 53977785023364240823
ܓ yena’s bubble ⊹ ݁ . 27 . 09
custom 545176636150622611710custom 54540703709423608338custom 52670289604279334866custom 53976433096508482413custom 53980383392678958222custom 53977186691470234691
hate that i made you love me 𑣲𝄞
custom 539775429160577656213custom 53980383392678958226custom 53976433096508482415custom 52670289604279334864custom 53977186691470234691
https://t.me/OnlyMyKimChae/284?comment=591
Я также создала отдельный аккаунт в Инстаграме и выложила туда видео , помогите пожалуйста тоже продвинуть 🙏🏻 https://www.instagram.com/reel/Ddyfe7cAGR0/?stkn=MjJ5cGMzMTc2amp1
custom 526702896042793348617
Showing the 12 most recent of 13 posts we hold for @OnlyMyKimChae. 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.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“𝜗ৎ𝒞háe ⊹ ࣪ ˖” (@OnlyMyKimChae), 171 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/OnlyMyKimChae.
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.