Telegram RegisterThe public register of Telegram
Telegram profile photo for ⻩ ׅ ͝ ͜ 𝓪ᥣׁׅ֪𝐬𝐭𝐫𝕺 ֹ 𝓮ꩇׁׅ֪݊𝐞𝐫𝐢𝕬 ⁱⁿᶠᵒ ۶♡⃘ ׅ

Channel

⻩ ׅ ͝ ͜ 𝓪ᥣׁׅ֪𝐬𝐭𝐫𝕺 ֹ 𝓮ꩇׁׅ֪݊𝐞𝐫𝐢𝕬 ⁱⁿᶠᵒ ۶♡⃘ ׅ

@MERIA_inf

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

72subscribers

+8 since we began measuring on 14 September 2026

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

Register entry

Telegram ID-1003968456668
TypeChannel
Username@MERIA_inf
Created8 September 2026measured — dated from the channel’s first post
First recorded14 September 2026
Last confirmed live15 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/MERIA_inf

Growth

64726814 Sept 2026, 10:47 — 64 subscribers14 Sept 2026, 11:22 — 64 subscribers15 Sept 2026, 17:37 — 72 subscribers14 Sept 2026, 10:4715 Sept 2026, 17:37
3 measurements spanning 1 day, net +8. 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 63–73 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 17:3772+8
14 Sept 2026, 11:2264no change
14 Sept 2026, 10:4764first reading

Engagement

18 posts held, back to 8 September 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.

ERR · 30 days
123.8%
avg views ÷ 72 subscribers
Avg views / post
89.1
16 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
18
of 18 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 September 2026
Posts held18 (8 September 202612 September 2026)
Views total1,426
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Sept 2026, 11:22 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.

Recent posts

12 Sept 2026, 06:43 UTCviews —

Channel name was changed to «⻩ ׅ ͝ ͜ 𝓪ᥣׁׅ֪𝐬𝐭𝐫𝕺 ֹ 𝓮ꩇׁׅ֪݊𝐞𝐫𝐢𝕬 ⁱⁿᶠᵒ ۶♡⃘ ׅ»

8 Sept 2026, 13:31 UTC150 viewsread 14 September 2026
Photo

— ⁠⁠⁠♡𝑅𝐸𝑆𝑇𝑆.ᐟ🐾🐾 🤩рест🔤временный отдых от активности во флуде🔤 🤩🤩максимальный срок реста в нашем флуде ➖ 🤩 месяца🔤 если у вас серьезная причина🔤то мы можем выдать рест на более долгий срок🔤 по окончанию реста у вас есть неделя набрать норму🔤 🦷 после окончания реста🔤взять следующий можно будет только через 🤩недели➖🌺 ☺️апрещено брать рест за 🤩дня до чистки 🔤 ✍️ по поводу реста писать🔤тыктык.

8 Sept 2026, 13:30 UTC139 viewsread 14 September 2026
Photo

᜔ ֹ ◯⃘ ۪ 𝐼𝑁𝐼𝑇𝐼𝐴𝐿𝑆🎀 ᯏ ˙⚫️тавить его в имя не является обязательным🔤 ⚫️то делается по желанию➖ 🐱⚫️нициал нашего флуда🔤 #MERIA #ASM #ALM 🤩🤩 🏳 .`𝔄𝐿𝐒ℑ𝑅𝙊𝘌𝐌𝐸𝙍𝐼𝔄:;🏳 🤩🤩 你给 𓈒ִ нажмите хэштег чтобы поставить в имя ^_<

8 Sept 2026, 13:30 UTC84 viewsread 14 September 2026
Photo

⃟ 𝐴𝐷𝑀𝐼𝑁𝐼𝑆𝑇𝑅𝐴𝑇𝐼𝑂𝑁𓏼🥰 ྀ֯ . . если у вас есть вопросы или жалобы по поводу флуда ִ вы всегда можете написать их админам ! ! ⏜⏜ 𓈒 𑄻𑄾 владелец😻 🤩/🤍/ +0 к МСК /🤩/ обязанности🔤добавление участников ִ выдача тегов ִ инфо канал ִ смены ролей ִ слежка за соблюдением правил ִ проведение чисток ִ тт ִ ⏜⏜ 𓈒 𑄻𑄾 совладелец🔤 обязанности🔤добавление участников ִ выдача тегов ִ инфо канал ִ смены рол

8 Sept 2026, 13:30 UTC62 viewsread 14 September 2026
Photo

᜔ ֹ ◯⃘ ۪ 𝐶𝐿𝐸𝐴𝑁𝐼𝑁𝐺ㅤㅤㅤㅤ͝ ⏝⁠⁠⁠⁠ 🐱 🦷 | ⚫️орма в нашем флуде составляет 🤩🤩🤩 сообщений в неделю🔤⚫️сли вы не наберете данное количество сообщений вам без предупреждения выдадут бан на чистке 🔤 чистка проводится по субботам🔤🌸 ⚫️частников которые находятся во флуде менее 🤩 дней чистка не касается🔤😊 если у вас не получается набрать норму?попросите помощи у админов🔤мы всегда рады помочь влиться➖

8 Sept 2026, 13:25 UTC68 viewsread 14 September 2026
Photo

ꫂ ⢄𝐹𝑂𝑅𝑀 !݁ ˎ 💭💭💭💭💭 ⚫️ нкета требуется для быстрого анализа заявки🔤просто отправьте ее🔤и если вы подойдете🔤то в скором времени получите ссылку на чатик🔤 🔤? 💭💭💭💭💭💭💭💭💭💭 ⚫️ нкеты строго по шаблону скидывать сюда 🤩 〽️〽️〽️ ☪️

Showing the 12 most recent of 18 posts we hold for @MERIA_inf. 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 10 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.

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 15 September 2026 — this entry's latest reading, not the date you are reading this.

“⻩ ׅ ͝ ͜ 𝓪ᥣׁׅ֪𝐬𝐭𝐫𝕺 ֹ 𝓮ꩇׁׅ֪݊𝐞𝐫𝐢𝕬 ⁱⁿᶠᵒ ۶♡⃘ ׅ” (@MERIA_inf), 72 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/MERIA_inf.

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.