Telegram RegisterThe public register of Telegram
Telegram profile photo for Ivan Dobromyslov🍃

Channel

Ivan Dobromyslov🍃

@ivan_dobromyslov67

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

1,864subscribers

+15 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001775967005
TypeChannel
Username@ivan_dobromyslov67
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/ivan_dobromyslov67

Topic

Travel — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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

1,8471,8661,856.57 August 2026 — 1,849 subscribers7 August 2026 — 1,849 subscribers11 August 2026 — 1,847 subscribers14 August 2026 — 1,848 subscribers17 August 2026 — 1,849 subscribers20 August 2026 — 1,852 subscribers24 August 2026 — 1,866 subscribers27 August 2026 — 1,863 subscribers30 August 2026 — 1,862 subscribers2 September 2026 — 1,861 subscribers7 September 2026 — 1,862 subscribers11 September 2026 — 1,861 subscribers15 September 2026 — 1,864 subscribers1,8647 August 202615 September 2026
13 measurements spanning 39 days, net +15. 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 1,844–1,869 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 08:591,864+3
11 Sept 2026, 19:581,861-1
7 Sept 2026, 00:181,862+1
2 Sept 2026, 08:341,861-1
30 Aug 2026, 12:441,862-1
27 Aug 2026, 08:351,863-3
24 Aug 2026, 15:231,866+14
20 Aug 2026, 21:031,852+3
17 Aug 2026, 16:371,849+1
14 Aug 2026, 17:241,848+1
11 Aug 2026, 15:041,847-2
7 Aug 2026, 17:331,849no change
7 Aug 2026, 17:191,849first reading

Engagement

16 posts held, back to 3 July 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
9s
Average length
9s

Measured directly from 1 video 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

2,169 reactions across 16 posts, in 26 distinct kinds. The most used accounts for 23.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥49923.0%
👍35116.2%
❤‍🔥31514.5%
😍29113.4%
🥰1707.84%
custom 5362042093806068445823.78%
custom 5375317507005493820562.58%
custom 5397987658653796335512.35%
custom 5778406621596094695421.94%
custom 5201811024499470222411.89%
custom 5420328579583991095411.89%
custom 5420284654953453153361.66%
custom 5425052755846785687331.52%
custom 5364105417569868801251.15%
custom 6003749176066706814231.06%
custom 5404838161555661329210.968%
custom 5287394058963009252180.83%
custom 5445146051671497117150.692%
custom 5449850741667668411130.599%
custom 5363985003866769909100.461%
6 further kinds361.66%

Custom emoji. 15 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 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 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 2,169 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 3 July 2026 to 7 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

7 Aug 2026, 09:38 UTC268 views91 reactionsread 7 August 2026
Photo

Маскируется или прячется от дождя… Вас как, не заливает?🌧️ Болотная сова (Asio flammeus) 🦉Иван Добромыслов

🥰28custom 542032857958399109526custom 544514605167149711715🔥11👍7❤‍🔥2😍2

4 Aug 2026, 07:56 UTC522 views62 reactionsread 7 August 2026
Photo

✴️✴️✴️✴️✴️ Эта поездка на Кавказ получилась особенной, поскольку во-первых, в горах иначе не может быть, а во-вторых, получилось охватить довольно много локаций: Домбай, Архыз, Приэльбрусье. Посмотрели и на озера, и на величественный Эльбрус, и с сусликами познакомились. Самое запоминающееся место для меня- долина реки Малая Дукка с березовым криволесьем и рододендронами. Лазали по каменным россыпям и осыпающимся ск

👍25custom 528739405896300925218❤‍🔥10🔥6😁3

2 Aug 2026, 11:13 UTC565 views100 reactionsread 7 August 2026
Video

А где ваши лучшие места? 🗺 Пусть этот кусочек весны 2026 останется тут😌

🔥46custom 536410541756986880125👍19custom 54250527558467856876custom 53642381621240847934

1 Aug 2026, 18:22 UTC665 views181 reactionsread 7 August 2026
Photo

Все любят сов. Давно их не было. Исправляюсь🤷‍♀️ Болотная сова (Asio flammeus) 🦉Иван Добромыслов

😍57❤‍🔥44🔥34custom 600374917606670681423custom 542032857958399109515🥰7👍1

19 Jul 2026, 16:01 UTC≈1,060 views146 reactionsread 7 August 2026
Photo

Молочная река Кавказа😍 Рододендрон кавказский (лат. Rhododendron caucasicum) ⛰ Иван Добромыслов

👍58❤‍🔥45🥰22custom 54202846549534531539custom 52242720670749983026😍4🔥2

18 Jul 2026, 10:13 UTC955 views154 reactionsread 7 August 2026
Photo

Тихое апрельское утро с парой чомг😍 Как же мне нравится этот небольшой период, когда в природе всё просыпается, зеленой листвы еще нет. В полях поют жаворонки, на лесной опушке хоркает вальдшнеп, с озера доносятся покрякивания гоголей, а утром трубят журавли. В это время ощущаю жизнь по-особенному😌 Чомга (Podiceps cristatus) 🪶Иван Добромыслов

🔥57😍40custom 542028465495345315327👍15❤‍🔥11🥰4

15 Jul 2026, 18:54 UTC≈1,080 views164 reactionsread 7 August 2026
Photo

Небесные огни севера😍 Кольский п-ов, март 🤩Иван Добромыслов

🔥56custom 539798765865379633551😍33👍14❤‍🔥9🥰1

13 Jul 2026, 19:07 UTC959 views118 reactionsread 7 August 2026
Photo

Призрачный исполин🫣 Не соскучились по зиме? 🏔Пермский край, Помяненный камень 🗻 Иван Добромыслов

❤‍🔥44👍28custom 540483816155566132921🔥15😍10

12 Jul 2026, 18:20 UTC≈1,090 views165 reactionsread 7 August 2026
Photo

С днём фотографа📸

🔥77custom 577840662159609469541👍30custom 60124035523480155246😍5❤‍🔥4😁2

11 Jul 2026, 15:44 UTC918 views97 reactionsread 7 August 2026
Photo

✴️✴️✴️✴️✴️✴️✴️✴️ ✴️✴️✴️✴️✴️✴️ Такой вот фрагментик с горной речки. Кто подскажет, как правильно назвать подобный жанр? Не интимный ли пейзаж🧐 Вода размыта нарочно выставленной длинной выдержкой. Так как-то помягче и поинтереснее смотрится☺️ ⛰ Иван Добромыслов

🔥33😍26custom 544985074166766841113👍10custom 536398500386676990910❤‍🔥4😁1

9 Jul 2026, 15:42 UTC899 views153 reactionsread 7 August 2026
Photo

Морозным апрельским утром🌟 Чудесное время, в которое всегда хочется возвращаться😍🥹 Тетерев (лат. Lyrurus tetrix) 🪶Иван Добромыслов

🔥54❤‍🔥44custom 542505275584678568727👍16😍8🥰4

8 Jul 2026, 11:01 UTC958 views147 reactionsread 7 August 2026
Photo

🔤🔤🔤🔤🔤🔤❤️ Как и другие поганки, красношейные имеют в своем арсенале брачные танцы на воде. Помимо синхронных движений, птицы ныряют и достают водоросли, которые преподносят своему партнеру🤗 Красношейная поганка (лат. Podiceps auritus) 🦆 Иван Добромыслов

🥰53custom 536204209380606844540❤‍🔥26👍15🔥11😍2

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

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

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“Ivan Dobromyslov🍃” (@ivan_dobromyslov67), 1,864 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/ivan_dobromyslov67.

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.