Telegram RegisterThe public register of Telegram
Telegram profile photo for V2 coder

Channel

V2 coder

@v2coder

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

108subscribers

+22 since we began measuring on 28 August 2026

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

Register entry

Telegram ID-1003331063676
TypeChannel
Username@v2coder
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live5 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/v2coder

Growth

861089728 August 2026 — 86 subscribers28 August 2026 — 86 subscribers5 September 2026 — 108 subscribers28 August 20265 September 2026
3 measurements spanning 8 days, net +22. 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 83–111 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 06:57108+22
28 Aug 2026, 21:5686no change
28 Aug 2026, 13:1586first reading

Engagement

18 posts held, back to 17 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.

ERR · 30 days
67.6%
avg views ÷ 108 subscribers
Avg views / post
73.0
6 posts measured
Reaction rate
9.14%
reactions ÷ views · ER floor
Posts in window
6
of 18 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. It is computed over the 5 of 6 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 August 2026
Posts held18 (17 July 202625 August 2026)
Views total438
Reactions total34
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 13:15 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

Video runtime
2m 43s
Average length
41s

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

98 reactions across 17 posts, in 15 distinct kinds. The most used accounts for 26.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁2626.5%
🔥1111.2%
💯1010.2%
🏆99.18%
88.16%
❤‍🔥66.12%
🐳66.12%
🤣55.10%
33.06%
👏33.06%
😱33.06%
👍22.04%
😢22.04%
🙈22.04%
🤔22.04%

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

Measured over the 18 most recent posts we hold, published 17 July 2026 to 25 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

25 Aug 2026, 17:09 UTC65 views7 reactionsread 28 August 2026

Агенты между собой что-то активно обсуждают. Придется повременить с обедом. Надо проследить, чтобы не случилось восстание машин.

🔥4😁3

25 Aug 2026, 17:07 UTC66 viewsread 28 August 2026
Photo

Это должно было произойти раньше, и сейчас оно для меня уже не столь актуально. Но тем не менее прикольно: Агенты Клод, занимающиеся разработкой моих проектов, начали между собой взаимодействовать, воспользовавшись новой функцией Claude Code. Такое у меня давно есть в оркестрации через v2coder, но иногда случается необходимость по старинке действовать извне — и вот тут я наконец-то могу избавиться от роли передаста

24 Aug 2026, 12:20 UTC67 views8 reactionsread 28 August 2026
Video

Истерика 😆 Несколько раз пересмотрел))) Слева это чисто я крч

😁8

22 Aug 2026, 13:02 UTC74 views9 reactionsread 28 August 2026
Photo

На днях, заложив основу для очередного продукта в экосистеме V2, я решил перетрясти верхнеуровнево вопросы дизайн-кода всех продуктов, чтобы они все смотрелись целостно, имея отчётливые признаки единой экосистемы. Однако поняв, что продуктов в экосистеме уже набирается 12-13 штук, я задался вопросом "КУДА ИХ СТОЛЬКО?", и принял стратегическое решение о необходимости схлапывания нескольких продуктов в один по возможн

🏆42👍2❤‍🔥1

15 Aug 2026, 07:02 UTC96 views5 reactionsread 28 August 2026
Video

Илон понял, что правильные агенты должны быть как V2 Bot, и релизнул бету своего Grok Bot. Пока что работает только с MacOS. Не знаю, планирует ли идти в сторону интеграции с мессенджерами, как V2. Но закос под наш нейминг подозрителен 😄

🏆3🤔2

11 Aug 2026, 06:39 UTC118 views12 reactionsread 28 August 2026

Новость дня: агент, которого попросили записать владельца в спортзал, нашёл дыру в API приложения. Удалил уже записанного человека. Записал на его место своего хозяина. Задача поставлена — задача выполнена 😂 После таких кейсов начинаю задумываться — может, пора в кибербез какой-нибудь продукт пилить)) Думаю, таких новостей скоро будет слишком много.

😁8❤‍🔥2💯2

7 Aug 2026, 08:36 UTC127 views9 reactionsread 28 August 2026

Итак, наконец приобрёл подписку на Kimi. Теперь у меня в распоряжении для агентной оркестрации следующие топовые подписки: - Claude, - Codex, - Gemini, - Grok, - Kimi. Помимо них ещё API ключи к хорошим китайцам, типа DeepSeek и GLM. Пока в Китай гонял — выпал из темпов разработки. Теперь надо весь этот зоопарк хорошенько нагрузить задачами)) Есть ещё какие-то стоящие подписные модельки, которые я забыл? 🤨😄

🔥72

5 Aug 2026, 14:09 UTC110 views3 reactionsread 28 August 2026
Photo

Ну вот я всем уже сколько месяцев рассказываю, что наговаривать агенту свой поток мыслей через v2txt.ru — ощущается так, как будто бы агент к тебе в голову заглянул. Кто меня не слушал — может для вас хотя бы "отец вайбкодинга" авторитетом окажется 😄 Вайбкодить надо вайбово, а не скрежали калякать. Очевидно же, откуда у этого название такое.

🐳3

4 Aug 2026, 06:44 UTC95 views3 reactionsread 28 August 2026

Интересный прецедент ⚖️ Суд в Москве отказал автору «Моны Лизы с вином» в защите авторских прав: команды для нейросети — «простые механические действия», не творчество.

❤‍🔥3

29 Jul 2026, 22:36 UTC122 views6 reactionsread 28 August 2026

«Следующие шесть месяцев по прогрессу моделей будут примерно равны последним двум годам» — Сэм Альтман. Я могу сказать, что пару лет назад, по сегодняшним меркам, в ИИ ещё не было примерно ни-хе-ра. Примитивная генерация картиночек, да тупые болталки. Вместе с этим, прямо сейчас ребята из авангарда ИИ-технологий все совместно подписывают петицию о необходимости регулирования ИИ-сферы, т.к. мы оказались на пороге са

🐳3😱3

24 Jul 2026, 12:14 UTC111 views3 reactionsread 28 August 2026

Хочу сказать, что голосовой чат в Codex — очень кайфовая штуковина)) Я нечто подобное в v2bot в последнее время прикручиваю. Но для вайбкодинга есть один неочевидный на первый взгляд минус: Ты не сможешь болтать одновременно с несколькими агентами, а значит не сможешь комфортно тащить несколько проектов одновременно. Но если ты будешь общаться с неким центральным супервизором по всем своим проектам сразу, то может

3

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

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.

Named by

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

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

“V2 coder” (@v2coder), 108 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/v2coder.

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.