─────𝗚𝗘𝗡𝗦𝗛𝗜𝗡 𝗜𝗠𝗣𝗔𝗖𝗧──────🔥 Рᴏᴧи ─────‼️ (💤 - занято) Мᴏндɯᴛᴀᴛ ───── ✨ А᧘ьδᥱд᧐ Бᥲρδᥲρᥲ Бᥱннᥱᴛ Вᥱнᴛᥙ Дᥙ᧐нᥲ Дᥙ᧘юκ Джᥙнн 𐌺ᥱᥔя 𐌺᧘ᥙ 𐌡ᥙᤋᥲ 𐌑ᥙκᥲ 𐌑᧐нᥲ 𐋏᧐϶᧘᧘ь Р᧐ᤋᥲρᥙя Рᥱᥔᤋ᧐ρ 𑀝ᥲ᥊ᥲρ᧐ᤋᥲ Фᥙɯ᧘ь Э᧐᧘ᥲ Эⲙδᥱρ ᴧи ю϶ ─────✨ Бᥲᥔ Կжу Бᥱᥔ Д᧐у 𐌲ᥲнь Юᥔ Е 𐌡ᥲнь 𐌺ᥲ ⲙᥙн 𐌺ᥱ цᥙн 𐌡ᥲнь Янь 𐋏ᥙн 𐌲уᥲн 𑀝ᥙн Цю 𑀝ᥙнь Янь 𑀝ян 𐌡ᥙн 𑀝янь Юᥔ 𑀝я᧐ 𐌗у Тᥲ᧐ Цᥙ цᥙ Կжун 𐌡ᥙ Կунь Юнь Ш϶нь 𐌗϶ Юнь Цᤋᥙнь Янь Ф϶ᥔ Я᧐ Я᧐ Инᴀдɜуʍᴀ ─────✨ Аяᴛ᧐ Аяκᥲ 𐌲᧐ρ᧐ Еᥔⲙᥙя Иᴛᴛ᧐ 𐌺ᥲдᤋу᥊ᥲ …

