Telegram RegisterThe public register of Telegram
Telegram profile photo for Библиотека С# С++

Channel

Библиотека С# С++

@cpluscsharp

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

10,016subscribers

-69 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001224151555
TypeChannel
Username@cpluscsharp
Descriptionhttps://t.me/+WgGTjeH0p1NjMDFi - ссылка на канал По всем вопросам- @workakkk @ai_machinelearning_big_data - Machine learning @itchannels_telegram - 🔥лучшие ит-каналы @csharp_ci- C# академия @pythonlbooks- python книги📚 РКН: clck.ru/3Fmvsw
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/cpluscsharp

Topic

Education — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@cpluscsharp/575 · this entry14 Jun 2026, 13:29 UTC@cpluspluc/149214 Jul 2026, 13:01 UTC1.0030 days
@cpluscsharp/582 · this entry25 Jul 2026, 10:15 UTC@cpluspluc/15064 Aug 2026, 11:04 UTC1.0010 days
@cpluscsharp/584 · this entry4 Aug 2026, 10:24 UTC@cpluspluc/15096 Aug 2026, 13:02 UTC1.002 days
@cpluspluc/159726 Oct 2026, 09:44 UTC@cpluscsharp/606 · this entry26 Oct 2026, 11:00 UTC1.0076 minutes
@cpluscsharp/599 · this entry19 Oct 2026, 11:33 UTC@cpluspluc/16044 Nov 2026, 13:03 UTC1.0016 days
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
@cpluspluc5 (5/5 hand-verifiable sample passed)1.002 daysthis entry (4–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 38 comparable posts for this entry, running 26 April 2026 to 2 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).

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.

Growth

10,01510,08610,050.57 August 2026 — 10,085 subscribers7 August 2026 — 10,084 subscribers8 August 2026 — 10,082 subscribers9 August 2026 — 10,080 subscribers11 August 2026 — 10,074 subscribers13 August 2026 — 10,073 subscribers14 August 2026 — 10,074 subscribers16 August 2026 — 10,072 subscribers17 August 2026 — 10,067 subscribers18 August 2026 — 10,059 subscribers20 August 2026 — 10,061 subscribers20 August 2026 — 10,060 subscribers22 August 2026 — 10,054 subscribers24 August 2026 — 10,063 subscribers26 August 2026 — 10,057 subscribers28 August 2026 — 10,053 subscribers29 August 2026 — 10,055 subscribers30 August 2026 — 10,053 subscribers31 August 2026 — 10,052 subscribers31 August 2026 — 10,061 subscribers2 September 2026 — 10,077 subscribers3 September 2026 — 10,086 subscribers7 September 2026 — 10,082 subscribers10 September 2026 — 10,072 subscribers12 September 2026 — 10,069 subscribers14 September 2026 — 10,074 subscribers16 September 2026 — 10,066 subscribers18 September 2026 — 10,067 subscribers2 October 2026 — 10,085 subscribers7 October 2026 — 10,079 subscribers11 October 2026 — 10,073 subscribers14 October 2026 — 10,068 subscribers15 October 2026 — 10,066 subscribers16 October 2026 — 10,060 subscribers17 October 2026 — 10,061 subscribers18 October 2026 — 10,072 subscribers19 October 2026 — 10,074 subscribers20 October 2026 — 10,075 subscribers21 October 2026 — 10,078 subscribers22 October 2026 — 10,080 subscribers23 October 2026 — 10,078 subscribers24 October 2026 — 10,079 subscribers25 October 2026 — 10,077 subscribers26 October 2026 — 10,072 subscribers27 October 2026 — 10,065 subscribers28 October 2026 — 10,055 subscribers29 October 2026 — 10,054 subscribers30 October 2026 — 10,049 subscribers31 October 2026 — 10,045 subscribers1 November 2026 — 10,041 subscribers2 November 2026 — 10,036 subscribers3 November 2026 — 10,034 subscribers4 November 2026 — 10,031 subscribers5 November 2026 — 10,029 subscribers6 November 2026 — 10,024 subscribers8 November 2026 — 10,019 subscribers9 November 2026 — 10,015 subscribers11 November 2026 — 10,016 subscribers10,0167 August 202611 November 2026
58 measurements spanning 96 days, net -69. 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 10,004–10,097 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, 06:4710,016+1
9 Nov 2026, 14:4010,015-4
8 Nov 2026, 03:0110,019-5
6 Nov 2026, 20:2510,024-5
5 Nov 2026, 18:3010,029-2
4 Nov 2026, 19:0910,031-3
3 Nov 2026, 22:2710,034-2
2 Nov 2026, 22:0810,036-5
1 Nov 2026, 19:4910,041-4
31 Oct 2026, 20:0010,045-4
30 Oct 2026, 20:5810,049-5
29 Oct 2026, 21:0110,054-1
28 Oct 2026, 23:3910,055-10
27 Oct 2026, 22:4610,065-7
26 Oct 2026, 00:4810,072-5
25 Oct 2026, 00:5810,077-2
24 Oct 2026, 03:4910,079+1
23 Oct 2026, 07:1010,078-2
22 Oct 2026, 07:3510,080+2
21 Oct 2026, 03:4010,078first reading

