Telegram RegisterThe public register of Telegram

Channel

ламия вещает_

@llamia_m

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

192subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002726833482
TypeChannel
Username@llamia_m
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/llamia_m

Growth

19210 Aug 2026, 08:46 — 192 subscribers10 Aug 2026, 21:48 — 192 subscribers10 Aug 2026, 08:4610 Aug 2026, 21:48
2 measurements taken within a single day. 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 191–193 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:48192no change
10 Aug 2026, 08:46192first reading

Engagement

19 posts held, back to 26 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
59.3%
avg views ÷ 192 subscribers
Avg views / post
114
19 posts measured
Reaction rate
14.2%
reactions ÷ views · ER floor
Posts in window
19
of 19 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 12 of 19 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 9 August 2026
Posts held19 (26 July 20269 August 2026)
Views total2,165
Reactions total187
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 08:46 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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54247862960757228645629.9%
custom 53552791008628347015026.7%
custom 53436897286150033822613.9%
🍓2513.4%
custom 5215268101930658574189.63%
custom 5269423323091078606115.88%
custom 533919727872276255010.535%

Custom emoji. 6 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 19 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 187reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 26 July 2026 to 9 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

8 Aug 2026, 18:17 UTC70 views6 reactionsread 10 August 2026
File

телеграм жесть качество съел

custom 53436897286150033824🍓1custom 54247862960757228641

8 Aug 2026, 18:15 UTC71 views33 reactionsread 10 August 2026
Photo

🤩 задумывалось как просто забавный скетч изначально , , , ну да ладно, всё равно хотела обновить аватарку 🤩 #ut #сона #ламия

custom 542478629607572286414custom 53552791008628347019🍓6custom 53436897286150033823custom 52152681019306585741

6 Aug 2026, 11:54 UTC94 views10 reactionsread 10 August 2026
Photo

☀️ очень кривой и быстрый скетч с Гено, тк у моего котенка сегодня день рождения ❤️❤️ ☀️а ещё я, кстати, пытаюсь сделать одно видео с лами и киллером . . .😉 #ut #гено

custom 52694233230910786064🍓3custom 53552791008628347012custom 53436897286150033821

6 Aug 2026, 09:52 UTC74 views5 reactionsread 10 August 2026
Forwarded from @inversionoffPhoto

• Арт на заказ 🎀 {💕}- Здравствуйте! Вот первый заказ который я закончила 😚 Цена: 140⭐ - два персонажа по 70⭐ Автор: её Телеграмм-канале 🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤 #Арт #артназаказ #ТФ

custom 52152681019306585744custom 54247862960757228641

4 Aug 2026, 06:15 UTC112 views15 reactionsread 10 August 2026
Photo

☀️утро начинается не с кофе. ☀ Вообще я это ещё ночью нарисовала, но выкладывать пост в час с чем-то ночи не посчитала рациональным. 😮‍💨 #ut #эррор

custom 53552791008628347018custom 54247862960757228643custom 53436897286150033822custom 52152681019306585741custom 52694233230910786061

2 Aug 2026, 06:20 UTC136 views5 reactionsread 10 August 2026

☀️ХОСПИ ТЫ СУМАСШЕДШАЯ поз 🥹

custom 52152681019306585743custom 53552791008628347011custom 54247862960757228641

2 Aug 2026, 06:19 UTC121 viewsread 10 August 2026
Forwarded from @AnonAskBot

💬 У тебя новое анонимное сообщение! Между выбором 1. Пойти спать и 2. Бабахнуть пак ночью, чтобы отказала голова и у меня начались головокружения... Я выбрала второе. Чтобы сделать вторую часть пака, но уже не только с ос по ох. Может ещё твои работы добавлю, но позже... Пока такие. Самые главные ос (?) > https://t.me/addemoji/Lamiachanemoji_by_TgEmodziBot ⬅️ Свайпни для ответа.

1 Aug 2026, 20:13 UTC123 views18 reactionsread 10 August 2026
Photo

🤩некая к. давненько не рисовала её. на полноценку не хватило бюджета . . .😊 #hh #ос #келия

custom 52152681019306585747custom 53552791008628347017custom 52694233230910786062custom 53436897286150033821custom 54247862960757228641

31 Jul 2026, 14:43 UTC120 views3 reactionsread 10 August 2026

friendly reminder что у меня есть некий тикток 🙂 https://vt.tiktok.com/ZS4Mbkc7A/ #щп

🍓3

31 Jul 2026, 12:31 UTC117 views27 reactionsread 10 August 2026
Photo

☀️люблю Дрима и люблю жанр махо-сёдзе . . . Совместила две любимые вещи хд. ☀️а ещё Нил его котик, как Усаги и Луна :3 #ut #дрим #кор #нил

custom 542478629607572286413custom 53436897286150033827🍓5custom 52694233230910786061custom 53552791008628347011

Showing the 12 most recent of 19 posts we hold for @llamia_m. 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 — 721,172 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

Republished by

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

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.

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.

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

“ламия вещает_” (@llamia_m), 192 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/llamia_m.

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.