Telegram RegisterThe public register of Telegram
Telegram profile photo for Likoha

Channel

Likoha

@likohacos

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

159subscribers

+8 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001527920830
TypeChannel
Username@likohacos
CreatedBetween 1 August 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/likohacos

Growth

1511591559 August 2026 — 151 subscribers10 August 2026 — 152 subscribers18 August 2026 — 159 subscribers9 August 202618 August 2026
3 measurements spanning 8 days, 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 150–160 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 01:43159+7
10 Aug 2026, 14:33152+1
9 Aug 2026, 17:46151first reading

Engagement

14 posts held, back to 5 August 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
52.8%
avg views ÷ 159 subscribers
Avg views / post
83.9
14 posts measured
Reaction rate
19.6%
reactions ÷ views · ER floor
Posts in window
14
of 14 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 13 of 14 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 held14 (5 August 20269 August 2026)
Views total1,175
Reactions total213
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 17: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

213 reactions across 13 posts, in 7 distinct kinds. The most used accounts for 40.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8740.8%
custom 57783716949220447425023.5%
🔥3014.1%
custom 57784650761009931792210.3%
💋94.23%
💅83.76%
73.29%

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

Measured over the 14 most recent posts we hold, published 5 August 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

9 Aug 2026, 12:31 UTC46 views16 reactionsread 9 August 2026
Photo

Бийская косплей-делегация едет домой🛤

custom 5778371694922044742113custom 57784650761009931792

9 Aug 2026, 08:13 UTC55 views14 reactionsread 9 August 2026
Photo

У меня ещё есть такие фотки с парнями😎

10🔥4

9 Aug 2026, 06:57 UTC54 views15 reactionsread 9 August 2026
Forwarded from @ne_van_goghhPhoto

И ещё с Ликохой 🩷

7custom 57783716949220447426custom 57784650761009931792

8 Aug 2026, 14:34 UTC81 views28 reactionsread 9 August 2026
Photo

Ну какая я тусовщица, блин, класс💅

custom 5778371694922044742137🔥42custom 57784650761009931792

8 Aug 2026, 13:32 UTC81 views20 reactionsread 9 August 2026
Photo

Победила Лагунка то моя!🥳 Ураа)) И вышла прям огонь, я зря переживала, столько комплиментов получила, спасибо всем большое за поддержку❤️❤️❤️ (на дипломах видимо не всегда пишут номинации и места, не знала, поэтому не сразу поняла, ахах)

14🔥3custom 57783716949220447422custom 57784650761009931791

8 Aug 2026, 09:04 UTC78 views24 reactionsread 9 August 2026
Video message

Video message, posted without a caption

custom 5778371694922044742137custom 57784650761009931794

7 Aug 2026, 16:21 UTC88 views27 reactionsread 9 August 2026
Photo

🩷🩷🩷🩷🩷на ре:пати Я завтра очень постараюсь быть этой дивой🙏 Первый раз со мной такое, что я ни разу не мерила образ целиком перед выходом в свет🫪 Надеюсь, всë будет гуд🤞

🔥12💋96

7 Aug 2026, 14:36 UTC87 views14 reactionsread 9 August 2026
Photo

Поезд уже второй раз останавливают, но мне есть чем заняться

9custom 57784650761009931793custom 57783716949220447422

7 Aug 2026, 10:43 UTC88 views15 reactionsread 9 August 2026
Photo

Забыла скинуть результат примерки: Как я и думала, смотрится странно и непропорционально (огромная грудь на контрасте съедает попу). Может дело в размере одежды (но как выбрать размер с прежними нижними параметрами, если верхний так сильно изменился??), может в самом фасоне платья Нефер, но мне очень не понравилось как это выглядит и я решила фткаться без них. Теперь ищем персонажа с гигабубами.

10custom 57784650761009931795

7 Aug 2026, 09:10 UTC91 views12 reactionsread 9 August 2026

На фатуи точно нет, слишком устала от всей этой беготни по городам-вокзалам, хочу отдохнуть. На арлекино возможно, если успею персонажа и номер придумать) Про гэлэкси не слышала, кстати, когда он будет, так что не планировала пока

💅84

7 Aug 2026, 09:10 UTC90 viewsread 9 August 2026

Извините за беспокойство! А вы будете на Фатуи Фесте/Арлекино/Гэлэкси Ивенте?🥹

6 Aug 2026, 12:34 UTC100 views15 reactionsread 9 August 2026
Photo

Отфоталась~

9custom 57783716949220447423custom 57784650761009931793

Showing the 12 most recent of 14 posts we hold for @likohacos. 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 — 148,546 of 1,548,671entries 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 1 registered channel — 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.

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

“Likoha” (@likohacos), 159 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/likohacos.

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.