Telegram RegisterThe public register of Telegram
Telegram profile photo for Alexey_Kharitonov

Channel

Alexey_Kharitonov

@Kharit_on_off

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

504subscribers

+9 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-1001788085955
TypeChannel
Username@Kharit_on_off
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 live12 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/Kharit_on_off

Topic

Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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

495504499.57 August 2026 — 495 subscribers8 August 2026 — 495 subscribers15 August 2026 — 496 subscribers31 August 2026 — 497 subscribers10 September 2026 — 498 subscribers17 September 2026 — 499 subscribers2 October 2026 — 503 subscribers12 October 2026 — 504 subscribers7 August 202612 October 2026
8 measurements spanning 66 days, net +9. 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 494–505 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 13:50504+1
2 Oct 2026, 02:42503+4
17 Sept 2026, 16:58499+1
10 Sept 2026, 13:21498+1
31 Aug 2026, 09:54497+1
15 Aug 2026, 11:34496+1
8 Aug 2026, 04:19495no change
7 Aug 2026, 16:10495first reading

Engagement

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

Reaction mix

697 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 37.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍26037.3%
❤24034.4%
🔥12417.8%
🥰223.16%
😁213.01%
❤‍🔥152.15%
😍101.43%
😢30.43%
🙏20.287%

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

Measured over the 16 most recent posts we hold, published 27 June 2026 to 26 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

26 Jul 2026, 12:09 UTC167 views38 reactionsread 8 August 2026
Photo

Показали по пути в Красноярск (на телефон из иллюминатора)

🔥23👍10❤5

24 Jul 2026, 18:36 UTC201 views32 reactionsread 8 August 2026
Photo

Я не такая, я жду трамвая...

👍15🥰8😁6🔥2❤1

21 Jul 2026, 19:09 UTC309 views46 reactionsread 8 August 2026
Photo

Через несколько секунд этот лось меня учуял и очень быстро исчез в лесу. Ну да все равно света не было

❤25👍11🔥8🥰2

15 Jul 2026, 19:06 UTC426 views48 reactionsread 8 August 2026
Photo

Ну вот и встретились два танка, два ферзя...

👍22❤19🥰7

14 Jul 2026, 18:07 UTC349 views49 reactionsread 8 August 2026
Photo

Эта маленькая мезенская лошадка, поселившаяся недавно в Чухраях, меня просто покорила

❤33👍16

13 Jul 2026, 18:41 UTC328 views50 reactionsread 8 August 2026
Photo

В Брянском лесу нынче сохраняют и восстанавливают не только маленьких крапчатых сусликов и огромных зубров. В Чухраях теперь пасутся табуны прекрасных мезенских лошадей.

🔥19👍17❤13❤‍🔥1

12 Jul 2026, 19:03 UTC299 views47 reactionsread 8 August 2026
Photo

(Рыбинск, Спасо-Преображенский собор) Намедни снова пытался снимать лосей в Ярославской области. Не очень успешно, так скажем. Но в этот раз добрался до города Рыбинска, и погулял по нему немного. Красивое 🙂 Только сирены воздушной тревоги очень громко орут над Волгой, мол, граждане, валите в укрытие (никто особо никуда не валил, да и некуда). Ехал обратно, навстречу кавалькада пожарных машин. Таксист: "видать, попал…

❤22👍13🔥6😢3🙏2❤‍🔥1

8 Jul 2026, 15:09 UTC356 views41 reactionsread 8 August 2026
Photo

Cейчас этот маленький крапчатый суслик наверное принял форму, близкую к идеальной (идеальной считается форма шара) и может быть уже залег в спячку :)

👍19😁15🥰4❤2🔥1

7 Jul 2026, 17:37 UTC360 views30 reactionsread 8 August 2026
Photo

Добираю недобранное ) Старый батумский пирс в феврале

👍25🔥5

6 Jul 2026, 16:11 UTC341 views39 reactionsread 8 August 2026
Photo

Простые вещи. Паутинка на ветке елочки росистым июльским утром

👍18❤12🔥9

5 Jul 2026, 20:22 UTC366 views52 reactionsread 8 August 2026
Photo

В ночь с пятницы на субботу поехал я в Ярославскую область в надежде поснимать лосей. Прогноз ничего хорошего не обещал, и ехал я всю дорогу под наползающей черной тучей, глядя на сужающийся просвет впереди. А когда уже подъезжал на рассвете к месту, тучи внезапно куда-то делись, небо очистилось и над полями заколыхались волны тумана. Но ко второй половине дня лафа кончилась, небо снова затянуло и начался проливной д…

❤28👍13🔥10🥰1

1 Jul 2026, 17:00 UTC371 views38 reactionsread 8 August 2026
Photo

На этом туман в то утро закончился

👍19❤12🔥7

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

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

“Alexey_Kharitonov” (@Kharit_on_off), 504 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/Kharit_on_off.

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.