Telegram RegisterThe public register of Telegram

Channel

IanMatveev

@ian_matveev

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

65subscribers

+0 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-1001876813691
TypeChannel
Username@ian_matveev
DescriptionПишу теперь и тут.
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 live10 August 2026
Measurements held2
On Telegramt.me/ian_matveev

Growth

6510 Aug 2026, 09:16 — 65 subscribers10 Aug 2026, 09:30 — 65 subscribers10 Aug 2026, 09:1610 Aug 2026, 09:30
2 measurements taken within a single day. 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 64–66 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 09:3065no change
10 Aug 2026, 09:1665first reading

Engagement

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

What this channel posts

Photos
16
Videos
19
Links
1

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
4m 06s
Average length
41s

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

640 reactions across 13 posts, in 21 distinct kinds. The most used accounts for 47.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩30147.0%
🤡10015.6%
🤮589.06%
👍406.25%
🔥406.25%
🖕223.44%
💊142.19%
121.88%
👎111.72%
💯71.09%
😁71.09%
🤬60.938%
🤣50.781%
😢40.625%
👏30.469%
🥰30.469%
😈20.313%
🤩20.313%
😍10.156%
🙏10.156%
1 further kind10.156%

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

Measured over the 15 most recent posts we hold, published 16 February 2024 to 14 May 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

14 May 2026, 14:38 UTC86 viewsread 10 August 2026
Photo

❗️Саша Конь погиб под Брянском после удара дрона — СМИ. Мужчина шёл пешком из России в Южную Америку с 300-килограммовой повозкой. Свой путь он начал в Рязанской области, а дойти планировал аж до Бразилии.

12 Apr 2026, 18:02 UTC116 viewsread 10 August 2026

Раньше только Иран блокировал Ормузский пролив. Теперь по приказу Трампа США блокируют Ормузский пролив. Интересно, попросит ли он помощи у стран НАТО, чтобы и они начали блокировать Ормузский пролив?

19 Oct 2025, 20:11 UTC402 views11 reactionsread 10 August 2026

Считаю, что Уиткофф должен рассмотреть возможность уступки Великобритании города Нью-Йорк, так как он в основном англогоязычный

💊8💩2😁1

9 Mar 2025, 10:28 UTC≈1,100 views43 reactionsread 10 August 2026
Video

Украинский морской дрон запускает морской дрон поменьше. Интересная модификация. По сути получается беспилотный торпедный катер.

💩32🤡53🥰3

25 Feb 2025, 03:43 UTC≈1,140 views50 reactionsread 10 August 2026

Путин вышел рассказывать, что готов отдать США ресурсы. Лица Z-патриотов представили сейчас?

🖕22💩15🤡7😁4👏1💊1

4 Feb 2025, 06:15 UTC≈1,180 views24 reactionsread 10 August 2026

Очень любопытно, эти тарифные метания Трампа — спонтанные решения или часть заранее придуманного большого плана по формированию выгодных ему условий?

💩211👍1🙏1

12 Aug 2024, 06:24 UTC≈1,910 views64 reactionsread 10 August 2026
Video

На Запорожской АЭС не смогли выбрать нового папу PS: Это градирня. В ней охлаждается вода, когда станция работает. Гореть там нечему. Похоже, российские солдаты чет подложили туда и подожгли. Судя по дыму — это шины. Тупая провокация.

💩41💊5🤬5💯4🤡42👎2😁1

25 Jun 2024, 18:51 UTC≈2,000 views52 reactionsread 10 August 2026
Photo

Российский комплекс ПВО «Панцирь-С1» уничтожен ракетой HIMARS в Донецкой области. Ракета попала рядом и ЗРПК просто сгорел

💩37🔥8😢4👎2👍1

25 Jun 2024, 18:01 UTC≈1,660 views22 reactionsread 10 August 2026

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

💩211

25 Jun 2024, 18:00 UTC≈1,430 views18 reactionsread 10 August 2026

Судя по всему, произошло вот что. Ракета ATACMS летела к одной из военных целей, вероятно к аэродрому «Бельбек». На подлете к берегу ее перехватила российская зенитная ракета. Она поразила ATACMS и попадание осколков инициировали подрыв вышибного заряда, который и разбросал суббоеприпасы M74.

💩16👍2

25 Jun 2024, 18:00 UTC≈1,340 views16 reactionsread 10 August 2026
Video

Момент падения суббоеприпасов ракеты ATACMS на пляж в Крыму 23 июня. Не остается сомнений, что это не обломки ракеты ПВО, о чем писали некоторые каналы

💩13👎2👍1

20 Feb 2024, 16:53 UTC≈3,160 views84 reactionsread 10 August 2026
Video

Кадры из Авдеевки, разрушенной российскими войсками. При этом у пропаганды хватает безумия в двух соседних постах сначала писать, как мощно они бомбили ВСУ в Авдеевке, а затем горевать, как же Украина разрушила город

🔥29🤡28💩14👎3🤮3🤩2🤬1🤯1

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

Citation-graph rank

Citation-graph rank — 1,207,802 of 1,340,412entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“IanMatveev” (@ian_matveev), 65 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/ian_matveev.

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.