Telegram RegisterThe public register of Telegram

Channel

мунри шопᅠ

@munrishop

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

568subscribers

+14 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003840890276
TypeChannel
Username@munrishop
CreatedBetween 1 February 2026 and 18 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/munrishop

Growth

5545685616 Aug 2026, 12:04 — 554 subscribers6 Aug 2026, 18:17 — 554 subscribers7 Aug 2026, 01:34 — 568 subscribers6 Aug 2026, 12:047 Aug 2026, 01:34
3 measurements taken within a single day, net +14. 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 552–570 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 01:34568+14
6 Aug 2026, 18:17554no change
6 Aug 2026, 12:04554first reading

Engagement

18 posts held, back to 18 May 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
97.3%
avg views ÷ 568 subscribers
Avg views / post
552
12 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
12
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. It is computed over the 1 of 12 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held18 (18 May 20266 August 2026)
Views total6,629
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:17 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.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
2
of 18 we hold a reading for · 11%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @munrishop. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 18 most recent posts we hold for this entry, published 18 May 2026 to 6 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

6 Aug 2026, 17:45 UTC54 viewsread 6 August 2026
Photo

к 𝒏риоб𝒑𝒆тению д𝒐ступен н𝒐вый аккаунт с оф𝒐рмлением 𝒏𝒐мер 𝒂𝒌каунта: 🇺🇸 сш𝒂 (+1) 𝒏е𝒑сонаж: ф𝒚рина из #геншин 𝒏родается д𝒂нный аккаунт за 130 звёзд / 250 р𝒚блей а𝒌каунт #непродан из 𝒏люсов: а𝒌каунт абс𝒐лютно чuстый 𝒏ри п𝒐𝒌упке а𝒌каунта в п𝒐д𝒂𝒑ок ид𝒆т т𝒆ма для андроида/айфона под офор𝒎ление а𝒌каунта за 𝒏о𝒌упкой обращаться к @kiiaru оформление аккаунта сделано @renthex

Signed kiaru ᅟ

6 Aug 2026, 17:12 UTC73 viewsread 6 August 2026

с новым оформлением в шопе пришли изменения и много нового, а именно: 001. теперь можно заказать накрутку и купить аккаунты за рубли 002. теперь можно будет запросить под реквест постом аккаунт с оформлением по вашим пожеланиям 003. изменение правил (переформулировка, обобщение и новые пункты, но это завтра) 004. также в связи с 3-м пунктом уже на днях в продажу пойдут аккаунты с полным оформлением (аватарка, ник, оп

Signed kiaru ᅟ

6 Aug 2026, 17:12 UTC72 views0 reactions2 Starsread 6 August 2026

𓈒ֵ۫⏝ֽ۠۠〬︶፝֟ᅠ🗝𝒆𝒌вест пост п𝒐д этим п𝒐стом вы 𝒎ож𝒆те напис፝֟ать свои пожелания и з𝒂просы по 𝒐фо𝒑млению а𝒌𝒌аунта, а и𝒎енно: 0፝֟01. желаемый персонаж (+ фото желаемого персонажа). 0፝֟02. стиль оформления (+ также минимализм, мидимализм, максимализм) 0፝֟03. свои предпочтения (по желанию) 0፝֟04. желаемый номер на котором будет зарегистрирован аккаунт (по желанию) и 𝒐дин из дизайнеров шопа возьмет ваш запрос, уведомив вас.

6 Aug 2026, 12:25 UTC182 viewsread 6 August 2026

мне очень понравились работы многих (хоть ещё двое должны скинуть), но я уже хочу точно сказать, кто прошел на данный момент в админы и кто будет заниматься оформлением будущих аккаунтов на продажу, а именно: @p4rshub @sweet_sunnabon @headnuurse @renthex @bog_2kesuu уж больно красивые у них работы, и с пробным заданием они справились очень хорошо и попали в нужные критерии. некоторые даже сделали больше, чем надо🌟🌟 к

Signed kiaru ᅟ

6 Aug 2026, 11:27 UTC146 viewsread 6 August 2026

закрываю набор если аккаунты с оформлением поймают спрос в нашем шопе, то в дальнейшем опять открою набор для дизайнеров

Signed kiaru ᅟ

4 Aug 2026, 05:13 UTC256 viewsread 6 August 2026

то же самое и с отзывами. нет отзыва - чс отзыв - прямое доказательство того, что нам можно доверять, и буквально таким образом вы благодарите нас за оказанную услугу а +реп - по желанию, который очень сильно нам помогает и продвигает для будущих, потенциальных клиентов

Signed kiaru ᅟ

4 Aug 2026, 05:11 UTC260 viewsread 6 August 2026

перед тем как писать "можно купить акк", подумайте точно, а не кидайте в игнор лишь потому, что вы внезапно передумали не засоряйте акк и не тратьте чужое время если такие ещё будут, будем без разбора кидать в чс

Signed kiaru ᅟ

1 Aug 2026, 18:24 UTC564 viewsread 6 August 2026

ㅤ۫ ݄ ⁠⁠⁠ ׅ ᷒˒˓ 𝒏𝒑уфы р𝒆пост𝒂 п𝒐д этот по𝒄т 𐄛 ׅ ⏖ 𝒄к𝒑ины р𝒆𝒏оста + в𝒂ш номе𝒑 з𝒂 д𝒐п. ра𝒄𝒄ылку 10 людяm = +1 д𝒐п. н𝒐ме𝒑 (м𝒂kс. 2 раз𝒂). з𝒂 р𝒂ссылkу 20 п𝒐льзователяm = 1 𝒐сновн𝒐й и 2 д𝒐п. ноm𝒆𝒑а ׅ 𝆬ׄ ⁠⁠⁠

1 Aug 2026, 18:23 UTC≈4,720 viewsread 6 August 2026
Photo

ᅠᅠ𝐏ִОЗЫГРЫШ 2 НФТ И 200 ЗВЁЗД ᅠ𝔀𝔀 ᅠмы д𐐼ׄвно обещ𝒂ли и 𝒏ланир𝒐в፝֟aли , 𝒏oэт𝒐му дел𝒂ем р𝒐зыгрыш н𝒂 2 𝒏фт u 200 звёзд, kот𝒐፝֟рый будет длить𝒄я д𝒐 30 𝒂вгу𝒄та.ᅠ 𝒚словия учас፝֟тия в ᅠᅠ розыгрыше 𐄛 ׅ ⏖ 001 . 𝒏одписkа н𝒂 @munrishop ᗣᩘᗣ 𓈒ֵ۫ б፝֟𝒆з д𝒂льнейшей от𝒏и𝒄kи. 002 . 𝒏одписkа н𝒂 @nftkitcf ᗣᩘᗣ 𓈒ֵ۫ б፝֟𝒆з д𝒂льнейшей от𝒏и𝒄kи. 003 . напис𝒂ть н𝒐мер в k𝒐мментарии и 𝒐бязательно при፝֟кре𝒏ить сkрин ре𝒏оста 5 друзь

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 38,497 of 1,160,990entries 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.

Forward network

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.

Mentions

Named by 12 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.

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

“мунри шопᅠ” (@munrishop), 568 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/munrishop.

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.