Вайбкодер поставил задачу Fable 5.2 сделать игру пинг-понг и позволил нейронке «дать волю фантазии» — теперь это кошмар для эпилептика Если не боитесь, то поиграть можно — тут. Мы в МАХ 🤩
❤66😁19😢2👨💻1

Channel
@chatgptv
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · View velocity · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Domains linked from posts · Cite this entry
1,885,639subscribers
-20,688 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001848122804 |
|---|---|
| Type | Channel |
| Username | @chatgptv |
| Description | Медиа об IT, трендах, технологиях и нейросетях. Самое интересное тут! Реклама: @antosha_antosha РКН: https://vk.cc/cIwgBQ Работаем с сервисом BidFox |
| Created | 25 November 2022 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/chatgptv |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
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.
Posts published here appear in near-verbatim form on 8 other registered channels. This entry also sits inside a group of 5 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @chatgptv/11609 · this entry6 Aug 2026, 08:49 UTC | @cerb_news/14866 Aug 2026, 20:00 UTC | 1.00 | 11 hours |
| @chatgptv/11639 · this entry9 Aug 2026, 07:33 UTC | @cerb_news/15119 Aug 2026, 16:04 UTC | 1.00 | 8.5 hours |
| @chatgptv/11640 · this entry9 Aug 2026, 12:02 UTC | @cerb_news/152210 Aug 2026, 14:04 UTC | 1.00 | 26 hours |
| @chatgptv/11655 · this entry11 Aug 2026, 12:09 UTC | @cerb_news/154212 Aug 2026, 16:01 UTC | 1.00 | 28 hours |
| @chatgptv/11673 · this entry13 Aug 2026, 05:40 UTC | @cerb_news/154713 Aug 2026, 14:01 UTC | 1.00 | 8.3 hours |
| @chatgptv/11733 · this entry19 Aug 2026, 09:57 UTC | @cerb_news/163320 Aug 2026, 18:00 UTC | 1.00 | 32 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @cerb_news | 28 (8/8 hand-verifiable sample passed) | 0.99 | 24 hours | this entry (28–0) |
| @gptpublic | 16 (8/8 hand-verifiable sample passed) | 1.00 | 5.9 hours | this entry (16–0) |
| @matryoshka_io | 10 (8/8 hand-verifiable sample passed) | 0.94 | 5.6 hours | this entry (10–0) |
| @FerixdiJournal | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (9–0) |
| @TheTechBrief | 7 (7/7 hand-verifiable sample passed) | 0.95 | 88 minutes | this entry (7–0) |
| @aitechc | 7 (7/7 hand-verifiable sample passed) | 1.00 | 45 hours | this entry (7–0) |
| @dawnnewerapress | 6 (6/6 hand-verifiable sample passed) | 1.00 | 65 minutes | this entry (6–0) |
| @InnovateITNow | 6 (6/6 hand-verifiable sample passed) | 1.00 | 65 minutes | this entry (6–0) |
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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 5,848 comparable posts for this entry, running 8 April 2023 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.
Of the group of 5 channels, the one whose matching posts we hold earliest is @chatgptv — which is this entry. That is a statement about our reading window, not a claim of authorship.
On 5 of the 218 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0046 reactions per view.
| Post | Over | Views | Reactions | Expected |
|---|---|---|---|---|
| /1232518 Oct 2026, 11:46 UTC | 35 minutes | 13,900 → 16,200at least +2,200 | 70 → 71at most +2 | +10.2 |
| /1241825 Oct 2026, 07:50 UTC | 34 minutes | 10,700 → 13,000at least +2,200 | 43 → 44at most +2 | +10.2 |
| /1244127 Oct 2026, 13:24 UTC | 51 minutes | 16,100 → 19,500at least +3,300 | 41 → 41at most +1 | +15.2 |
| /1246530 Oct 2026, 09:13 UTC | 34 minutes | 12,400 → 14,900at least +2,400 | 46 → 47at most +2 | +11.1 |
| /125347 Nov 2026, 05:46 UTC | 35 minutes | 10,700 → 13,500at least +2,700 | 29 → 29at most +1 | +12.5 |
Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).
What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.
Recorded under the keys clone_source · view_reaction_decoupling, 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.
This channel is in a group of 5 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 23:07 | 1,885,639 | +52 |
| 8 Nov 2026, 11:05 | 1,885,587 | -1 |
| 7 Nov 2026, 03:17 | 1,885,588 | -347 |
| 6 Nov 2026, 02:17 | 1,885,935 | +588 |
| 4 Nov 2026, 22:55 | 1,885,347 | -631 |
| 3 Nov 2026, 23:37 | 1,885,978 | -572 |
| 3 Nov 2026, 01:58 | 1,886,550 | -109 |
| 2 Nov 2026, 00:36 | 1,886,659 | -738 |
| 31 Oct 2026, 22:55 | 1,887,397 | +174 |
| 30 Oct 2026, 19:47 | 1,887,223 | -339 |
| 29 Oct 2026, 17:08 | 1,887,562 | +223 |
| 28 Oct 2026, 14:37 | 1,887,339 | +532 |
| 27 Oct 2026, 17:00 | 1,886,807 | +420 |
| 26 Oct 2026, 16:48 | 1,886,387 | +1,406 |
| 25 Oct 2026, 14:26 | 1,884,981 | +2,184 |
| 24 Oct 2026, 13:28 | 1,882,797 | +1,449 |
| 23 Oct 2026, 12:36 | 1,881,348 | +1,383 |
| 22 Oct 2026, 10:19 | 1,879,965 | +797 |
| 21 Oct 2026, 05:09 | 1,879,168 | +206 |
| 20 Oct 2026, 01:30 | 1,878,962 | first reading |
7,978 posts held, back to 25 November 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 1,396 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 7,978 (25 November 2022 – 11 November 2026) |
| Views total | 7,594,100 |
| Reactions total | 39,073 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 20:45 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.
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. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 219 of this channel’s own posts over the last 30 days: across 211 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 4.1 hours of being posted; a typical post has already reached 29.4% of its 24-hour view count within the first hour, and 73.6% within the first six; the median 24-hour reach across those posts is 27,300 views — 1.45% of this channel’s own subscriber count (90th percentile 31,800).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /1257311 Nov 2026, 17:42 UTC | 718 minutes – 3.0 hours old | 13,200 views ~88 reactions | 60 minutes: 8,172 interp. → 3.0 hours: 13,200still climbing at last reading | not yet at 24h | 39 minutesprovisional — final view count still climbing |
| /1257211 Nov 2026, 15:45 UTC | 116 minutes – 5.0 hours old | 20,400 views ~221 reactions | 60 minutes: 8,741 interp. → 3.0 hours: 16,821 interp.still climbing at last reading | not yet at 24h | 82 minutesprovisional — final view count still climbing |
| /1257111 Nov 2026, 14:20 UTC | 1364 seconds – 6.4 hours old | 23,200 views ~119 reactions | 60 minutes: 9,418 interp. → 3.0 hours: 18,400 → 6.0 hours: 22,800still climbing at last reading | not yet at 24h | 83 minutesprovisional — final view count still climbing |
| /1257011 Nov 2026, 10:55 UTC | 1911 minutes – 9.8 hours old | 26,400 views ~164 reactions | 60 minutes: 7,971 interp. → 3.0 hours: 13,600 → 6.0 hours: 22,600still climbing at last reading | not yet at 24h | 2.7 hoursprovisional — final view count still climbing |
| /1256911 Nov 2026, 08:21 UTC | 2329 minutes – 12 hours old | 27,200 views ~206 reactions | 60 minutes: 9,526 interp. → 3.0 hours: 16,520 interp. → 6.0 hours: 21,200 → 12 hours: 27,100still climbing at last reading | not yet at 24h | 2.2 hoursprovisional — final view count still climbing |
| /1256811 Nov 2026, 06:35 UTC | 2724 minutes – 14 hours old | 27,200 views ~152 reactions | 60 minutes: 6,707 interp. → 3.0 hours: 15,349 interp. → 6.0 hours: 21,200 → 12 hours: 26,600still climbing at last reading | not yet at 24h | 2.4 hoursprovisional — final view count still climbing |
| /1256711 Nov 2026, 05:50 UTC | 2831 minutes – 15 hours old | 25,500 views ~127 reactions | 60 minutes: 7,492 interp. → 3.0 hours: 14,100 → 6.0 hours: 18,900 → 12 hours: 24,600still climbing at last reading | not yet at 24h | 2.7 hoursprovisional — final view count still climbing |
| /1256610 Nov 2026, 16:45 UTC | 4925 minutes – 28 hours old | 31,900 views ~143 reactions | 60 minutes: 8,497 interp. → 3.0 hours: 14,000 → 6.0 hours: 17,600 → 12 hours: 20,400 → 24 hours: 31,100still climbing at last reading | 31,100measured | 4.1 hours |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
Telegram’s own ‘edited’ marker: 31 of 217 posts held from the last 30 days (14.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).
Вайбкодер поставил задачу Fable 5.2 сделать игру пинг-понг и позволил нейронке «дать волю фантазии» — теперь это кошмар для эпилептика Если не боитесь, то поиграть можно — тут. Мы в МАХ 🤩
❤66😁19😢2👨💻1
Лицо Сэма Альтмана вывели на экран системы охлаждения и поставили «смотреть» на оперативу, которая работает не на его дата-центры Сэм Куколдман
❤130😁80👨💻7😢3👍1
Claude будет банить акки россиян даже заграницей — в силу вступили новые правила Anthropic С 12 ноября вы не можете юзать нейронку в стране, где она разрешена, работая на контору из списка запрещенных стран. VPN здесь не спасет. То есть, банить будут всех релокантов, работающих на российские компании. Мы в МАХ 🤩
😢82😁19❤7👨💻7👍3🔥1
В Австралии вомбат атакует чужие автомобили — животное проникает во внутрь и отказывается уходить Сотрудникам парка пришлось просить посетителей закрывать машины после серии необычных происшествий. Один и тот же вомбат забирался в разные автомобили и устраивался на пассажирских сиденьях. Одной паре пришлось почти час ждать, пока зверь освободит салон. Сначала работники думали, что речь идёт о брошенном животном, но…
😁112❤50🔥2
Lay’s дропнули вкус РАЗЛИВНОГО ПИВА — лимитка выпущена специально для Гонконга к Новому году Ждём на российских маркетплейсах! Мы в МАХ 🤩
😁148❤41😢11👨💻4👍2
Проводное радио хотят развивать в России — изменения в стратегию развития связи подготовило Минцифры Предполагается, что радиоточки смогут продолжать работу даже при перебоях с электроснабжением, когда привычные средства коммуникации окажутся недоступны. Необходимость развития такой инфраструктуры в документе связывают с «геополитической неопределенностью». «Будущее» уже близко 🤭
😢97😁34👍13❤6👨💻2
Мэра города в Перу выбрали подбросив монету — и да, это официально утвержденный способ В финале выборов в городе Конима оба кандидата набрали по 671 голосу. По закону победителя выбирают жеребьевкой, а способ подбрасыванием монеты утвердили в этом году. В итоге победил Рубен Киспе Капаханья, который сделал ставку на сторону монеты с гербом. Кенты, которые не могут определиться кто будет главным 😆 Мы в МАХ 🤩
😁93❤17🔥10👍7
Rockstar сегодня в ударе: вышел еще один трейлер GTA VI — в нем показаны фишки геймпада PS5, которые будут в игре Лучше бы 60 FPS завезли…
❤120👍16🔥7
Яндекс восстановил 97% данных в Yandex Cloud после атак на дата-центры — бэкапы теперь включены по умолчанию Инженеры смогли вернуть доступ к 97,16% клиентских данных. И это при серьёзных повреждениях оборудования! Для сравнения: после пожара в дата-центре OVHcloud во Франции в 2021 году часть клиентов осталась без данных навсегда. Так что результат восстановления у Яндекса впечатляет. Оставшиеся 2,84% восстановить …
👍61❤23🔥9😁4👨💻2
Подъехал лучший отзыв на GTA VI:
🔥125😁51❤28👍3😢3
🤩Показали новый трейлер GTA VI — в нем куча новых кадров геймплея Rockstar уже заработали более миллиарда долларов на GTA VI, еще до релиза игры. Сами разрабы также подтвердили, что на PS5 и PS5 Pro будет только 30 FPS. Играем через 🤩 дней.
❤54👨💻6🔥5👍3
Секрет миллиардеров в Кока-Коле — Уоррен Баффет пьет ее вместо воды уже почти пол века Он признался, что уже 48 лет может выпивать до 🤩 банок газировки в день. Также он предпочитает бургеры, картошку фри и мороженое. Как у нас много общего 😆
❤93👍14😁9👨💻3🔥1😢1
Showing the 12 most recent of 7,978 posts we hold for @chatgptv. 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.
@chatgptv edited 20 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.
We recorded 7 posts on @chatgptv 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.
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.
Named by 33 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@chatgptv named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was 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.
Read from Telegram’s recommendation API, most recently 8 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.
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.
This channel appears in 54 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
257 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
1 of 257 shown as text only, not a link. The exact host, not merely a domain it shares a registrable root with, matches a threat-intelligence blocklist this register already checks elsewhere (see methodology) — the link still appearing in a post is still a measured fact and is still shown, but no anchor is rendered here, so no click and no link equity passes to it from this page.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“Цифровой Журнал | IT, Neiroseti” (@chatgptv), 1,885,639 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/chatgptv.
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.