Engagement

39 posts held, back to 26 April 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 55 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
6.80%
avg views ÷ 10,016 subscribers
Avg views / post
681
9 posts measured
Reaction rate
0.505%
reactions ÷ views · ER floor
Posts in window
9
of 39 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 held39 (26 April 2026 – 11 November 2026)
Views total6,133
Reactions total31
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 22:50 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
220
Videos
15
Links
211

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
1h 40m
Average length
25m 13s

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

221 reactions across 38 posts, in 8 distinct kinds. The most used accounts for 49.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10949.3%
👍6429.0%
🔥4118.6%
😁20.905%
🥰20.905%
🙏10.452%
🤡10.452%
🤣10.452%

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

Measured over the 39 most recent posts we hold, published 26 April 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.

Advertising

Ad load
5.13%
2 of 39 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
834
over 2 measured posts
Median views · rest
1,180
over 37 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
2VSb5xhhMJz124 September 202624 September 2026
2VtzqwMJdhX15 October 20265 October 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 39 most recent posts we hold, published 26 April 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: 0 of 9 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).

11 Nov 2026, 08:47 UTC271 views2 reactionsread 11 November 2026
Photo

🖥️ Почему `errno` в C не ломается при работе 32 потоков одновременно? На первый взгляд errno выглядит как обычная глобальная переменная: if (errno == EINTR) { // retry } Но если 32 потока одновременно выполняют системные вызовы, почему они не перезаписывают errno друг у друга? Потому что errno на самом деле не обычная глобальная переменная. В glibc это макрос, который обращается к специальной функции __err…

❤2

2 Nov 2026, 12:35 UTC640 views3 reactionsread 11 November 2026
Photo

✔️ Tencent показала Hyra 2.0: ресерч-агента для автоматизацииисследований В первой версии Hyra агент работал по схеме: предложить решение, запустить эксперимент, оценить метрику и использовать результаты для следующей итерации. В Hyra 2.0 Tencent предлагает сохранять не только удачные решения, но и полученные в процессе инструменты, модели и экспериментальные пайплайны. Например, при оптимизации обучения агент мо…

❤2👍1

2 Nov 2026, 10:35 UTC575 views3 reactionsread 11 November 2026
Photo

🖥️ Черная пятница на Stepik на один из лучших курсов по контейнеризации! Если давно хотел разобраться в теме, но постоянно откладывал или терялся среди десятков материалов, этот курс на Stepik поможет выстроить обучение последовательно. Что получишь: - Понятные объяснения без лишней воды. - Практические задания для закрепления знаний. - Возможность учиться в удобном темпе. - Структурированный подход вместо хаотично…

❤2👍1

29 Oct 2026, 12:03 UTC764 views4 reactionsread 11 November 2026
Photo

В C# наконец появились union-типы Разбираем C# 15 и .NET 11: union-типы, закрытые иерархии через closed, аргументы в коллекционных выражениях, extension-индексаторы и именованные break и continue. Разработчики на C# просили размеченные объединения (discriminated unions) почти десять лет. Обсуждение в репозитории языка годами оставалось одним из самых популярных, а команды тем временем писали свои OneOf, Result и ие…

❤3🔥1

28 Oct 2026, 07:48 UTC676 views2 reactionsread 11 November 2026
Video

Эта функция из 1983 года выглядит как ошибка. Но работает В 1983 году Том Дафф в Lucasfilm вставил switch прямо внутрь цикла do while, чтобы ускорить копирование. Показываю на примере 11 элементов, как код «проваливается» по веткам case, и привожу цитату из его письма Ритчи и Пайку. Я замерил на C: без оптимизаций трюк быстрее обычного цикла на 40%, с оптимизацией выигрыш всего 13%, а memcpy быстрее в пять раз. htt…

❤2

26 Oct 2026, 11:00 UTC685 views6 reactionsread 11 November 2026
Video

«what the fu**?»: самый странный комментарий в игровом коде Одна строка из Quake III заменяет деление и корень сдвигом битов и магическим числом 0x5f3759df. Покажу на примере, как это работает, и посчитаю погрешность: 3.44% до уточнения и 0.175% после одного шага Ньютона. А кто на самом деле придумал трюк, вы вряд ли угадаете. https://youtube.com/shorts/oIpqqzNNCHo

❤4👍1🔥1

26 Oct 2026, 07:55 UTC697 views1 reactionsread 11 November 2026
Photo

👨🏻‍💻 AI в бэкенд-задачах — на Podlodka Backend Crew Код теперь может написать агент, но за результат всё ещё отвечаете вы. Организаторы Podlodka Backend Crew собрали конференцию о том, как работать с бэкендом после того, как AI написал код. Причём в программе нет докладов в жанре «у нас все получилось» — только реальная практика. Конференция пройдёт с 26 по 30 октября. 🧠️️️️ Участники сезона: • Разберут пулл‑рек…

❤1

21 Oct 2026, 18:47 UTC942 views6 reactionsread 11 November 2026
Photo

20 готовых программ на C++ с кодом: практика для новичков и не только (2026) 20 готовых программ на C++ с исходным кодом: от калькулятора до LRU-кэша и алгоритма Дейкстры. Копируйте, запускайте и прокачивайте навыки в 2026 году. https://uproger.com/20-programm-na-cpp-s-kodom-2026/

❤4🔥1🥰1

19 Oct 2026, 11:33 UTC883 views4 reactionsread 11 November 2026
Photo

💡 В C можно заполнить три элемента массива, а остальные обнулятся автоматически Для этого есть designated initializers — инициализация с указанием индексов: int flags[256] = { ['A'] = 1, ['Z'] = 1, [42] = 99 }; Получаем: • flags['A'] и flags['Z'] равны 1. • flags[42] равен 99. • Все остальные элементы равны 0, даже если массив локальный. 'A' здесь — символьная константа: её числовое значение испол…

❤4

12 Oct 2026, 13:54 UTC≈1,170 views1 reactionsread 11 November 2026

Альфа-Банк ищет скиллового коллегу QA Fullstack на C# Предлагаем полную удалёнку или гибридный график – у нас классные ИТ-офисы в Москве, Питере и Екатеринбурге. Что нужно делать – Разрабатывать автотесты на C#. – Запускать функциональные, регрессионные и интеграционные тесты, включая API. – Снижать количество дефектов в диалоге с разработкой и бизнесом. Какие навыки важны – Опыт автоматизации на C# и ручного те…

❤1

6 Oct 2026, 13:22 UTC≈1,370 views7 reactionsread 11 November 2026
Photo

Rust vs Go vs C# в 2026: почему наивный Rust проиграл Go Сравнение производительности Rust, Go и C# в 2026 году: наш тест на аллокациях, где наивный Rust уступил Go, а Rust с ареной оказался в 7 раз быстрее, плюс разбор GC, памяти, холодного старта, Green Tea и .NET 10 Спор «что быстрее: Rust, Go или C#» обычно заканчивается ссылкой на чей-то бенчмарк, где один язык обгоняет другой в полтора раза. Мы решили провери…

❤4😁2👍1

5 Oct 2026, 13:45 UTC≈1,180 views9 reactionsread 11 November 2026
Photo

Наследование в чистом C: одно правило, и всё работает В C нет классов, но наследование можно собрать вручную. Правило одно: родительская структура должна стоять первым полем дочерней. struct Animal { int age; char name[32]; }; struct Dog { struct Animal base; // обязательно первым char breed[32]; }; struct Dog d = { {3, "Rex"}, "Labrador" }; print_animal((struct Animal *)&d); // работает Почему это …

❤4👍4🔥1

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

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

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.

Data Science. SQL hub
@sqlhub · 36,025
Telegram ranks this channel #19 of 87 here — alongside 86 others — read 2 September 2026
Data Science
@datascienceiot · 42,496
Telegram ranks this channel #22 of 76 here — alongside 75 others — read 29 August 2026
Учебные фильмы 🎞
@maths_lib · 25,588
Telegram ranks this channel #26 of 67 here — alongside 66 others — read 14 September 2026
Библиотека программиста (книги для разработчиков)
@programmist_of · 20,570
Telegram ranks this channel #28 of 63 here — alongside 62 others — read 5 October 2026
DevOps
@DevOPSitsec · 23,892
Telegram ranks this channel #30 of 90 here — alongside 89 others — read 18 September 2026
Python вопросы с собеседований
@python_job_interview · 24,906
Telegram ranks this channel #31 of 90 here — alongside 89 others — read 15 September 2026
Python/ django
@pythonl · 58,245
Telegram ranks this channel #43 of 84 here — alongside 83 others — read 22 August 2026
Open IT | Архив
@openit_archive · 18,760
Telegram ranks this channel #44 of 59 here — alongside 58 others — read 5 October 2026
Physics.Math.Code
@physics_lib · 146,676
Telegram ranks this channel #45 of 72 here — alongside 71 others — read 13 August 2026
Полка Разработчика
@developer_shelf · 26,715
Telegram ranks this channel #46 of 63 here — alongside 62 others — read 11 September 2026
Linux Academy
@linuxacademiya · 28,676
Telegram ranks this channel #59 of 84 here — alongside 83 others — read 9 September 2026
Анализ данных (Data analysis)
@data_analysis_ml · 51,973
Telegram ranks this channel #65 of 93 here — alongside 92 others — read 25 August 2026
Kali Linux
@linuxkalii · 55,900
Telegram ranks this channel #70 of 89 here — alongside 88 others — read 23 August 2026

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

“Библиотека С# С++” (@cpluscsharp), 10,016 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/cpluscsharp.

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.