Telegram RegisterThe public register of Telegram

Channel

Мир добра 🖤

@psy_li4n

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

5,191subscribers

-20 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002465624298
TypeChannel
Username@psy_li4n
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/psy_li4n

Growth

5,1915,2115,2017 August 2026 — 5,211 subscribers7 August 2026 — 5,211 subscribers8 August 2026 — 5,209 subscribers10 August 2026 — 5,205 subscribers14 August 2026 — 5,191 subscribers7 August 202614 August 2026
5 measurements spanning 6 days, net -20. 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 5,188–5,214 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 01:435,191-14
10 Aug 2026, 22:225,205-4
8 Aug 2026, 06:085,209-2
7 Aug 2026, 16:015,211no change
7 Aug 2026, 15:575,211first reading

Engagement

55 posts held, back to 6 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 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
3.71%
avg views ÷ 5,191 subscribers
Avg views / post
193
55 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
55
of 55 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 12 August 2026
Posts held55 (6 August 202612 August 2026)
Views total10,599
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:37 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.

Recent posts

11 Aug 2026, 23:05 UTC49 viewsread 12 August 2026

Я шла с работы. Вдруг у метро ко мне подошла женщина, и очень тихо сказала: -Только не оборачивайся, а то прямо здесь умрёшь. От страха я задрожала и начала что то мычать. Я хотела позвать на помощь, но не смогла. Тело словно окаменело. А она медленно подошла ко мне совсем близко, взяла за руку и посмотрела мне за спину. Мой взгляд упал на ее лицо... и у меня перехватило дыхание от страшной догадки. Нет, такого не мо

11 Aug 2026, 23:00 UTC49 viewsread 12 August 2026
Photo

✨ - Что у вас запланировано на первое января? - Катание на санках. - А если снег не выпадет? - Нас это, конечно, огорчит, но не остановит. Мир добра

11 Aug 2026, 19:00 UTC79 viewsread 12 August 2026
Photo

✨ Желаний в этом году накопилось СТОЛЬКО, что я решила, кроме Деда Мороза написать Санта Клаусу, Николаусу, и Йоулупукки, иЗюзе, и Бабаю... А вдруг? Мир добра

11 Aug 2026, 16:00 UTC109 viewsread 12 August 2026
Photo

✨ Не существует неправильного тела, существует неправильное платье. Мир добра

11 Aug 2026, 15:00 UTC115 viewsread 12 August 2026
Photo

‼️ — Я столько лет терпела твои измены. Теперь моя очередь, милый... Виктор прочитал записку на кухонном столе и сел мимо стула. Почерк жены. Лидин. Аккуратный, с завитушками, как в открытках на годовщину. Только годовщиной тут не пахло. Он перечитал ещё раз. Потом открыл окно. Потом закрыл. Потом выпил воды прямо из графина. «Знает», — холодно ударило в голову. 3 года он встречался с Аллой и был уверен, что всё п

11 Aug 2026, 13:00 UTC135 viewsread 12 August 2026

Пришлось выйти замуж в 19. Отец сильно болел, жили очень бедно, а тут богатый мужчина... Отец согласился, хотя я должна была стать второй женой. Жених как и обещал построил дом, вылечил отца. После свадьбы сразу улетели в Москву, к его первой семье. Муж сказал,что спать мы не будем, мол, очень любит первую жену. Жила одна, он приходил говорить, привозил еду. В один день позвонил и сказал, что вечером заедет и повезё

11 Aug 2026, 12:00 UTC145 viewsread 12 August 2026
Photo

✨ ...Не имей привычки постоянно оборачиваться в прошлое. Там нет уже ничего привлекательного. Сравни себя сейчас и год назад. Перемены, которые постоянно происходят с тобой уже не совпадают с тем, что было. Они требуют то, что будет. Меняясь, ты идешь к другим событиям, другим людям, другой жизни. с легкостью выбрасывай все то, с чем тебе дальше не по пути и что так тяжело тянуть за собой. Никогда не жалей старое пал

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

“Мир добра 🖤” (@psy_li4n), 5,191 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/psy_li4n.

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.