Telegram RegisterThe public register of Telegram
Telegram profile photo for Чартомойка

Channel

Чартомойка

@chartomojka

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

14,786subscribers

-103 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001109735806
TypeChannel
Username@chartomojka
Created9 February 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/chartomojka

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

Growth

14,77814,89414,8366 August 2026 — 14,889 subscribers6 August 2026 — 14,889 subscribers7 August 2026 — 14,886 subscribers8 August 2026 — 14,888 subscribers9 August 2026 — 14,887 subscribers11 August 2026 — 14,889 subscribers12 August 2026 — 14,888 subscribers13 August 2026 — 14,887 subscribers14 August 2026 — 14,890 subscribers16 August 2026 — 14,892 subscribers18 August 2026 — 14,894 subscribers19 August 2026 — 14,891 subscribers20 August 2026 — 14,892 subscribers21 August 2026 — 14,894 subscribers23 August 2026 — 14,890 subscribers25 August 2026 — 14,886 subscribers25 August 2026 — 14,890 subscribers26 August 2026 — 14,888 subscribers27 August 2026 — 14,890 subscribers28 August 2026 — 14,892 subscribers29 August 2026 — 14,887 subscribers30 August 2026 — 14,886 subscribers31 August 2026 — 14,885 subscribers1 September 2026 — 14,886 subscribers2 September 2026 — 14,882 subscribers3 September 2026 — 14,878 subscribers5 September 2026 — 14,877 subscribers9 September 2026 — 14,873 subscribers11 September 2026 — 14,876 subscribers13 September 2026 — 14,871 subscribers15 September 2026 — 14,869 subscribers16 September 2026 — 14,867 subscribers25 September 2026 — 14,845 subscribers4 October 2026 — 14,817 subscribers8 October 2026 — 14,815 subscribers13 October 2026 — 14,798 subscribers14 October 2026 — 14,793 subscribers15 October 2026 — 14,789 subscribers16 October 2026 — 14,786 subscribers18 October 2026 — 14,778 subscribers20 October 2026 — 14,779 subscribers22 October 2026 — 14,781 subscribers23 October 2026 — 14,786 subscribers24 October 2026 — 14,783 subscribers26 October 2026 — 14,782 subscribers27 October 2026 — 14,781 subscribers29 October 2026 — 14,787 subscribers30 October 2026 — 14,790 subscribers31 October 2026 — 14,792 subscribers1 November 2026 — 14,790 subscribers2 November 2026 — 14,788 subscribers3 November 2026 — 14,792 subscribers4 November 2026 — 14,793 subscribers5 November 2026 — 14,791 subscribers7 November 2026 — 14,792 subscribers8 November 2026 — 14,790 subscribers9 November 2026 — 14,787 subscribers11 November 2026 — 14,786 subscribers14,7866 August 202611 November 2026
58 measurements spanning 97 days, net -103. 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 14,761–14,911 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
11 Nov 2026, 12:5614,786-1
9 Nov 2026, 21:0814,787-3
8 Nov 2026, 14:3614,790-2
7 Nov 2026, 09:3714,792+1
5 Nov 2026, 09:5014,791-2
4 Nov 2026, 11:2614,793+1
3 Nov 2026, 13:0714,792+4
2 Nov 2026, 13:2114,788-2
1 Nov 2026, 10:5614,790-2
31 Oct 2026, 10:5414,792+2
30 Oct 2026, 12:4414,790+3
29 Oct 2026, 15:3914,787+6
27 Oct 2026, 18:5014,781-1
26 Oct 2026, 18:4914,782-1
24 Oct 2026, 20:5014,783-3
23 Oct 2026, 18:2714,786+5
22 Oct 2026, 18:4014,781+2
20 Oct 2026, 14:5814,779+1
18 Oct 2026, 13:3714,778-8
16 Oct 2026, 12:4114,786first reading

Engagement

