Telegram RegisterThe public register of Telegram
Telegram profile photo for Владилен: IT в эпоху AI

Channel

Владилен: IT в эпоху AI

@vladm

2 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

39,328subscribers

-313 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001161464837
TypeChannel
Usernames@js_by_vladilen @vladm
DescriptionПишу о том, как AI меняет работу, продукты и жизнь разработчиков. Тестирую инструменты, строю свои системы и делюсь тем, что действительно работает. Владилен Минин Реклама: @vlad_0045 Live канал: @minin_live РКН: http://bit.ly/4epHOdZ
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held126
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/vladm

Topic

Technology — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@vladm/1561 · this entry22 Jul 2026, 11:56 UTC@result_jfd/265222 Jul 2026, 11:56 UTC1.00under a minute
@vladm/1567 · this entry30 Jul 2026, 11:02 UTC@result_jfd/265630 Jul 2026, 11:02 UTC1.00under a minute
@result_jfd/266013 Aug 2026, 17:47 UTC@vladm/1576 · this entry13 Aug 2026, 17:59 UTC1.0012 minutes
@vladm/1586 · this entry29 Aug 2026, 16:24 UTC@result_jfd/266230 Aug 2026, 07:40 UTC1.0015 hours
@vladm/1590 · this entry2 Sept 2026, 10:16 UTC@result_jfd/26642 Sept 2026, 11:08 UTC1.0052 minutes
@vladm/1611 · this entry16 Sept 2026, 14:16 UTC@result_jfd/266816 Sept 2026, 14:16 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@result_jfd13 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (12–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 91 comparable posts for this entry, running 3 July 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @result_jfd. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

39,17739,64239,409.539,3286 August 202611 November 2026
126 measurements spanning 97 days, net -313. 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 39,107–39,712 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 126
Measured (UTC)SubscribersChange
11 Nov 2026, 07:3739,328+11
10 Nov 2026, 02:1739,317-8
8 Nov 2026, 17:5839,325+6
8 Nov 2026, 01:1839,319+2
7 Nov 2026, 13:0139,317-9
7 Nov 2026, 02:2039,326+2
6 Nov 2026, 14:4439,324+6
5 Nov 2026, 16:4839,318+1
5 Nov 2026, 01:0539,317+2
4 Nov 2026, 20:0739,315-4
4 Nov 2026, 00:4039,319+8
3 Nov 2026, 17:2039,311+5
2 Nov 2026, 22:2039,306+3
2 Nov 2026, 17:3539,303-4
2 Nov 2026, 00:3539,307-2
1 Nov 2026, 14:1639,309+3
1 Nov 2026, 01:2739,306+4
31 Oct 2026, 12:1039,302+5
30 Oct 2026, 22:1439,297-1
30 Oct 2026, 13:0839,298first reading

Engagement

107 posts held, back to 2 July 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 187 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
21.6%
avg views ÷ 39,328 subscribers
Avg views / post
8,480
28 posts measured
Reaction rate
1.07%
reactions ÷ views · ER floor
Posts in window
28
of 107 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held107 (2 July 2026 – 11 November 2026)
Views total237,370
Reactions total2,541
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 10:24 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
519
Videos
127
Links
624

Lifetime counters from Telegram’s own channel header, read 11 November 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
14m 34s
Average length
51s

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

7,740 reactions across 105 posts, in 9 distinct kinds. The most used accounts for 34.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2,67134.5%
❤1,91224.7%
😁1,23215.9%
custom 539787937393833103484010.9%
🤯5146.64%
👏4145.35%
🏆710.917%
💔650.84%
🤩210.271%

Custom emoji. One 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 count beside it is 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 105 of the 107 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 7,740 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 107 most recent posts we hold, published 2 July 2026 to 11 November 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
238
across the posts below
Posts paid on
99
of 105 we hold a reading for · 94%
Most on one post
25
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @vladm. 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 107 most recent posts we hold for this entry, published 2 July 2026 to 11 November 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.

Advertising

Ad load
1.87%
2 of 107 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
6,980
over 2 measured posts
Median views · rest
9,080
over 103 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2SDnjeR6WVy11 September 20261 September 2026
2SDnjecba8s124 August 202624 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 107 most recent posts we hold, published 2 July 2026 to 11 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 11 of 28 posts held from the last 30 days (39.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 09:52 UTC≈1,440 views7 reactionsread 11 November 2026
Photo

Что уже построили на Fable 5.2: игры, 3D-миры, электроника 9 ноября вышел Fable 5.2, а потому тестируем. В видео покажу что УЖЕ сделали на Fable (6 примеров, включая шутер). Разберемся с бенчмарками. Подробный разбор новых effort, как выбирать модели, цены и где эффективно применять модель. Также покажу свой пример, когда по 1 запросу Fable создала 6 впечатляющих демо и поговорим про то, как такие модели влияют н…

🔥4custom 53978793739383310342🤯1

11 Nov 2026, 05:16 UTC≈3,620 views92 reactionsread 11 November 2026
Photo

К слову о Китае – он играет на совершенно другом уровне Вы же видите этот паттерн?) В связи с этим считаю важным сообщить, что стратегически важно переходить нам всем в OpenAI, потому что Сэм Альтман в безопасности от восточного влияния. Если вы понимаете о чем я...

😁82❤4💔3🤯3

10 Nov 2026, 14:09 UTC≈4,880 views49 reactions4 Starsread 11 November 2026
Photo

Как удешевить Claude Code до 40 раз: Opus + Haiku Показываю вам свою рабочую связку: как настроить проект в Claude, который будет эффективен до 40 раз по токенам. Кстати, вместо Claude может быть Codex – принцип схожий. Мы настраиваем умного оркестратора и систему дешевых субагентов, которые делают ревью и пишут код. Проект представляет из себя мини-харнес с самообучением. И настраивается он буквально минут 10. П…

🔥30😁8❤6custom 53978793739383310345

10 Nov 2026, 14:09 UTC≈4,630 views19 reactions12 Starsread 11 November 2026
File

Дополнительные материалы к видео про оптимальный Claude В проекте уже все настройки, адаптируйте под свой проект Схемы из видео

❤9🔥8👏2

10 Nov 2026, 05:05 UTC≈5,480 views70 reactions3 Starsread 11 November 2026
Photo

Китайские модели — лучшие Правда, стоит уточнить, какие именно модели. Сейчас в сети жуткий скандал с CEO NVIDIA — Дженсеном Хуангом. Его спалили, и он уже публично признался в измене с китайской красоткой, которую в сети величают китайским шпионом — Элис Хуанг Куча мемов, споров. Компания, производящая видюхи и ИИ-чипы, теряет 7% — сотни миллиардов долларов. Но есть такое впечатление, что это осознанный вброс д…

😁57❤8🔥3custom 53978793739383310342

9 Nov 2026, 15:57 UTC≈5,670 views25 reactions1 Starread 11 November 2026
Photo

Меня в рабочих чатах больше всего бесит то, что, блин, их просто огромное количество. Одному человеку ответил, он сейчас не на связи. Переключился на другой чат, а там уже другой контекст. Тут первый вернулся с ответом, параллельно что-то написал сотрудник в третьем. И ты постоянно между всем этим переключаешься. По факту информация теряется. Всё где-то есть, но единого места, где можно нормально найти нужное и разо…

😁12❤5👏5💔2🔥1

9 Nov 2026, 10:11 UTC≈6,030 views70 reactions1 Starread 11 November 2026
Photo

В конце этого года мы увидим свой Чернобыль Знакомьтесь – Джеффри Хинтон. В сети его называют крестный отец ИИ (нейронок). Один из учёных, заложивших фундамент современных нейросетей. В 2024 году получил нобелевскую премию. Про него подробней писал тут и тут. И вот недавно Мистер Хинтон в интервью The Guardian выдает такую имбу: В конце этого года или в следующем мы увидим свой Чернобыль, и, возможно, этого хватит…

😁30🔥21custom 539787937393833103411❤3🤯3👏2

6 Nov 2026, 11:52 UTC≈7,440 views59 reactions6 Starsread 11 November 2026
Photo

ИИ всё объяснил. Почему в голове пусто? С появлением ИИшки очень высокий соблазн делегировать ему наше умение думать. Мы спокойно можем получить готовые ответы из любой области, ИИ прекрасно решает задачи и делает это автоматизированно. Он может очень складно давать нам ответы и поддерживать любые наши идеи. Но это чревато последствиями. Как минимум потому, что он не несет никакой ответственности.. В отличии от нас…

🔥39❤11custom 53978793739383310347🤯2

3 Nov 2026, 12:19 UTC≈10,200 views89 reactions2 Starsread 11 November 2026
Photo

Мне заблокировали Claude. Один запрос — и он снова меня знает Мы строили второй мозг неправильно, а потому ловите обещанный ролик. Внутри объясняю как у меня работает система Second Brain 2.0. Абсолютно автономно, с любыми источниками информации, моментально выдает информацию, строит графы и понимает весь контекст с учетом времени – практически бесплатно. В видео я показал несколько прикладных кейсов как у меня эт…

❤48🔥22custom 539787937393833103414👏2😁2🏆1

31 Oct 2026, 09:24 UTC≈11,400 views485 reactions8 Starsread 11 November 2026
Voice message

Пару мыслей на счет блокировки Claude

🔥394custom 539787937393833103446❤36🏆3👏3😁3

31 Oct 2026, 09:12 UTC≈10,800 views65 reactions4 Starsread 11 November 2026
Photo

Я с вами теперь перехожу на SimpleClaw 🤝

😁43💔10❤9🏆3

30 Oct 2026, 12:13 UTC≈10,200 views35 reactions1 Starread 11 November 2026

Добавили голос в SimpleClaw 🎙 Теперь через наш API можно переводить голос в текст и озвучивать текст. Обе функции работают через API-ключ SimpleClaw. Например, можно подключить это к своему Telegram-боту: наговариваешь задачу, агент получает текст, обрабатывает запрос, а его ответ приходит голосом. Удобно, когда идёшь куда-то и печатать вообще не хочется. Или собрать автоматизацию, которая превращает твои голосовы…

🔥20🏆8❤7

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

Posts edited after publishing

@vladm edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
21 August 2026
Most recent edit
4 September 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @vladm as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
26 August 2026
Most recent seen missing
22 October 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
1

Forward network

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

Named by 7 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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Осознанная Меркантильность | Антон Назаров
@m0rtymerr_channel · 80,638
#1
Уставший техдир
@tired_glebmikheev · 18,460
#2
Max [RED Group x htmllessons]
@redgroup · 7,902
#3
Frontender's notes [ru]
@frontendnoteschannel_ru · 30,750
#4
Result: IT в эпоху AI
@result_jfd · 6,707
#5
Zar Zakharov | Lead Developer
@zarzakharov · 4,435
#6
Rozetked
@rozetked · 646,921
#7
Digital Ниндзя
@digital_ninjaa · 41,032
#8
PurpleSchool - обучение frontend, backend, devops, mobile
@purple_code_channel · 7,612
#9
Один день айтишника
@one_IT_day · 13,045
#10
Kobezzza. База в программировании
@kobezzza_channel · 3,960
#11
Frontend | Вопросы собесов
@easy_javascript_ru · 17,284
#12
FrontEndDev
@front_end_dev · 25,428
#13
Код.ру
@d_code · 405,458
#14
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,611
#15
Веб-страница
@tproger_web · 22,155
#16
Деплой | Ваня Ботанов
@dev_yttg · 7,190
#17
Yandex for Frontend
@yandex4frontend · 10,816
#18
Евгений Паромов
@cleanfrontend · 3,633
#19
Диджитализируй!
@t0digital · 28,616
#20
mefody.dev
@mefody_dev · 5,386
#21
Node.JS [ru] | Серверный JavaScript
@we_use_js · 10,605
#22
🧊 siberiacancode x IT-ХОЗЯЕВА
@siberiacancode · 3,427
#23
Senior Software Vlogger
@seniorsoftwarevlogger · 22,727
#24
CodeCamp
@codecamp · 177,564
#25
Ilnur Ryazhapov Frontend
@ilnur_ryazhapov_blog · 3,113
#26
КИРИЛЛ ПОЗДНЯКОВ | ДЖАВАСКРИПТИЗЕРЫ
@jswrl · 5,972
#27
Programmer & IT Memes
@itmemes · 121,903
#28
Руслан Куянец | Reactify x YeaHub
@reactify_IT · 6,259
#29
Result University
@result_school_it · 3,809
#30
Александр Белькевич </> Frontend вдохновляет
@front_everyday · 1,687
#31
JavaScript Job | Вакансии | Стажировки
@JScript_jobs · 12,752
#32
Типичный программист
@tproger · 78,009
#33
Хабр
@habr_com · 134,497
#34
Програмысли - Михаил Фленов
@mflenov · 4,932
#35
IT Юмор
@ithumor · 60,047
#36
Елена Литвинова — про путешествия, бег, программирование 🛸
@webelart · 2,116
#37
The ExtremeCode Times
@extremecode · 35,840
#38
В АйТи из Уфы | Раушан Каримов
@nashuarit · 1,022
#39
Саня об IT 👨🏻‍💻 Frontend ментор
@sanya_ob_it · 2,533
#40
Галера Морева
@gmoreva · 4,911
#41
Настоящий JavaScript
@true_js · 5,793
#42
Организованное программирование | Кирилл Мокевнин
@orgprog · 16,803
#43
IT-KAMASUTRA.COM
@itkamasutra · 6,013
#44
Анна Блок | FrontendBlok
@frontendblok · 6,831
#45
IT Отец. Заметки техлида
@it_father · 5,034
#46
Frontend по-флотски 👨‍💻 | AI & Modern Dev
@frontend_pasta · 4,425
#47
Андрей Смирнов | Викенд в IT
@itsmirnov · 7,263
#48
Frontend Portal
@FrontendPortal · 36,268
#49
Misha - Frontend Dev
@m1sha_frontend · 3,176
#50
Стародубцев x IT-ХОЗЯЕВА
@strdub · 3,942
#51
React Job | JavaScript | Вакансии
@job_react · 16,822
#52
Frontender Libs - обзор библиотек JS / CSS
@sWebDev · 7,338
#53
Гайды по JavaScript | Программирование
@guides_js · 7,071
#54
Будни разработчика
@htmlshit · 14,341
#55
React JS
@react_tg · 16,049
#56
Катерина | Про Frontend
@katerina_profrontend · 2,799
#57
АйТи Синяк
@it_sin9k · 2,149
#58
Миша Ларченко – о программировании и не только
@larchanka · 4,533
#59
xCode Journal
@xCode_Journal · 13,767
#60
Alek OS
@Alek_OS · 32,292
#61
JavaScript заметки
@notesjs · 7,359
#62
Артём Шумейко
@artemshumeiko · 19,769
#63
Мир ИТ c Антоном Павленко
@worlditech · 7,264
#64
Frontend Interview - собеседования по Javascript / Html / Css
@frontendInterview · 10,249
#65
Эксплойт
@exploitex · 2,022,997
#66
Путь волка к six pack | Антон Назаров
@nazarov_life · 7,141
#67
Алексей Шевцов
@jolybells · 357,371
#68
ВИЛСАКОМ РЕД / WYLSACOM RED
@wylsared · 1,088,291
#69
Бэкдор
@whackdoor · 1,538,229
#70
Артемий Лебедев
@temalebedev · 968,108
#71
СТАС БОМБИТ
@ikakprosto · 322,499
#72
NN
@naebnet · 2,177,859
#73
Сова пишет…
@sergeysova · 2,983
#74
artalog
@artalog · 4,235
#75
Антонов такой Антонов
@auantonov · 321,546
#76
Дудь
@yurydud · 849,220
#77
Frontend | Вакансии
@frontend_vakansii · 15,056 (as read 30 August 2026)
#78
UzDev Jobs – IT Jobs
@uzdev_jobs · 26,206
#79
Javascript jobs — вакансии по фронтенду, джаваскрипт, React, Angular, Vue
@jsdevjob · 9,749
#80
Что-то происходит
@smthisgoingon · 2,677
#81
S0ER
@softwareengineervlog · 10,361
#82
GitHub Community
@github · 154,995
#83
Рефералки в IT | Вакансии и резюме
@refer_me_it · 31,764
#84
Фрагменты
@hrdmx · 925
#85
JavaScript | LeetCode
@easy_frontend_task · 8,179
#86
Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 18,893
#87
Ayub Begimkulov - уроки по JS
@ayub_begimkulov_coding · 2,782
#88
🦊 Angular Fox 🚀 — русскогорящие новости сообщества
@angular_fox · 4,084
#89
Кошачья Бацыла
@koshachyabacyla · 14,584
#90
Senior Frontend - javascript, html, css
@seniorFront · 23,475
#91
Javascript
@javascriptv · 16,664
#92
@yegor256 news
@yegor256news · 9,492
#93
Николай Тузов
@ntuzov · 16,905
#94
Двач
@dvachannel · 969,125
#95
Волчьи следы
@nazarov_travel · 4,815
#96

Read from Telegram’s recommendation API, most recently 30 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Осознанная Меркантильность | Антон Назаров
@m0rtymerr_channel · 80,638
Telegram ranks this channel #9 of 87 here — alongside 86 others — read 18 August 2026
Digital Ниндзя
@digital_ninjaa · 41,032
Telegram ranks this channel #11 of 91 here — alongside 90 others — read 30 August 2026
Frontender's notes [ru]
@frontendnoteschannel_ru · 30,750
Telegram ranks this channel #13 of 95 here — alongside 94 others — read 6 September 2026
Веб-страница
@tproger_web · 22,155
Telegram ranks this channel #15 of 96 here — alongside 95 others — read 20 September 2026
Alek OS
@Alek_OS · 32,292
Telegram ranks this channel #17 of 95 here — alongside 94 others — read 4 September 2026
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,611
Telegram ranks this channel #19 of 93 here — alongside 92 others — read 25 September 2026
Диджитализируй!
@t0digital · 28,616
Telegram ranks this channel #27 of 88 here — alongside 87 others — read 9 September 2026
АйТиБорода
@itbeard · 19,001
Telegram ranks this channel #29 of 93 here — alongside 92 others — read 3 October 2026
Артём Шумейко
@artemshumeiko · 19,769
Telegram ranks this channel #33 of 92 here — alongside 91 others — read 29 September 2026
FrontEndDev
@front_end_dev · 25,428
Telegram ranks this channel #35 of 95 here — alongside 94 others — read 13 September 2026
Code Ready | Frontend
@code_ready · 21,534
Telegram ranks this channel #49 of 89 here — alongside 88 others — read 23 September 2026
Рефералки в IT | Вакансии и резюме
@refer_me_it · 31,764
Telegram ranks this channel #49 of 89 here — alongside 88 others — read 7 September 2026
Мэйхэм 🇬🇧
@maYhemEng · 27,524
Telegram ranks this channel #51 of 73 here — alongside 72 others — read 10 September 2026
Frontend Portal
@FrontendPortal · 36,268
Telegram ranks this channel #56 of 90 here — alongside 89 others — read 1 September 2026
Senior Frontend - javascript, html, css
@seniorFront · 23,475
Telegram ranks this channel #62 of 89 here — alongside 88 others — read 17 September 2026
Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 18,893
Telegram ranks this channel #67 of 90 here — alongside 89 others — read 2 October 2026
Fullstack / Software Job Offers
@runello_rus_webdevelopment · 24,176
Telegram ranks this channel #79 of 93 here — alongside 92 others — read 17 September 2026

This channel appears in 17 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Владилен: IT в эпоху AI” (@vladm), 39,328 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/vladm.

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.