Telegram RegisterThe public register of Telegram
Telegram profile photo for Komori

Channel

Komori

@KomoriForest

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

290subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001670898042
TypeChannel
Username@KomoriForest
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/KomoriForest

Growth

289290289.57 August 2026 — 289 subscribers8 August 2026 — 289 subscribers16 August 2026 — 290 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, net +1. 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 289–290 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 16:53290+1
8 Aug 2026, 08:18289no change
7 Aug 2026, 18:07289first reading

Engagement

20 posts held, back to 8 March 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 20 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 08s
Average length
2m 04s

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

885 reactions across 20 posts, in 20 distinct kinds. The most used accounts for 24.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
21424.2%
❤‍🔥21224.0%
custom 52333331638743444809510.7%
🔥9510.7%
custom 5377762498743116673748.36%
💘444.97%
🕊313.50%
💋283.16%
custom 5357357315278253846273.05%
😨141.58%
💊101.13%
custom 535740770383457065691.02%
🥰80.904%
custom 535729068745059156270.791%
🤡70.791%
😱50.565%
custom 536650492130886916620.226%
💅10.113%
😈10.113%
😘10.113%

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

Measured over the 20 most recent posts we hold, published 8 March 2026 to 3 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.

Telegram Stars

Stars received
3
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @KomoriForest. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 8 March 2026 to 3 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

3 Jul 2026, 11:35 UTC172 views26 reactionsread 8 August 2026

вспомнила, что я оказывается ещё умею на бумаге рисовать

14🕊5❤‍🔥4😈1custom 53572906874505915621custom 53573573152782538461

3 Jul 2026, 11:35 UTC173 views33 reactionsread 8 August 2026
Photo

Photo, posted without a caption

18❤‍🔥9🕊3custom 52333331638743444801custom 53573573152782538461custom 53665049213088691661

16 Jun 2026, 09:09 UTC270 views35 reactionsread 8 August 2026
Photo

https://vt.tiktok.com/ZSQq4rsUr в ТТ заливается больше контента, так чтооооо

💘16🕊8custom 535729068745059156252❤‍🔥1custom 52333331638743444801custom 53573573152782538461custom 53665049213088691661

14 Jun 2026, 20:53 UTC284 views47 reactionsread 8 August 2026
Photo

а вот и заказики пошли

❤‍🔥25🕊8💋5custom 53573573152782538463custom 53777624987431166733custom 52333331638743444802custom 53572906874505915621

29 May 2026, 15:28 UTC384 views45 reactionsread 8 August 2026
Photo

Воспоминания

28❤‍🔥11💘4custom 53573573152782538461custom 53777624987431166731

28 May 2026, 14:14 UTC362 views57 reactionsread 8 August 2026
Photo

опять сага вайб?🤩

🔥29💘15❤‍🔥82custom 52333331638743444801custom 53574077038345706561custom 53777624987431166731

27 May 2026, 19:18 UTC342 views57 reactionsread 8 August 2026
Photo

сон

❤‍🔥379🔥6💊2🤡1custom 52333331638743444801custom 53777624987431166731

22 May 2026, 09:33 UTC391 views47 reactions3 Starsread 8 August 2026
Photo

Photo, posted without a caption

custom 5377762498743116673305❤‍🔥5🕊4💊1🤡1custom 52333331638743444801

10 May 2026, 19:15 UTC459 views56 reactionsread 8 August 2026
Photo

ой, а тут у одной группы сингл выходит с обложкой моей. поддержите ребят ❤️

🔥27custom 537776249874311667311custom 53573573152782538469❤‍🔥5🕊2💊1🤡1

22 Apr 2026, 17:40 UTC485 views53 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 52333331638743444802413🔥9❤‍🔥4🤡2💊1

17 Apr 2026, 10:20 UTC503 views52 reactionsread 8 August 2026
Photo

Photo, posted without a caption

27custom 537776249874311667314custom 53574077038345706566❤‍🔥3💊2

9 Apr 2026, 15:29 UTC546 views35 reactionsread 8 August 2026
Photo

а вот мне интересно, а какой контент вам нравится на моём канале? может стоит что-то новенькое вбросить? или вернуть гартик?

custom 523333316387434448025custom 53573573152782538463custom 53574077038345706562custom 53777624987431166732❤‍🔥1💊1🕊1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“Komori” (@KomoriForest), 290 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/KomoriForest.

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.