Telegram RegisterThe public register of Telegram
Telegram profile photo for своя комната

Channel

своя комната

@leriyaagreeennn

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

151subscribers

-10 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-1001805890510
TypeChannel
Username@leriyaagreeennn
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/leriyaagreeennn

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 25 September 2026 and assigned it the closest of 31 fixed categories, at 74% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

15116115610 August 2026 — 161 subscribers11 August 2026 — 161 subscribers18 August 2026 — 159 subscribers25 August 2026 — 156 subscribers1 September 2026 — 153 subscribers9 September 2026 — 152 subscribers16 September 2026 — 151 subscribers10 August 202616 September 2026
7 measurements spanning 37 days, net -10. 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–163 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 18:39151-1
9 Sept 2026, 10:16152-1
1 Sept 2026, 00:48153-3
25 Aug 2026, 09:22156-3
18 Aug 2026, 10:27159-2
11 Aug 2026, 02:31161no change
10 Aug 2026, 22:16161first reading

Engagement

7 posts held, back to 4 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 7 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
44s
Average length
22s

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

71 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 33.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53733447555120050342433.8%
custom 52422019320381539251825.4%
custom 52334325708924016961216.9%
custom 52357289138119098161216.9%
custom 534397914069127426857.04%

Custom emoji. Every 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 counts beside them are Telegram’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 7 of the 7 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 71 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

10 Aug 2026, 18:28 UTC12 views3 reactionsread 10 August 2026
Forwarded from @strokdushi

Posted without readable text

custom 53733447555120050343

10 Aug 2026, 18:24 UTC95 views8 reactionsread 10 August 2026
Photo

🤍🤍🤍 | спустя две недели после возвращения домой я вышла куда-то дальше Кекса возле дома сегодня была на коллажной встрече. у нас в Ростове прекрасная Лена проводит встречи для тех, кто любит клеить коллажи в блокнотах. дико соскучилась по девочкам, потому что не видела их месяца три уже наверное. как приятно просто сидеть, пить лимонад, хихикать и клеить разворотики. а еще я сегодня принесла девочкам метафорические…

custom 52334325708924016963custom 53733447555120050343custom 52422019320381539252

8 Aug 2026, 19:45 UTC55 views12 reactionsread 10 August 2026
Video

не прошло и года | ⭐️📔🌟 и вот наконец-то я намонтировала разворот с Катиным стикерпаком. видосики получаются у меня пока так себе, думаю, мне для них нужен другой штатив, но я постаралась в вайб. думаю, для начала это уже неплохо. жду много красивых реакций, если вам понравился разворотик и вы хотите еще таких видео💙

custom 53733447555120050347custom 52422019320381539253custom 52334325708924016962

7 Aug 2026, 18:20 UTC49 views9 reactionsread 10 August 2026
Photo

🤍🤍🌟держусь только на этом вам тоже скоро покажу. и разворот с Катиным стикерпаком. как раз на днях намонтировала.

custom 52422019320381539256custom 52334325708924016963

7 Aug 2026, 12:30 UTC48 views13 reactionsread 10 August 2026
Photo

утро | 🍯🌟🌟 по чуть-чуть возвращаюсь к делам. их откуда-то берется куча, наверное потому что я сама себе их придумываю. сегодня внезапно рано встала и решила посидеть пописать тексты. самый лучший способ не выпадать из интернета - наделать контента на месяц вперед. благо тем для буковок у меня хоть отбавляй, меньше не станет. тем более я на вчера на досуге почитала пару гайдов по написанию сценариев для рилс. вот бу…

custom 52357289138119098165custom 53439791406912742685custom 52334325708924016962custom 53733447555120050341

4 Aug 2026, 18:25 UTC54 views13 reactionsread 10 August 2026
Photo

✨обещала вам красоту из окна самолета✨

custom 52357289138119098167custom 53733447555120050346

4 Aug 2026, 18:22 UTC55 views13 reactionsread 10 August 2026
Photo

☕️🌟5-6/6 на 5 день в Египте Макс решил, что это не честно, что плохо только мне, и тоже организовал себе тепловой удар. поэтому наша поездка в Каир за малым не отменилась из-за его трупа, но он в итоге ожил, и мы уехали. 🌟сам Каир мы конечно толком не посмотрели, но нам и не надо было. нам нужны были пирамиды, а они находятся как раз в черте города. но этот факт вообще не убавляет их ваушности. 🌟на пирамидах мы ту…

custom 52422019320381539257custom 53733447555120050344custom 52334325708924016962

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

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

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

“своя комната” (@leriyaagreeennn), 151 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/leriyaagreeennn.

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.