Channel
@bluekiss_oi
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
57subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002434709758 |
|---|---|
| Type | Channel |
| Username | @bluekiss_oi |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/bluekiss_oi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 09:37 | 57 | -1 |
| 25 Aug 2026, 14:53 | 58 | -1 |
| 18 Aug 2026, 11:13 | 59 | +2 |
| 12 Aug 2026, 07:02 | 57 | no change |
| 12 Aug 2026, 01:31 | 57 | first reading |
20 posts held, back to 3 August 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 20 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 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.
14 reactions across 3 posts, in 7 distinct kinds. The most used accounts for 21.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5318841929763407948 | 3 | 21.4% | |
| custom 5393364332518074395 | 3 | 21.4% | |
| custom 5215655134318587386 | 2 | 14.3% | |
| custom 5301165558065022966 | 2 | 14.3% | |
| custom 5407088367936494393 | 2 | 14.3% | |
| custom 5217429780445552034 | 1 | 7.14% | |
| custom 5325585011238259513 | 1 | 7.14% |
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 3 of the 20 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 3 August 2026 to 11 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.
Почему оформление иишное лень ручками слелать🥺🙏 Это убого они не похожи даже на себя блять. Хочу раз и навсегда развеять этот миф. Я не отрицаю тспользование ии, НО... Оно использовано для вырезки фона у участниц Nmixx, потому что другие редакторы НЕ распознавали, где фон, а где люди. Всё
Sticker, posted without a caption
Такс, коммы ей пишем, видео плохо продвигается, активнее)
# 🩵 *🤍luekiss⁶ [ 🎁 ] 🎀 🌟 “ 🎀ew 🎀ractice𓍯 ➿➿ ➿➿➿ ➿➿ : · : 😱 You always be my blue valentine 🤩 ＊. 🎀 ° ➖rue NMIXX 💦 ▫️ NMIXX we get it on now 🤩 ゞ. By Juelin - Shine ➿➿ ➿➿➿ ➿➿ ™️ Tt ⸝ @bluekiss_group ✈️ Tg ⸝⸝⸝ @bluekiss_oi ▫️
custom 53188419297634079482custom 52156551343185873861custom 53011655580650229661custom 53255850112382595131custom 53933643325180743951custom 54070883679364943931
Sticker, posted without a caption
Продвигаем нашу Джулин)
# 🩵. * 🤍luekiss⁶ [ .🎁 ] 🎀 🌟 “ 🎀ew 🎀ideo𓍯 ➿➿ ➿➿➿ ➿➿ : · : 😱 You always be my blue valentine 🤩 ＊. 🎀 ° ➖rue NMIXX 💦 ▫️ NMIXX we get it on now 🤩 ゞ. тыкни чтобы посмотреть ➿➿ ➿➿➿ ➿➿ ™️ Tt ⸝ @bluekiss_group ✈️ Tg ⸝⸝⸝ @bluekiss_oi ▫️
custom 52156551343185873861custom 52174297804455520341custom 53011655580650229661custom 53188419297634079481custom 53933643325180743951custom 54070883679364943931
Sticker, posted without a caption
# 🩵. * 🤍luekiss⁶ [ .🎁 ] 🎀 🌟 “ 🎀ew 🎀ideo𓍯 ➿➿ ➿➿➿ ➿➿ : · : 😱 You always be my blue valentine 🤩 ＊. 🎀 ° ➖rue NMIXX 💦 ▫️ NMIXX we get it on now 🤩 ゞ. тыкни чтобы посмотреть ➿➿ ➿➿➿ ➿➿ ™️ Tt ⸝ @bluekiss_group ✈️ Tg ⸝⸝⸝ @bluekiss_oi ▫️
Sticker, posted without a caption
Продвигаем нашу Каиши)
custom 53933643325180743951
# 🩵. * 🤍luekiss⁶ [ .🎁 ] 🎀 🌟 “ 🎀ew 🎀ideo𓍯 ➿➿ ➿➿➿ ➿➿ : · : 😱 You always be my blue valentine 🤩 ＊. 🎀 ° ➖rue NMIXX 💦 ▫️ NMIXX we get it on now 🤩 ゞ. тыкни чтобы посмотреть ➿➿ ➿➿➿ ➿➿ ™️ Tt ⸝ @bluekiss_group ✈️ Tg ⸝⸝⸝ @bluekiss_oi ▫️
Showing the 12 most recent of 20 posts we hold for @bluekiss_oi. 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 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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“🂱 𝗕𝗟𝗨𝗘𝗞𝗜𝗦𝗦|𝗢𝗜 𝗚𝗥𝗢𝗨𝗣 🂱” (@bluekiss_oi), 57 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/bluekiss_oi.
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.