Telegram RegisterThe public register of Telegram

Channel

лайв коал

@livekoal

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

10subscribers

+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-1003874362633
TypeChannel
Username@livekoal
CreatedBetween 1 February 2026 and 10 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/livekoal

Growth

1010 August 2026 — 10 subscribers12 August 2026 — 10 subscribers10 August 202612 August 2026
2 measurements spanning 2 days. 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 9–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 10:0410no change
10 Aug 2026, 19:4510first reading

Engagement

17 posts held, back to 10 June 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 14 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
34
Videos
65
Links
15

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
43s
Average length
14s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

27 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 44.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1244.4%
🍓1140.7%
❤‍🔥13.70%
🎅13.70%
👍13.70%
🔥13.70%

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

Measured over the 17 most recent posts we hold, published 10 June 2026 to 14 July 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

14 Jul 2026, 06:38 UTC16 viewsread 12 August 2026
Forwarded from @IslandOfDawn

Флуд закрывается. Спасибо всем за проведенное вместе время, не знаю, будет новый или нет. В общем, нам кажется, что мы уже давно не для флудов или прочих заморочек. Разрыв со всеми союзниками У WT еще один союзник закрылся #breakup #repost

10 Jul 2026, 15:42 UTC181 viewsread 12 August 2026

❕ очень важно — всем союзникам привет, доброе утро, доброго вечера. я принял очень важное решение — заморозить проект на долгое время, пока сам не смогу собраться и полноценно вести ролевую. особых причин для этого нет, скорее всё личное, а отчасти становится труднее вести проект. насчёт того, что будет с союзами, я пока не решил, но думаю, с учётом того, что разморозка будет явно не че

5 Jul 2026, 10:00 UTC30 views1 reactionsread 12 August 2026
Forwarded from @partiyaboulinga

внимание, пожарная тревога. срочно ищем САЯ (который с дрессроуз, муж детки 5), ЛУФФИ, ЧАКУ (который с алабасты), КУРО (18+) и СМОКЕРА (17+). писать @tr4flaw по поводу вступления. пж, вступите за них, а то меня ждущие сожрут. репост по желанию. 🌟

🍓1

4 Jul 2026, 12:29 UTC227 views2 reactionsread 12 August 2026

нам очень нужны участники в нашу ролевую, только вышли из внутреннего реста. инфо — https://t.me/hvnlyinfo писать:@hvlly_bot ~ @myakitty союзы, очень надеюсь на репост

1🍓1

2 Jul 2026, 09:22 UTC48 views1 reactionsread 12 August 2026
Forwarded from @HanhokbrothelLAIFPhoto

🔀🔀🔀🅰️овый союз🔀🔀🔀 Мы заключили новый союз! Со флудом 𖥔𝑯𝒆𝒂𝒗𝒆𝒏𝒍𝒚 Владелец флуда: @moyasanncc Лайф канал: тык #союзыHB #unionsHB

🍓1

30 Jun 2026, 13:17 UTC34 views2 reactionsread 12 August 2026
Forwarded from @IslandOfDawn2

Мы тоже ищем новые союзы Условия #repost

❤‍🔥1🍓1

20 Jun 2026, 14:57 UTC60 views3 reactionsread 12 August 2026

➖➖➖➖➖➖➖➖➖➖ ⟨🧏⟩ –– Всем доброго времени суток. Спешу сообщить, что наш проект уходит в рест до 17.07! Скорее всего проект будет переоформлен, а также будут внесены небольшие корректировки в правила и условия заключения союзов, особых изменений там не будет. ➖➖➖➖➖➖➖➖➖➖ #news

2🍓1

18 Jun 2026, 09:57 UTC52 views6 reactionsread 12 August 2026

я бы побоялась так ло сказать☠☠ и спасибо☝️

3🍓1👍1🔥1

18 Jun 2026, 09:57 UTC45 views1 reactionsread 12 August 2026
Forwarded from @ARCOBALENO_lifePhoto

Вот такая пицца у нас получилась😁😁😁😁#ЛоЯНеНапишуАнкету. Коала с дррррр(Heavenly) #РЕПОСТ

🎅1

17 Jun 2026, 21:01 UTC21 viewsread 12 August 2026
Forwarded from @Namilifechannel

Всем доброго вечера суток. хотела бы сообщить новость, что я ухожу из должности владельца. У меня нет больше времени и желания вести флуд. Флуд держался по факту довольно большое время, та и была идея закрыть, но обстоятельства сложились иначе. Теперь новый владелец наш админ - Дофламинго: @Zeekrsad Теперь Доффи будет за это отвечать (желаю удачи) ➿➿➿➿➿➿➿ Была рада знакомству с союзниками, но а с чатом не пр

17 Jun 2026, 06:32 UTC45 views2 reactionsread 12 August 2026
Photo

гуд гайс, итс уамии. караули

1🍓1

Showing the 12 most recent of 17 posts we hold for @livekoal. 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 — 395,759 of 1,176,251entries 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 6 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“лайв коал” (@livekoal), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/livekoal.

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.