Channel
@BlissCupid
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
20subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003721859253 |
|---|---|
| Type | Channel |
| Username | @BlissCupid |
| Created | 5 April 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BlissCupid |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 15:16 | 20 | no change |
| 6 Aug 2026, 22:46 | 20 | first reading |
9 posts held, back to 5 April 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 pageof 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 9 posts for this entry, the most recent from 15 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 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.
4 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 50.0% | |
| 👍 | 1 | 25.0% | |
| 😭 | 1 | 25.0% |
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 4 of the 9 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 5 April 2026 to 15 June 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.
#BlissROM #cupid Bliss ROM 19.6 | 16 Waterlily For Xiaomi 12 By Maxim (n0201) Download: View Builds Changelog: ROM Notes: - Gapps not inbuilt Follow 👉🏻 Bliss Official Channel Join 👉🏻 Bliss Support Group Join 👉🏻 Device specific chat
If you look closely at the notes, you'll notice I decided to ship both: gapps and vanilla packages from now on. If you want to change from one to another, a clean flash is recommended and necessary as well. Bliss decided to update the 19.5 tag and thus synced all the latest lineage changes so I was able to squish the time for testing into my little free time (had no issues with the build as the dt has all its require…
#BlissROM #cupid Bliss ROM 19.5 | 16 Waterlily For Xiaomi 12 By Maxim (n0201) Download: View Builds Changelog: ROM Notes: - Available in Google Apps & Vanilla flavours Follow 👉🏻 Bliss Official Channel Join 👉🏻 Bliss Support Group Join 👉🏻 Device specific chat
❤2
#BlissROM #cupid Bliss ROM 19.4 | 16 Waterlily For Xiaomi 12 By Maxim (n0201) Download: View Builds Changelog: ROM Notes: - Gapps not inbuilt Follow 👉🏻 Bliss Official Channel Join 👉🏻 Bliss Support Group Join 👉🏻 Device specific chat
Forgot to mention I've released 19.4 already. Probably shows that I'm a little to stressed to even think about the basic things 😅
Cupid will either receive 19.5 delayed or will even skip it. Because git-lfs is being weird with forks I can't fork the vendor for our device which means that I can't just merge commits up to the date 19.5 released and will always have to be on the latest commit (if I want to build using bliss's build server). Due to me being busy I missed that time window and will probably not be able to find a quick workaround for…
👍1😭1
Updates will follow on this channel. The discussion group will stay linked to it, but I just want to give people the possibility to check updates in a more clean way. So be sure to check out (follow) https://t.me/BlissCupid Let's keep cupid blissful! 🪷
Channel photo updated
Channel created
Showing the 9 most recent of 9 posts we hold for @BlissCupid. 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.
Citation-graph rank — 891,331 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Xiaomi 12 Bliss updates” (@BlissCupid), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/BlissCupid.
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.