Telegram RegisterThe public register of Telegram
Telegram profile photo for ⦙⦙ 𓈒 ʙʟɪꜱꜱ || ɪɴꜰᴏ . ♡゙

Channel

⦙⦙ 𓈒 ʙʟɪꜱꜱ || ɪɴꜰᴏ . ♡゙

@Blissinfo415

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

4subscribers

+0 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004300220293
TypeChannel
Username@Blissinfo415
Created25 June 2026 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live3 October 2026
Measurements held4
Confirmed unchanged3 times, most recently 3 October 2026
On Telegramt.me/Blissinfo415

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 56% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

454.58 August 2026 — 4 subscribers13 August 2026 — 4 subscribers1 September 2026 — 5 subscribers10 September 2026 — 4 subscribers8 August 202610 September 2026
4 measurements spanning 32 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 4–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 04:574-1
1 Sept 2026, 10:365+1
13 Aug 2026, 04:304no change
8 Aug 2026, 21:304first reading

Engagement

2 posts held, back to 25 June 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 2 posts for this entry, the most recent from 26 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

15 reactions across 1 post, in 3 distinct kinds. The most used accounts for 46.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥746.7%
👎746.7%
🍓16.67%

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 1 of the 2 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 15 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 2 most recent posts we hold, published 25 June 2026 to 26 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.

Recent posts

26 Jun 2026, 03:57 UTC240 views15 reactionsread 13 August 2026
Photo

𓏔 ˠ ⏜ ✧ ☆ ✧ ⏜ ˠ 𓏔 ︵ ୨ 🔤𝑒𝑙𝑐𝑜𝑚𝑒 𝑡𝑜 𝑚𝑦 𝐼𝑁𝐹𝑂 ୧ ︵ ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ • He/Him ┏ 𓏔‿⏜ ⏜‿𓏔 ┓ ⏤‌🔤ame: 🔤liss/🔤emphis ⏤‌🔤ge: ⏤🔤irthday: ²⁴.⁰⁸ ┗ 𓏔 𓏔 ┛ 𓏴᳘⥱⁠⁠⁠ ⁠⁠⁠⁝ +7 UTC 4️⃣ . . ⎯⎯ ( ‌𝅄.𝂅ׄ ○꯭𓈓ྀ⃨.︪︩.֪ ֒ ⁠⁠⁠⁠⁠ ᷓ﹚⎯⎯ . . 4️⃣ 🔤𝚞𝚜𝚒𝚌 𝚃𝚊𝚜𝚝𝚎: 🔤𝚛𝚢𝚜𝚝𝚊𝚕 𝙲𝚊𝚜𝚝𝚕𝚎𝚜, 𝙼𝚒𝚝𝚜𝚔𝚒, 𝚂𝚊𝚛𝚊𝚞𝚗𝚑𝟶𝚕𝚢, 𝙿𝚊𝚜𝚝𝚎𝚕 𝙶𝚑𝚘𝚜𝚝, 𝙿𝚞𝚗𝚔𝚒𝚗𝚕𝚘𝚟𝚎𝚎, 𝙾𝙽𝙳𝙰 𝙰𝙽𝙳𝙰𝚁, 𝚍𝟸𝚜𝟷, 𝙼𝚊𝚝𝚝𝚢𝚎𝚞𝚡, 𝙻𝚞𝚖𝚒 𝙰𝚝𝚑𝚎𝚗𝚊, 𝚕𝚘𝚕𝚢 𝚒𝚗 𝚎𝚊𝚛𝚕𝚢 𝟸𝟶𝚜, 𝙼𝙶𝙼𝚃, 𝚛𝚞𝚔𝚒𝚊𝚠𝚊𝚊,…

❤‍🔥7👎7🍓1

Showing the 2 most recent of 2 posts we hold for @Blissinfo415. 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.

Mentions

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.

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.

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 10 September 2026 — this entry's latest reading, not the date you are reading this.

“⦙⦙ 𓈒 ʙʟɪꜱꜱ || ɪɴꜰᴏ . ♡゙” (@Blissinfo415), 4 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/Blissinfo415.

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.