Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝑴𝑨𝑳𝑳𝑰𝑼𝑺

Channel

𝑴𝑨𝑳𝑳𝑰𝑼𝑺

@MALLIUS_virt

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

55subscribers

-5 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003533641209
TypeChannel
Username@MALLIUS_virt
Created18 January 2026measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live9 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/MALLIUS_virt

Growth

556057.514 August 2026 — 60 subscribers15 August 2026 — 60 subscribers23 August 2026 — 59 subscribers30 August 2026 — 58 subscribers9 September 2026 — 55 subscribers14 August 20269 September 2026
5 measurements spanning 26 days, net -5. 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 54–61 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 06:0055-3
30 Aug 2026, 00:0758-1
23 Aug 2026, 15:1759-1
15 Aug 2026, 01:0460no change
14 Aug 2026, 12:4960first reading

Engagement

17 posts held, back to 18 January 2026the 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 17 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

32 reactions across 4 posts, in 12 distinct kinds. The most used accounts for 21.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5438196820356388957721.9%
custom 5190958947812540549412.5%
custom 5474676919653908694412.5%
custom 519537137816910875539.38%
custom 547429231821745430439.38%
custom 519542621631154501526.25%
custom 547206132322535004726.25%
custom 547431977164840975326.25%
custom 547458321205744517426.25%
custom 519040693714082311613.13%
custom 519049324880360367413.13%
custom 519292998990904814113.13%

Custom emoji. Every 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 counts beside them are Telegram’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 4 of the 17 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 18 January 2026 to 31 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.

Recent posts

31 Jul 2026, 07:11 UTC45 viewsread 14 August 2026

(

Signed ❯̸⃟⃟𝐂̷͍𝐑̚𝐈𝐌̷̷̸̎𝐄̷̸ ༒𝐃̷ͧ𝐄̷̰͢𝐕̷͍𝐈̚𝐋

31 Jul 2026, 07:10 UTC45 viewsread 14 August 2026

влд закрывать кф не хочет)

Signed ❯̸⃟⃟𝐂̷͍𝐑̚𝐈𝐌̷̷̸̎𝐄̷̸ ༒𝐃̷ͧ𝐄̷̰͢𝐕̷͍𝐈̚𝐋

31 Jul 2026, 07:10 UTC46 viewsread 14 August 2026

привет

Signed ❯̸⃟⃟𝐂̷͍𝐑̚𝐈𝐌̷̷̸̎𝐄̷̸ ༒𝐃̷ͧ𝐄̷̰͢𝐕̷͍𝐈̚𝐋

15 Jul 2026, 20:10 UTC186 viewsread 14 August 2026

Лан,влд не новый,с основы пацан двигаться решил

Signed Truffle.

12 Jul 2026, 09:14 UTC205 viewsread 14 August 2026

совлд старый (((

Signed ❯̸❯̸𝐅̋𝐀̷̚𝐍͢𝐓̲̍𝐎͢𝐌̲𝐗̷ وهم

12 Jul 2026, 09:13 UTC194 viewsread 14 August 2026

У нас снова перенабор и новый владелец😘

Signed RË1N RĄU55

5 Mar 2026, 17:32 UTC864 views4 reactionsread 14 August 2026
File

для вступления к нам вам нужно: 1. прочитать правила. 2. подписаться на канал. 3. поставить инициалы. 4. подать заявку в чат. ЗАЯВКИ КОПИМ по вопросам обращаться к владельцу или со-владельцу. мы ждём именно тебя у нас.🌟

custom 51904069371408231161custom 51904932488036036741custom 51909589478125405491custom 51929299899090481411

18 Jan 2026, 19:37 UTC964 views12 reactionsread 14 August 2026
Photo

🤩🤩🤩🤩🤩🤩🤩🤩 🌟🌟NAVIGATION • PATENT 🌟• RULES • NORMA🌟 • ADMINISTRATION 🌟🌟🎋 CHAT 🎋 проголосовать за тгк. ⭐⭐⭐⭐⭐⭐⭐⭐ Анон владельца. Напиши что тебя не устраивает в нашем кф или же в администрации,мы это исправим.) всё что приходит в анон — анонимно,не бойся.

custom 54381968203563889573custom 54742923182174543042custom 54746769196539086942custom 51909589478125405491custom 51953713781691087551custom 54720613232253500471custom 54743197716484097531custom 54745832120574451741

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

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.

“𝑴𝑨𝑳𝑳𝑰𝑼𝑺” (@MALLIUS_virt), 55 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/MALLIUS_virt.

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.