19 posts held, back to 20 February 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 70 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
23.7%
avg views ÷ 14,786 subscribers
Avg views / post
3,510
2 posts measured
Reaction rate
5.51%
reactions ÷ views · ER floor
Posts in window
2
of 19 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 8 November 2026
Posts held19 (20 February 2026 – 8 November 2026)
Views total7,010
Reactions total386
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 07:08 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 03s
Average length
31s

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

2,515 reactions across 19 posts, in 27 distinct kinds. The most used accounts for 47.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁1,18547.1%
❤29311.7%
🤣27010.7%
🔥26910.7%
🤯1003.98%
👍913.62%
😱722.86%
🏆532.11%
👏471.87%
💯230.915%
🤔210.835%
🥰150.596%
🤡140.557%
👎110.437%
🍌80.318%
😍80.318%
💩60.239%
🤩60.239%
😢50.199%
❤‍🔥40.159%
7 further kinds140.557%

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

Measured over the 19 most recent posts we hold, published 20 February 2026 to 8 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) 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).

8 Nov 2026, 14:25 UTC≈2,970 views303 reactionsread 11 November 2026
Photo

Помните. Корреляция не означает причинно-следственной связи

😁160🔥89❤45🥰5💯2❤‍🔥1👍1

Signed Aleksandr Bogachev

13 Oct 2026, 06:20 UTC≈4,040 views83 reactionsread 11 November 2026
Forwarded from @datanatureVideo

Визуализация как отдых от AI-повестки. Вдохновился проектом Саши Богачева про Париж и собрал две карты для визуального исследования Петербурга и Амстердама, двух близких мне городов. К подходу Саши я добавил слои контекста: Серебряный век, блокада, «Последний адрес», дворы-колодцы, парадные, старые бары; стрит-арт. Своеобразные линзы, через которые можно смотреть на город сквозь его историю. У каждого здания в слое…

🔥57❤23👍1👏1💩1

Signed Aleksandr Bogachev

11 Oct 2026, 10:24 UTC≈4,840 views191 reactionsread 11 November 2026
Photo

Ну, как-то так пока.

😁153👍20💯9❤8🎉1

Signed Aleksandr Bogachev

3 Oct 2026, 05:39 UTC≈7,990 views354 reactionsread 11 November 2026
Photo

Это конечно шедевр. Присмотритесь к оси Y.

😁201🤣113🔥29👍6🌭2😱2🍌1

Signed Aleksandr Bogachev

12 Aug 2026, 12:04 UTC≈7,300 views100 reactionsread 11 November 2026
Forwarded from @interactivenewsVideo

Сегодня вечером в Европе будет полное солнечное затмение. И я очень рад, что мой проект про затмения попал в подборку Datawrapper рядом с отличными проектами Reuters и The New York Times — командами, чью работу я бесконечно уважаю. Для меня это большая честь. Вообще, мне кажется, такой формат все еще вполне способен привлекать читателей: не обязательно эксплейнер со скроллителлингом, а скорее большой интерактивный …

❤58👍18🔥16👏8

Signed Aleksandr Bogachev

29 Jul 2026, 14:33 UTC≈6,660 views72 reactionsread 11 November 2026
Photo

В бургере есть булочка? Кетчуп? Майонез? Лук? Быть не может, никогда бы не подумал. ИИ-иллюстрация занимает пол-экрана. Справа два числа. В заге — риторический вопрос. В источниках расчеты на основе Росстата. Может быть вместо взрыв схемы бургера показать график роста и сравнить с инфляцией? Можно будет например увидеть динамику изменений, в какие моменты рост становился быстрее и отрывался от инфляции. Нет, лучш…

😁45🤣19💯3🔥2😢2❤1

Signed Aleksandr Bogachev

27 Jul 2026, 15:43 UTC≈5,110 views28 reactionsread 11 November 2026

Полностью согласен с Лёшей, ИИ меняет подход к визуализации. И это прекрасно. Но накладывает больше ответственности в части "знать, что делаешь". Кстати, по-дружески очень советую курс Лёши. Если бы я сейчас только начинал эта заниматься, обязательно записался бы. https://t.me/perfectgraphs/381

