Telegram RegisterThe public register of Telegram

Channel

живые кости

@livingbones_tg

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

18,458subscribers

-92 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001954974050
TypeChannel
Username@livingbones_tg
DescriptionНа самом деле анорексия давно контролирует тебя. Прайс на все каналы: t.me/pricerekssakamol Владелец: @ilovellarixx Boost: https://t.me/boost/livingbones_tg Чат: https://t.me/+7j0Fp2WHt5g1NTZi (правила обязательны к прочтению)
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/livingbones_tg

Growth

18,45818,55018,5047 August 2026 — 18,550 subscribers7 August 2026 — 18,550 subscribers8 August 2026 — 18,546 subscribers8 August 2026 — 18,523 subscribers9 August 2026 — 18,510 subscribers10 August 2026 — 18,494 subscribers11 August 2026 — 18,486 subscribers12 August 2026 — 18,469 subscribers14 August 2026 — 18,458 subscribers7 August 202614 August 2026
9 measurements spanning 7 days, net -92. 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 18,444–18,564 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:3818,458-11
12 Aug 2026, 23:0418,469-17
11 Aug 2026, 21:2218,486-8
10 Aug 2026, 21:0618,494-16
9 Aug 2026, 21:5218,510-13
8 Aug 2026, 23:1218,523-23
8 Aug 2026, 01:2118,546-4
7 Aug 2026, 18:3018,550no change
7 Aug 2026, 18:2918,550first reading

Engagement

42 posts held, back to 3 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 21 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
9.43%
avg views ÷ 18,458 subscribers
Avg views / post
1,740
42 posts measured
Reaction rate
7.08%
reactions ÷ views · ER floor
Posts in window
42
of 42 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 14 August 2026
Posts held42 (3 August 202614 August 2026)
Views total73,104
Reactions total5,173
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 10:50 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.

What this channel posts

Photos
8,360
Videos
1,680
Links
669

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 24s
Average length
14s

Measured directly from 6 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

5,173 reactions across 42 posts, in 2 distinct kinds. The most used accounts for 53.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54205751278866384262,77053.5%
💔2,40346.5%

Custom emoji. One row above is a 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 count beside it isTelegram’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 42 of the 42 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 5,173reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

14 Aug 2026, 15:58 UTC≈1,000 views65 reactionsread 15 August 2026
Photo

🤩🤩#истории #обсуждение🤩🤩 🕯🕯🕯🕯🕯🕯🕯🕯🕯🕯🕯 как вы думаете, что должен делать человек, если у него слишком тяжёлый случай для обычной терапии, но при этом не готов к стационару? 🕯🕯🕯🕯🕯🕯🕯🕯🕯🕯🕯

custom 542057512788663842636💔29

14 Aug 2026, 15:52 UTC984 views202 reactionsread 15 August 2026
Photo

💙💙💙💙💙💙💙💙💙💙 🌟 - идеал 🌟🌟🌟💔 - перебор 💙💙💙💙💙💙💙💙💙💙 🤩🤩🤩#кости🤩🤩🤩

💔139custom 542057512788663842663

13 Aug 2026, 17:25 UTC≈1,430 views125 reactionsread 15 August 2026

Делать ещё такие посты? Извините я просто очень люблю супы поэтому сделала такой постик

custom 5420575127886638426114💔11

13 Aug 2026, 16:22 UTC≈1,530 views9 reactionsread 15 August 2026
Photo

🤩 Ты уже выбрала свою вселенную? В AniWorld ты не просто смотришь аниме – ты в нем живешь! ⭐⭐⭐⭐⭐⭐⭐⭐⭐ ⚔️ Собирай карты любимых персонажей 🖼 Захватывай города 🔥 Прокачивай способности 🥺 Вступай в клан и веди войны за территории ⭐⭐⭐⭐⭐⭐⭐⭐⭐ Десятки вселенных, ивенты каждую неделю, и сообщество, которое уже рубится не на шутку. ⭐⭐⭐⭐⭐⭐⭐⭐⭐ 👥 +1.ООО пользователей уже играет, присоединяйся к нам: @aniwrd_bot

💔9

13 Aug 2026, 16:04 UTC≈1,490 views71 reactionsread 15 August 2026
Photo

™️🌰🐶 самых высококалорийных и самых низкокалорийных супов 🍲low‑calorie: 🤩Мисо-суп ≈ 15-20ккал/100г 🤩Гаспачо ≈25-35ккал/100 г 🤩Овощной суп ≈30-35 ккал/100г 🤩Куриный суп с лапшой ≈30-45 ккал/100г 🤩Томатный суп без сливок ≈35-40 ккал/100г 🍜high‑calorie: 🤩Beer Cheese Soup / пивной сырный суп ~150-200ккал/100г 🤩Cheeseburger Soup / чизбургер-суп ~140-190ккал/100г 🤩Loaded Baked Potato Soup / картофельный суп с сыром, слив

custom 542057512788663842659💔12

12 Aug 2026, 19:13 UTC≈1,800 views266 reactionsread 15 August 2026
Photo

💙💙💙💙💙💙💙💙💙💙 🌟 - идеал 🌟🌟🌟💔 - перебор 💙💙💙💙💙💙💙💙💙💙 🤩🤩🤩#кости🤩🤩🤩

💔165custom 5420575127886638426101

12 Aug 2026, 12:02 UTC≈1,760 views62 reactionsread 15 August 2026
Video

🤩 отдать голос каналу 🤩 вступить в чат 🤩 предложка 🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 #тиктоки 👿

custom 542057512788663842646💔16

12 Aug 2026, 05:20 UTC538 views68 reactionsread 12 August 2026
Photo

🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠 😀😀😀😀😀😀😀😀😀😀😀😀 🦋🅰️улимия – не длинноволосая красавица, скорчившаяся над унитазом с печальным выражением на смазливом лице, это – распухшая физиономия со стекающей по подбородку рвотой и чёртова кровь из носа. 😀😀😀😀😀😀😀😀 🦋🅰️норексия – не стройная нимфа, смущённо отказывающаяся от пирожного, это – волосы по всему твоему замёрзшему истощённому телу. 😀😀😀😀😀😀😀😀 🦋🅰️епрессия – не моде

custom 542057512788663842646💔22

11 Aug 2026, 20:51 UTC≈1,140 views113 reactionsread 12 August 2026

голод - не норма переедание - не норма что же тогда для вас норма?

💔80custom 542057512788663842633

11 Aug 2026, 15:50 UTC≈1,420 views57 reactionsread 12 August 2026

По скидывайте ваши самые крутые смешные стикеры которыми вы пользуетесь

custom 542057512788663842648💔9

10 Aug 2026, 20:17 UTC≈1,970 views184 reactionsread 12 August 2026
Photo

В мечтах всё равно когда-нибудь иметь такую фигуру

custom 5420575127886638426136💔48

10 Aug 2026, 18:39 UTC≈1,770 views160 reactionsread 12 August 2026
Photo

Делитесь любыми итогами дня в чате, от сегодняшнего рациона до своего самочувствия 🌟 🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️ 🖤🤩- был хороший день 🖤 🖤 💔 - был плохой день 🖤 🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️🌨️

custom 542057512788663842699💔61

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

Mentions

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.

“живые кости” (@livingbones_tg), 18,458 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/livingbones_tg.

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.