Telegram RegisterThe public register of Telegram
Telegram profile photo for луговые мари, please tokyo и все-все-все

Channel

луговые мари, please tokyo и все-все-все

@lugovyemari

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

875subscribers

+5 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-1001759039282
TypeChannel
Username@lugovyemari
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/lugovyemari

Growth

8698758726 August 2026 — 870 subscribers6 August 2026 — 870 subscribers7 August 2026 — 869 subscribers14 August 2026 — 875 subscribers6 August 202614 August 2026
4 measurements spanning 8 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 868–876 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 13:37875+6
7 Aug 2026, 07:55869-1
6 Aug 2026, 14:34870no change
6 Aug 2026, 08:49870first reading

Engagement

12 posts held, back to 25 July 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
43.3%
avg views ÷ 875 subscribers
Avg views / post
379
12 posts measured
Reaction rate
9.90%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 3 August 2026
Posts held12 (25 July 20263 August 2026)
Views total4,544
Reactions total450
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 14:34 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.

Reaction mix

450 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 60.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
27260.4%
custom 54701165620337113285712.7%
custom 54628698226289615744610.2%
❤‍🔥316.89%
custom 5323759242115560120224.89%
🔥204.44%
custom 547229159360196351320.444%

Custom emoji. 4 of the rows above are 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 areTelegram’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 12 of the 12 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 450reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 25 July 2026 to 3 August 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

3 Aug 2026, 14:02 UTC226 views19 reactionsread 6 August 2026
Forwarded from @echomaniafestPhoto

луговые мари 🏞 легенды купить билет

19

3 Aug 2026, 10:53 UTC274 views26 reactionsread 6 August 2026
Video

На днях мы отправились в Обнинск на фестиваль, и совершенно спонтанно получилось влететь на несколько треков с шÿвыр в лайв-сет Obnx Ska Sckankers Сам Обнинск, люди которые там живут, сосны, которые тянутся к небу - это просто нечто Сошлись на том, что это будто бы какой-то сон, потому что тяжело поверить в то, что наяву может быть так здорово!

16🔥10

28 Jul 2026, 13:11 UTC455 views28 reactionsread 6 August 2026
File

Ну Чуваши конечно маттурсем в плане ритмики… Артем включил сборник Чувашских песен на пластинке и некоторые запали прямо в самое сердце

27🔥1

28 Jul 2026, 11:30 UTC541 views22 reactionsread 6 August 2026
Photo

Следующая остановка - Эхомания в Москве 15 августа! Покто веле, корно сай! Билеты тут!

10custom 54628698226289615748custom 53237592421155601204

28 Jul 2026, 08:29 UTC392 views69 reactionsread 6 August 2026
Photo

А у нашей Лады сегодня день рождения! Шочмо кече дене! 💚

41❤‍🔥17custom 53237592421155601206custom 54628698226289615745

28 Jul 2026, 05:38 UTC356 views35 reactionsread 6 August 2026
Forwarded from @ladaism_nabroskiPhoto

Козьмодемьянск

31custom 54628698226289615743❤‍🔥1

27 Jul 2026, 10:27 UTC345 views69 reactionsread 6 August 2026
Forwarded from @vishvetkasabinaPhoto

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

custom 54701165620337113283424custom 54628698226289615747custom 53237592421155601204

27 Jul 2026, 06:09 UTC368 views44 reactionsread 6 August 2026
Video

Кырык марла шиэш йäнг, Äтям-äвäм кырык марын. Кырык мары мыры сем, Пӹрхä сусун йäнг гӹцем live @ Кырыкмары кымдем снял Артем!

24custom 546286982262896157410custom 53237592421155601208custom 54722915936019635132

26 Jul 2026, 12:32 UTC537 views43 reactionsread 6 August 2026
Video

live @ Chuvashia 2002

19custom 547011656203371132815🔥9

26 Jul 2026, 08:29 UTC337 views25 reactionsread 6 August 2026
Forwarded from @topyo_mediaVideo

Группа «Луговые Мари» на благотворительном фестивале «Шевле»⭐️

23custom 54701165620337113282

26 Jul 2026, 05:55 UTC338 views47 reactionsread 6 August 2026
Forwarded from @shevlefestVideo

Марийские настроения от Луговых Мари⭐️

30custom 546286982262896157411custom 54701165620337113286

25 Jul 2026, 13:15 UTC375 views23 reactionsread 6 August 2026
Video message

Video message, posted without a caption

❤‍🔥138custom 54628698226289615742

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

Citation-graph rank — 108,728 of 1,549,376entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“луговые мари, please tokyo и все-все-все” (@lugovyemari), 875 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/lugovyemari.

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.