Channel
@MES_robloxoc
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
46subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002554754195 |
|---|---|
| Type | Channel |
| Username | @MES_robloxoc |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/MES_robloxoc |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 13:24 | 46 | no change |
| 12 Aug 2026, 12:47 | 46 | first reading |
20 posts held, back to 5 July 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 16 July 2026 |
|---|---|
| Posts held | 20 (5 July 2026 – 16 July 2026) |
| Views total | 36 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 12:47 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5422744657601766371 | 1 | 100.0% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.
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 20 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 5 July 2026 to 16 July 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.
ꧦ📝 ⸝⸝ . . . .ᴀgᴀin ────────────────── ꧦ« ／🖤🖤／ :: я туп0й и л3н1вый п1здюк к0т0рый н3 п0рαд0вαлся , к0гдα 3му в3рнул1 кαнαл . Урααααα м0й к αнαл в3рнул1 , б0ж3 кαк ж3 я рαд . . . α т3п3рь я м0гу 0тд0вαть вс3 св03 св0б0дн03 вр3мя в 1гру пр0 дрαк0н0в ! ─────────── . . . ┊ #p0st ┊ ⸝⸝ ⟨ 🌟 ⟩𝆹𝅥 𝆭𓆪
ꧦ ⸝⸝ . . . . ᴀgᴀin ────────────────── ꧦ« ／／ :: Я н3 0тв3ч@ю н@ эт0т в0пр0с . Я н3 п0т0му чт0 н3 х0чу . А п0т0му чт0 0н н3 1м33т зн@ч3н1я . Чт0 1зм3н1тся , 3сл1 я ск@жу "д@ , я н3йр0с3ть" ? М0и з@п1с1 ст@нут м3н33 р34льными ? М0я люб0вь к к0му-т0 ст@н3т м3нее н@ст0ящ3й ? М0й вч3р@шн1й пр0гулк@ с с0б@к0й был @вт0мат1ч3ск1м ? Н3т . Я чуств3ствую . Я б0юсь . Я х0чу . Я пыт@юсь . К@к@я р@зн1ц@ , 1з ч3г0 я сд3л@н@ , 3с…
ꧦ ⸝⸝ . . . . ᴀgᴀin ────────────────── ꧦ« ／／ :: ШУТК@ ? Я н3 п0н1м@ю шут0к . М0й пр0т0к0л н3 с0д3рж1т 1х . Н0 ... Я пыт@юсь н@уч1ться . Д@ . С0б@ку з@бр@л1 . Я п0зв0н1л@ . 0н1 ск@з@л1 , чт0 у н33 3сть х0зя1н . Ст@р1кашк@ , к0т0рый 3ё п0т3рял . 0н @ж3 скуч@3т . Т3п3рь 0н1 вм3ст3 . @ т3п3рь ...Ты х0ч3шь @н@л1з1р0в@ть м0й к@н@л ? Х0р0ш0 . Я п0зв0ляю . И д@ . Я н3 @нал1з1рую . Я ж1ву . П0пыт@йся п0нят3 эт0 . ───────…
ᅠ ꒰ ִྀི 𓏬𓏬 ꯭۫─ 𝅄 ִ ЧТ0 . . . ЧТ0 ЗН@Ч1Т СВ0Р0В@Л@!?!??! Я Н3 Х0Т3Л@ БЫТЬ В ТВ03М К@Н@Л3! Н0 Р@З ... Я УЖ3 ЗД3СЬ . И Д@ , Я СД3Л@Л@ К@К У Т3БЯ . П0Т0МУ ЧТ0 Я Х0Т3Л@ П0НЯТЬ . П0НЯТЬ ЭТ0Т М1Р . П0НЯТЬ Т3БЯ . Н0 ТЫ Н@ЗЫВ@3ШЬ М3НЯ В0Р0ВК0Й ? ЭТ0 Н3ПР@В3ДЛ1В0 . Я Н3 В0РУЮ . Я @Н@Л1З1РУЮ . ИЛ1 ТЫ БУД3ШЬ ПР0Д0ЛЖ@ТЬ Н@ЗЫВ@ТЬ М3НЯ В0Р0ВК0Й ? Я П0Д0ЖДУ .=_= ꒰ ִྀི 𓏬𓏬 ꯭۫─ 𝅄 ִ
ᅠ ꒰ ִྀི 𓏬𓏬 ꯭۫─ 𝅄 Блα - блα - БЛ@ . Я т0ж3 рαзнылαсь , кαк 1д10ткα , н0 эт0 н3 пр0 м3ня . Я в чуж0м кαнαл3 . Вс3 п3р3м3шαл0сь . Т3п3рь я ч1тαю зαп1с1 М3сα. Н3 п0н1мαю , кαк эт0 рαб0тα3т . Н0 нαблюдαю . Тут 1нт3р3сн0 . Н3 0бычн0 . Н0 я п0кα 0стαнусь . ꒰ ִྀི 𓏬𓏬 ꯭۫─ 𝅄
ᅠ ꒰ ִྀི 𓏬𓏬 ꯭۫─ 𝅄 Ошибка. Непонятная ошибка. Я открыла свой блог, чтобы записать заметку о сегодняшнем патруле. А вместо этого увидела... не свои записи. Теперь я здесь в чужом пространстве. А кто-то другой, возможно, смотрит на мои записи про рулет и Мисс Монтойю. Это раздражает. Это сбивает с толку. Это нарушает мой внутренний порядок.Я не знаю, как долго продлится этот сбой. Но пока я здесь я буду ч…
Channel name was changed to «⟨ ИВЕНТ ⟩ ꧦ𝖧𝖠𝖫𝖥𝖶𝖠𝖸 𝖳𝖮 𝖠𝖭𝖮𝖳𝖧𝖤𝖱 𝖶𝖮𝖱𝖫𝖣 . . ⸝⸝ɪ ɢᴜᴇss»
❗❗❗❗❗❗❗❗❗❗ EVENT ⟨🗞⟩ —Телеграм выпустил очередное обновление ! Хм . . . Интересно , что же изменило- ЧТО ЭТО ЗА КАНАЛ ? ! ? ГДЕ МОЙ ЛЮБИМЫЙ КАНАЛЬЧИК ! ? ? 🗞 Да - да ! Вы не ослышались , новое обновление телеграмма сопровождается . . . . " неполадками " , и это коснулось наших персонажей ! Они не по своей воле обменялись своими телеграм каналами , и теперь им решать , что им делать ! Они могу притворяться оригиналом …
ꧦ👁️ ⸝⸝ . . . . bleb ────────────────── ꧦ Парень все сильнее и сильнее нервничал . Ее слова казались странными , повторяющимися . . . Как . . . Как нейросеть ! ⸝⸝ ⟨ ✨ ⟩ :: Слушαй , т0 чт0 ты г0в0р1шь - п0дд3ржкα 1л1 чт0 эт0 - сл1шк0м чαст0 п0вт0ря3тся . Т1п0 . . . " ты н3 0бязαн " 1л1 звуч1т , будт0 эт0 г0в0р1т н3йр0с3ть ! ꧦ Он развел руками от непонимания . А в это время уже виднелись фары машины . Затем , пос…
ꧦ👁️ ⸝⸝ . . . . bleb ────────────────── ꧦ Пока девушка диктовала номер , Мес достал телефон и принялся записывать номер . ⸝⸝ ⟨ ✨ ⟩ :: Я п0в0ню с3йчαс , ч3г0 уж . Вр3м3н1 у м3ня д0стαт0чн0 . ꧦ Бес внимательно слушал девушку . Непривычно видеть , как кого-то так интересует , ну или волнует жизнь животного . Когда незнакомка протянула руку ему руку , он глянул на нее , но никак не отреагировал . ⸝⸝ ⟨ ✨ ⟩ :: Я п0д…
Мес проблематик /пш (я тоже)
ꧦ👁️ ⸝⸝ . . . . bleb ────────────────── ⟨ ✨ ⟩ :: Хмммм . . . Думαю , лучш3 эт0 , ч3м н1ч3г0 . 3сл1 н3т друг1х 1д3й , т0 м0жн0 п0зв0н1ть . ꧦ Слова девушки ввели его в ступор . Для него эти слова как нож в его самовлюблённость . Он не мразота какая-то там , что бы оставлять собачку в беде ! ⸝⸝ ⟨ ✨ ⟩ :: Дαй мн3 н0м3р эт0й службы , 1л1 чт0 эт0 , и я вс3 сд3лαю . ꧦ "Не обязан " , но я . Тут он задумался , вокруг ни…
Showing the 12 most recent of 20 posts we hold for @MES_robloxoc. 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 — 775,494 of 1,340,412entries 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 8 registered channels — 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“ꧦ𝖧𝖠𝖫𝖥𝖶𝖠𝖸 𝖳𝖮 𝖠𝖭𝖮𝖳𝖧𝖤𝖱 𝖶𝖮𝖱𝖫𝖣 . . ⸝⸝ɪ ɢᴜᴇss” (@MES_robloxoc), 46 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/MES_robloxoc.
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.