Channel
PANDORA|INFO
@pandorainfokn
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1subscribers
-1 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002690432798 |
|---|---|
| Type | Channel |
| Username | @pandorainfokn |
| Created | 15 April 2025 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/pandorainfokn |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 21:39 | 1 | -1 |
| 14 Aug 2026, 06:45 | 2 | no change |
| 11 Aug 2026, 15:17 | 2 | first reading |
Engagement
5 posts held, back to 15 April 2025 — 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 5 posts for this entry, the most recent from 16 May 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
💙𝗗𝗠𝗜𝗡𝗜𝗦𝗧𝗥𝗔𝗧𝗜𝗢𝗡────╮ ────────╯ Иᴄᴨыᴛᴀᴛᴇᴧьный ᴄᴩᴏᴋ- ⏰ Рᴇᴄᴛ - 👎 ╰────────ᯓ 🚨 "Вᴧᴀдᴇᴧᴇц ᴏᴛʙᴇчᴀᴇᴛ ɜᴀ ʙᴄᴇ ʙᴏᴨᴩᴏᴄы"ᯓ ╰─────🔡🔡🔡 ──────╮ ✅𝗟𝗬𝗡𝗘𝗬🎸ᯓ ╭ @LegimenTos [𝗠𝗔𝗗𝗟𝗘𝗡-𝗛𝗘/𝗛𝗜𝗠]/мск. │ ╰──────Вᴇдᴇниᴇ ᴛиᴋ-ᴛᴏᴋ ᴀᴋᴋᴀунᴛᴀ, ᴏɸᴏᴩʍᴧᴇниᴇ, нᴀбᴏᴩᴏʍ ʙᴏ ɸᴧуд, чиᴄᴛᴋи и ᴩᴇᴄᴛиᴋи. ✅𝗥𝗔𝗜𝗗𝗘𝗡👤ᯓ ╭ @Hitamaru69 [𝗛𝗜𝗧𝗔𝗠𝗔𝗥𝗨-𝗦𝗛𝗘/𝗛𝗘𝗥]/мск. │ ╰──────ʙᴇдᴇниᴇ инɸᴏ ᴋᴀнᴀᴧᴀ, чиᴄᴛᴋи и ᴩᴇᴄᴛиᴋи. ✅𝗖𝗛𝗔𝗦𝗞𝗔👤ᯓ ╭ @natth666[𝗖𝗛𝗠𝗢-𝗦𝗛𝗘/𝗛𝗘𝗥]/мск. …
╭─────────𝗥𝗨𝗟𝗘𝗦───────‼️ │ ╰──────ЗА𐌿РЕЩЕ𐋏𐌏ᯓ •🔗ᯓᴏᴄᴋᴏᴩбᴧᴇния, ᴩᴀɜᴦᴏʙᴏᴩы ᴏ ᴨᴏᴧиᴛиᴋᴇ, ᴋᴏнɸᴧиᴋᴛы ʙᴏ ɸᴧудᴇ, ᴏᴄᴋᴏᴩбᴧᴇниᴇ нᴀциᴏнᴀᴧьнᴏᴄᴛи и ᴏᴩᴇинᴛᴀции ᴋᴀᴩᴀᴇᴛᴄя 𝘃𝗮𝗿𝗻𝗼𝗺, ɜᴀᴛᴇʍ ʙыдᴀёᴛᴄя 𝗯𝗮𝗻 •🔗ᯓᴏᴛᴨᴩᴀʙᴧᴇниᴇ ᴄᴄыᴧᴏᴋ ᴄ нᴇиɜʙᴇᴄᴛных иᴄᴛᴏчниᴋᴏʙ, ᴨиᴀᴩ ᴄʙᴏих ᴦᴩуᴨᴨ/ɸᴧудᴏʙ/ᴩᴏᴧᴇʙых/ᴋᴀнᴀᴧᴏʙ, ᴄᴩᴀɜу 𝗯𝗮𝗻 •🔗ᯓᴨᴇᴩᴇхᴏды нᴀ ᴧичнᴏᴄᴛь, ᴏᴄᴋᴏᴩбᴧᴇниᴇ ᴩᴏдиᴛᴇᴧᴇй иᴧи жᴇ ᴩᴏдᴄᴛʙᴇнниᴋᴏʙ учᴀᴄᴛниᴋᴀ, ᴨᴏᴧучᴀᴇᴛᴇ 𝘃𝗮𝗿𝗻 •🔗ᯓʙидᴇᴏ/ ɸᴏᴛᴏ/ ᴦиɸ ᴄᴏдᴇᴩжᴀщиᴇ 18+ ᴋᴏнᴛᴇнᴛ ᴄᴛᴩᴏᴦ…
𝅄𓈒݂۫⃝━݂۫━݂۫━݂۫╼━─━𝗡𝗔𝗩𝗜𝗚𝗔𝗧𝗜𝗢𝗡 ╰۫┄𞥊☨⏜◦₊ ִֶָ۫ ᩠♱ ִֶָ۫ ₊◦︵•☨ ࣪˖ ┊┊┊⋆𖥔 ִֶָ ° • ┊┊ ุ๋.𝅄✦𓈒 ࣪˖ ִֶָ ۫ ┊𖥔 ִֶָ ⭒ ° ┊ ࣪˖ ִֶָ ۫ ✦𓈒 ִֶָ ° ╰┈➤ 𝙜𝙡. 𝙞𝙣𝙛𝙤𝙧𝙢𝙖𝙩𝙨𝙞𝙮𝙖 ㅤㅤㅤㅤㅤㅤ~●○°●○°●○~ ╭───────────────╯ │ │ㅤ──●ᥰρᥲʙᥙ᧘ᥲ. │ │ㅤ──●ᥴᥰᥙᥴ᧐κ ᥰᥱρᥴ᧐нᥲжᥱᥔ. │ │ㅤ──●ᥲдⲙᥙнᥙᥴᴛρᥲцᥙя. │ ╰────────────────╮ ू ₒ ु ˚ 𝙙𝙤𝙥. 𝙞𝙣𝙛𝙤𝙧𝙢𝙖𝙩𝙨𝙞𝙮𝙖 ㅤㅤㅤㅤㅤㅤㅤ~●○°●○°●○~ ╭────────────────╯ │ │ㅤ──●ᴛᥙκ ᴛ᧐κ. │ │ㅤ──●ᥲн᧐н ᥲдⲙᥙнᥙᥴᴛρᥲцᥙᥙ. │ ╰───────────…
Channel created
Showing the 5 most recent of 5 posts we hold for @pandorainfokn. 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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@pandorainfokn named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 15 August 2026 – 15 August 2026
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“PANDORA|INFO” (@pandorainfokn), 1 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/pandorainfokn.
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.