Channel
@mysteryb0xx
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002222274916 |
|---|---|
| Type | Channel |
| Username | @mysteryb0xx |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/mysteryb0xx |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 05:18 | 4 | -1 |
| 15 Aug 2026, 15:28 | 5 | +1 |
| 13 Aug 2026, 07:46 | 4 | no change |
| 6 Aug 2026, 22:43 | 4 | first reading |
10 posts held, back to 18 February 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 10 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 1 of the 10 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 18 February 2026 to 10 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.
ᅠ ℭ𝗋𝖺𝗌𝗁 𝗅𝗂𝗌𝗍 🌸 / 𝗴𝗼𝗲𝘀 𝗅𝗂𝗄𝖾 𝗍𝗁𝗂𝗌, 💎 𝕷𝖾𝗉𝗌𝗍𝖾𝖾𝗄 * 🩵 —— в этой папке собраны все мои любимые каналы. те которые меня вдохновляют и мои друзьяшки порядок не имеет значения ! буду рада репостам :)
ᅠ Fix On Officia!+ ( 📂 ) 2026 Crush LLList* 🤩 here LoveUu📞
ᘒ . * 𝗖𝗥𝗨𝗦𝗛𝓛𝗂ѕ𝗍 👠 러헺셔 🩵 ——— в этσй пαпке я собραлα все хелпы u поρты, котоρыми вдохновляюсь, дα u не только, вы все очень клαссные ρебятα , и пραктически со всеми знαкσмα и дружу, вαши ραботы невероятно шикαρные, я всегда сновα и сновα вαми восхищαюсь. Спαсибо вαм зα то, что вы есть 🌟 𓍯𝗦𝗢 𝗖𝗨𝗧𝗘 , 𝗢𝗛 𝗠𝗬 𝗛𝗘𝗔𝗥𝗧
File, posted without a caption
🎀 ’ 𝕸𝘺𝘴𝘵𝘦𝘳𝘺 & 𝙨𝙩𝙪𝘥𝘪𝘰 ! материал авторский, при использовании укажите @psmystery
❤1
𝐶͟r͟ush list ╱ : 🤩 In mყ heɑrt ①'사랑. Dɑnce like rebo͟r͟ռ
ᅠ 💋 นรก „You are MY CRUSH ( !! ) By CN 🥹🥹🥹🥹🥹 ❤️ Tap Here.
{ Ͳhe 𝗖𝗿𝗮𝘀𝗵 𝖫𝗂𝗌𝗍，&꯭987 *🫶사실 } ﹙🩷﹚ – в этой папке я собрала каналы, который меня очень мотивируют ‹3 𝗂 𝗅𝗈𝗏𝖾 𝗎𝗎 &. 運命` t.me/DoubleUport
ᅠ ♡ 재미 —— 𝔐Y 𝗖𝗥𝗨𝗦𝗛 : 𝗟𝘂𝘃 U 𝖬𝖠𝖪𝖤𝖲 𝖴𝖲 𝖲𝖳𝖱𝖮𝖭𝖦 * 💠 This channel’s make me feel happy! Love you all! Keep going and be creative as always!! 𝗕𝗢𝗗𝗬 𝕭ANG 🥹 \ > 𝒯he 𝖡𝖾𝗌𝗍
รักแ💬 &̲ 𝗧𝗪𝗜𝗫 𝔇isp ／ : l𐐫ve 𝘁𝗶𝗺𝗲 龙 ⎯⎯ Очень люблю своих друзей, порты катсуки, Аято, сэхи, катекс и Миланы ⦗ R͏υles ⦘， > 𝗹𝗼𝘃𝗲 messa͟͟g͟͟e
Showing the 10 most recent of 10 posts we hold for @mysteryb0xx. 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.
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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“MYSTERY BOX” (@mysteryb0xx), 4 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/mysteryb0xx.
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.