Group ˎˊ˗ . About Set. ˖ ࣪ ⊹ 🫧🩵 — ✦ ─── ✦ ─── ✦ ─ Group🏖️ — cover group With a prototype BLACKPINK ✦ Members 🥥˖ ࣪ ⊹ #O4 — jennie, lisa, rose, jisoo 🦩 Social .Network — telegram & tiktok

Channel
🥥 XIELLYN || OI 🏖️
@xiellyncover
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
7subscribers
+0 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003904613490 |
|---|---|
| Type | Channel |
| Username | @xiellyncover |
| Created | Between 1 April 2026 and 11 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 3 times, most recently 8 September 2026 |
| On Telegram | t.me/xiellyncover |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 09:08 | 7 | no change |
| 20 Aug 2026, 23:34 | 7 | first reading |
Engagement
20 posts held, back to 11 May 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 28 May 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
36 reactions across 19 posts, in 10 distinct kinds. The most used accounts for 30.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5251564127519786875 | 11 | 30.6% | |
| custom 5832713661260503687 | 5 | 13.9% | |
| 💘 | 5 | 13.9% | |
| custom 5215693514146342362 | 4 | 11.1% | |
| custom 5938173563851773417 | 3 | 8.33% | |
| custom 5249464240699363300 | 2 | 5.56% | |
| custom 5251745164686283513 | 2 | 5.56% | |
| custom 5298487267998848031 | 2 | 5.56% | |
| custom 5362063083311214432 | 1 | 2.78% | |
| 🐳 | 1 | 2.78% |
Custom emoji. 8 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 19 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 36 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 11 May 2026 to 28 May 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
дякую всім! Навіть якщо ви не попали, не втрачайте надію, і сподіваюсь що скоро будуть набори на тимчасових учасників, тому слідкуйте за новинами 🩵
💘2custom 52156935141463423621custom 52494642406993633001custom 53620630833112144321custom 59381735638517734171
ЛІНН!!!!
💘1
І це….
custom 52515641275197868752
Реакцій…
custom 58327136612605036871
І останній учасник який пройшов…
custom 52984872679988480312
МІРЕЕ!!!!
custom 52156935141463423621custom 52494642406993633001
4 учасник це…
🐳1
ЮМІІ!!!
💘1custom 52517451646862835131custom 59381735638517734171
це…
custom 58327136612605036872
3 учасник —
custom 52515641275197868751
ЮХІ!!!
custom 52515641275197868751
Showing the 12 most recent of 20 posts we hold for @xiellyncover. 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.
Forward network
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“🥥 XIELLYN || OI 🏖️” (@xiellyncover), 7 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/xiellyncover.
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.