❤9👍8🥰7😁2👏1🔥1

Signed Aleksandr Bogachev

24 Jul 2026, 12:02 UTC≈6,520 views31 reactionsread 11 November 2026
Photo

Датавраппер наносит ответный удар. Они добавили возможность делать каскадную диаграмму (waterfall) и.. двойные оси! С которыми Лиза Шарлотта Мут (тогда ещё Рост) ранее активно боролась. Впрочем, теперь она говорит, что изменила свое мнение и даже написала статью когда и как правильно их использовать. Читаем: https://www.datawrapper.de/blog/dual-axis-charts-guide

😁18🤯9❤3🔥1

Signed Aleksandr Bogachev

18 Jul 2026, 14:59 UTC≈5,980 views33 reactionsread 11 November 2026
Photo

Просто симпатичная подборка иконических датавиз-проектов от Яна Хольтца. В закладки для вдохновения https://www.dataviz-inspiration.com/

❤19👍8🔥6

Signed Aleksandr Bogachev

19 Jun 2026, 18:13 UTC≈7,730 views115 reactionsread 11 November 2026
Video

Video, posted without a caption

😁83🤣20🔥10❤2

Signed Aleksandr Bogachev

11 Jun 2026, 12:29 UTC≈9,750 views62 reactionsread 11 November 2026
Video

В честь начинающегося ЧМ по футболу запилил небольшой интерактивчик про перелеты команд и углеродный след от них. Ссылка: worldcup.bogachev.fr Там цифры не очень большие, а вот если брать с болельщиками, которые летают с матча на матч - в 500-1500 раз больше. По разным оценкам на ближайшем чемпионате углеродный удар составит 8-9 млн тонн CO2. Это больше чем годовые выбросы небольшой страны типа Кипра 🤷🏻 Но всё …

❤26🔥15👎10❤‍🔥3💩2🤡2😁2💔1

Signed Aleksandr Bogachev

14 May 2026, 09:53 UTC≈7,440 views139 reactionsread 11 November 2026
Photo

Свежий график Коммерсанта, и то, как его видят читатели.

😁91👏20🤯17💯9❤1👎1

Signed Aleksandr Bogachev

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

Forward network

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 6 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.

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.

Рациональные числа
@rationalnumbers · 25,574
Telegram ranks this channel #5 of 93 here — alongside 92 others — read 13 September 2026
настенька и графики
@nastengraph · 28,082
Telegram ranks this channel #6 of 94 here — alongside 93 others — read 9 September 2026
Reveal the Data
@revealthedata · 27,662
Telegram ranks this channel #7 of 96 here — alongside 95 others — read 10 September 2026
Excel Everyday
@excel_everyday · 52,038
Telegram ranks this channel #42 of 97 here — alongside 96 others — read 24 August 2026
Магия Excel
@lemur_excel · 49,845
Telegram ranks this channel #49 of 95 here — alongside 94 others — read 25 August 2026
Google Таблицы
@google_sheets · 59,478
Telegram ranks this channel #56 of 98 here — alongside 97 others — read 22 August 2026
Клуб анонимных аналитиков
@analyst_club · 33,324
Telegram ranks this channel #63 of 96 here — alongside 95 others — read 4 September 2026
LEFT JOIN
@leftjoin · 41,485
Telegram ranks this channel #75 of 95 here — alongside 94 others — read 29 August 2026
Инжиниринг Данных
@rockyourdata · 23,679
Telegram ranks this channel #78 of 93 here — alongside 92 others — read 17 September 2026
Если быть точным
@tochno_st · 19,605
Telegram ranks this channel #85 of 97 here — alongside 96 others — read 2 October 2026
Noukash
@noukashblog · 21,573
Telegram ranks this channel #87 of 95 here — alongside 94 others — read 23 September 2026
karpov.courses
@KarpovCourses · 27,313
Telegram ranks this channel #93 of 96 here — alongside 95 others — read 10 September 2026

This channel appears in 12 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.

“Чартомойка” (@chartomojka), 14,786 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/chartomojka.

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.