Channel
@MJRINFO
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002396211416 |
|---|---|
| Type | Channel |
| Username | @MJRINFO |
| Description | https://t.me/M4LFOYJR |
| Created | 1 February 2025 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/MJRINFO |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 13:30 | 1 | no change |
| 14 Aug 2026, 13:18 | 1 | first reading |
5 posts held, back to 1 February 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 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 5 posts for this entry, the most recent from 6 October 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
ᅠ ᅠᅠ 𝖣𝖱𝖠𝖢𝖮 ᅠ𝖫𝖴𝖢𝖨𝖴𝖲 ᅠ𝖬𝖠𝖫𝖥𝖮𝖸 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ ᅠᅠ𝐖𝐡𝐚𝐭 𝐢𝐟 𝐭𝐡𝐢𝐬 𝐰𝐚𝐬 𝐚𝐥𝐥 𝐣𝐮𝐬𝐭 𝐚 𝐛𝐚𝐝 𝐝𝐫𝐞𝐚𝐦? ᅠᅠ𝐎𝐫 𝐦𝐚𝐲𝐛𝐞 𝐡𝐞 𝐣𝐮𝐬𝐭 𝐰𝐚𝐧𝐭𝐞𝐝 𝐭𝐨 𝐭𝐡𝐢𝐧𝐤 𝐬𝐨. ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ ᅠᅠ— Мы знакомы? — произносит Драко в почти явном недоумении, когда расстояние между ними сокращается до метра. ᅠᅠ— Мы знакомы. ᅠᅠ— Боюсь, Вы меня с кем-то путаете. ᅠᅠ— Мы действительно знакомы, — настойчивость со стороны незнакомца казалась пугающей, — вспомни. ᅠᅠМалфой м…
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ ᅠᅠᅠᅠᅠ ВЗАИМНЫЙ ПИАР ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ • ВП 0+ • без подписки • держу 1 час • сразу отправляйте шаблон Шаблоны, содержащие в себе материалы вызывающего характера [NC-17,21] не принимаются. ᅠᅠСвязь: @mlfyjrbot
ᅠ ᅠ𝕮𝐎𝐍𝐍𝐄𝐂𝐓 𝐋𝐈𝐒𝐓 :: 𝖳𝖧𝖤𝖮𝖣𝖮𝖱𝖤 𝖭𝖮𝖳𝖳 ᅠᅠБронь: Пэнси
ᅠᅠᅠУСЛОВИЯ ДЛЯ ЗАКЛЮЧЕНИЯ КОННЕКТА: ᅠᅠ— Ваш персонаж должен быть из вселенной Гарри Поттера; ᅠᅠ— Взаимная подписка и активность (реакции, репосты комментарии, посты); ᅠᅠ— Ваш персонаж — канон или ОП с хорошей анкетой/раскрытием в постах; ᅠᅠ— Я буду единственным Драко в Вашем коннект-листе. ᅠᅠОбщение в личных приветствуется. Я не заключаю коннект ради коннекта, хочу видеть отдачу и взаимодействия. От себя могу пообещ…
Channel created
Showing the 5 most recent of 5 posts we hold for @MJRINFO. 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 — 903,273 of 1,478,351entries 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“info” (@MJRINFO), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/MJRINFO.
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.