Telegram RegisterThe public register of Telegram
Telegram profile photo for Мой код писал GPT

Channel

Мой код писал GPT

@gpt_wrote_my_code

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

851subscribers

+3 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002388434488
TypeChannel
Username@gpt_wrote_my_code
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/gpt_wrote_my_code

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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

848857852.58 August 2026 — 848 subscribers9 August 2026 — 848 subscribers17 August 2026 — 850 subscribers25 August 2026 — 854 subscribers1 September 2026 — 857 subscribers10 September 2026 — 851 subscribers8518 August 202610 September 2026
6 measurements spanning 33 days, net +3. 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 847–858 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 14:00851-6
1 Sept 2026, 12:44857+3
25 Aug 2026, 03:37854+4
17 Aug 2026, 10:36850+2
9 Aug 2026, 04:11848no change
8 Aug 2026, 18:47848first reading

Engagement

20 posts held, back to 28 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

300 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 62.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥18762.3%
4214.0%
🤣299.67%
🏆227.33%
🤯144.67%
😁51.67%
😱10.333%

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

Measured over the 20 most recent posts we hold, published 28 July 2026 to 5 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
1
of 19 we hold a reading for · 5%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @gpt_wrote_my_code. 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 20 most recent posts we hold for this entry, published 28 July 2026 to 5 August 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.

Recent posts

5 Aug 2026, 09:47 UTC313 views26 reactionsread 8 August 2026

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

🤯13🏆6🤣43

4 Aug 2026, 17:58 UTC370 views30 reactions2 Starsread 8 August 2026
Photo

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

🔥21🏆54

4 Aug 2026, 16:56 UTC406 views16 reactionsread 8 August 2026
Photo

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

🔥13🤣2😱1

4 Aug 2026, 12:15 UTC381 views10 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥5😁5

4 Aug 2026, 07:14 UTC396 viewsread 8 August 2026

Кто не верит, это реальное прохождение тестов перед интервью на вакансию Источник: https://t.me/gpt_wrote_code

4 Aug 2026, 07:07 UTC399 views22 reactionsread 8 August 2026
Photo

Отклики на хэхэ вышли на новый уровень

🤣22

3 Aug 2026, 12:39 UTC396 views11 reactionsread 8 August 2026

Тестовую группу набрали. Всем спасибо, кто откликнулся! В первые полчаса написали 10 человек. Видим интерес к этому, и сейчас будем дорабатывать платформу Напоминаю, что продукт будет доступен всем! 🙏

6🔥5

3 Aug 2026, 11:13 UTC396 views14 reactionsread 8 August 2026

Ищем тестовую группу ребят, которые готовы пройти наш новый бесплатный курс по Python + SQL. Вам будет выдан ранний доступ, и вы сможете протестить весь функционал курса. Нужны были скиллы в питоне + SQL для Data Engineer собеседований? Гоу к нам!

🔥131

3 Aug 2026, 10:54 UTC384 viewsread 8 August 2026

139 пользователей уже опробовали нашего бота! По-честному с некоторыми резюме возникали проблемы парсинга. Это было связано тем, что мы сделали универсальный парсинг под PDF, txt, docs и прочие форматы. Сейчас уже пофиксили много возникших проблем. Будем продолжать актуализировать прожарки бота под рынок. Нам важно, чтобы наше решение было топ на рынке в любую погоду. Спасибо, что вы с нами!

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

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

“Мой код писал GPT” (@gpt_wrote_my_code), 851 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/gpt_wrote_my_code.

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.