Telegram RegisterThe public register of Telegram
Telegram profile photo for Николай Тузов

Channel

Николай Тузов

@ntuzov

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

16,923subscribers

+289 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-1001687870480
TypeChannel
Username@ntuzov
DescriptionGo Developer, автор YouTube канала по Go: https://www.youtube.com/@nikolay_tuzov Live канал: @ntuzov_live AI News: @tuzov_ai_lab Go Digest: @golang_digest Обратная связь: @justskiv Поддержать: https://boosty.to/nikolay.tuzov/ https://t.me/ntuzov/126
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live5 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/ntuzov

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 73% 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

16,63416,93416,7846 August 2026 — 16,634 subscribers7 August 2026 — 16,636 subscribers8 August 2026 — 16,635 subscribers9 August 2026 — 16,634 subscribers10 August 2026 — 16,640 subscribers11 August 2026 — 16,642 subscribers12 August 2026 — 16,645 subscribers13 August 2026 — 16,638 subscribers14 August 2026 — 16,651 subscribers15 August 2026 — 16,656 subscribers17 August 2026 — 16,663 subscribers19 August 2026 — 16,667 subscribers20 August 2026 — 16,674 subscribers21 August 2026 — 16,681 subscribers22 August 2026 — 16,682 subscribers24 August 2026 — 16,681 subscribers25 August 2026 — 16,678 subscribers26 August 2026 — 16,686 subscribers27 August 2026 — 16,695 subscribers28 August 2026 — 16,699 subscribers29 August 2026 — 16,710 subscribers30 August 2026 — 16,719 subscribers31 August 2026 — 16,725 subscribers1 September 2026 — 16,724 subscribers2 September 2026 — 16,739 subscribers4 September 2026 — 16,750 subscribers7 September 2026 — 16,756 subscribers10 September 2026 — 16,773 subscribers12 September 2026 — 16,768 subscribers13 September 2026 — 16,759 subscribers15 September 2026 — 16,756 subscribers17 September 2026 — 16,764 subscribers27 September 2026 — 16,870 subscribers4 October 2026 — 16,898 subscribers9 October 2026 — 16,903 subscribers13 October 2026 — 16,908 subscribers14 October 2026 — 16,919 subscribers15 October 2026 — 16,926 subscribers17 October 2026 — 16,927 subscribers18 October 2026 — 16,932 subscribers19 October 2026 — 16,934 subscribers21 October 2026 — 16,933 subscribers22 October 2026 — 16,926 subscribers23 October 2026 — 16,927 subscribers24 October 2026 — 16,924 subscribers25 October 2026 — 16,919 subscribers26 October 2026 — 16,923 subscribers27 October 2026 — 16,924 subscribers28 October 2026 — 16,920 subscribers29 October 2026 — 16,928 subscribers30 October 2026 — 16,931 subscribers31 October 2026 — 16,926 subscribers1 November 2026 — 16,917 subscribers3 November 2026 — 16,920 subscribers4 November 2026 — 16,921 subscribers5 November 2026 — 16,923 subscribers16,9236 August 20265 November 2026
56 measurements spanning 91 days, net +289. 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 16,589–16,979 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
5 Nov 2026, 05:4116,923+2
4 Nov 2026, 08:3516,921+1
3 Nov 2026, 06:3816,920+3
1 Nov 2026, 03:5016,917-9
31 Oct 2026, 06:0116,926-5
30 Oct 2026, 07:5816,931+3
29 Oct 2026, 09:0116,928+8
28 Oct 2026, 07:2916,920-4
27 Oct 2026, 05:4116,924+1
26 Oct 2026, 05:3716,923+4
25 Oct 2026, 03:4616,919-5
24 Oct 2026, 06:0816,924-3
23 Oct 2026, 03:0916,927+1
22 Oct 2026, 05:5016,926-7
21 Oct 2026, 01:2116,933-1
19 Oct 2026, 23:4916,934+2
18 Oct 2026, 21:0016,932+5
17 Oct 2026, 20:5916,927+1
15 Oct 2026, 15:3716,926+7
14 Oct 2026, 19:0116,919first reading

Engagement

33 posts held, back to 8 May 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 62 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
49.6%
avg views ÷ 16,923 subscribers
Avg views / post
8,390
6 posts measured
Reaction rate
0.652%
reactions ÷ views · ER floor
Posts in window
6
of 33 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 5 November 2026
Posts held33 (8 May 2026 – 5 November 2026)
Views total50,340
Reactions total328
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 16:22 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
271
Videos
19
Links
347

Lifetime counters from Telegram’s own channel header, read 5 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.

Reaction mix

4,191 reactions across 32 posts, in 15 distinct kinds. The most used accounts for 46.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1,93346.1%
👍71016.9%
custom 546063786126922608866415.8%
custom 529410768984711937659914.3%
custom 52808977706039640611453.46%
custom 5294443796807835481240.573%
custom 5449842070128699072190.453%
custom 5460802341336801764190.453%
custom 5422606750496867655180.429%
custom 5238177066645490209170.406%
custom 5395319350091599049130.31%
custom 5864027176893943469120.286%
custom 5280813894187639638100.239%
custom 546074072573595503760.143%
custom 528059565830939431820.048%

Custom emoji. 13 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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

Measured over the 33 most recent posts we hold, published 8 May 2026 to 5 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.

Telegram Stars

Stars received
288
across the posts below
Posts paid on
10
of 33 we hold a reading for · 30%
Most on one post
205
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ntuzov. 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 33 most recent posts we hold for this entry, published 8 May 2026 to 5 November 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

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

5 Nov 2026, 11:40 UTC≈3,330 views34 reactionsread 5 November 2026

♠️ Backend Roulette: system design за покерным столом 17 ноября ребята из AvitoTech собирают бэкендеров, Go-разработчиков и любителей System Design на вечеринку с инженерными кейсами. Докладов снова не будет — вместо них игровые столы. Как это устроено: Вместе со своей командой садитесь за стол, и эксперт AvitoTech в роли крупье раздаёт вводные к задаче. По ходу игры он подкидывает новые обстоятельства, и решение …

🔥17custom 54606378612692260889custom 52941076898471193765custom 52808977706039640612👍1

31 Oct 2026, 18:13 UTC≈7,150 views31 reactionsread 5 November 2026

Если вам вдруг очень не хватает детальных разборов новостей про Go, напоминаю что я их давно вынес в отдельный канал. А поскольку у меня теперь стало сильно больше времени, то и формат постов там изменился — разборы теперь более детальные. Читайте меня и тут, и там, и сям ☀️

custom 529410768984711937616🔥11custom 52944437968078354813👍1

31 Oct 2026, 18:07 UTC≈5,800 views53 reactionsread 5 November 2026
Forwarded from @golang_digest

Posted without readable text

👍28custom 546063786126922608814custom 52808977706039640614custom 52941076898471193764custom 52944437968078354813

20 Oct 2026, 18:54 UTC≈9,760 views0 reactionsread 5 November 2026
Poll

Как вам такие статьи?

  1. Интересно, делай ещё (в меру)67%
  2. Слишком подробно для такой тематики13%
  3. Не знаю / Посмотреть ответы20%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

20 Oct 2026, 15:58 UTC≈10,400 views90 reactions1 Starread 5 November 2026

👴 JSON v2 — не всё так гладко, как обещали https://golang.guide/json-v2/ В Go 1.27 добавили новый пакет для работы с JSON, а старый теперь работает на новом движке. После этой статьи вы будете знать о нём вообще всё, и даже чуть больше 😐 Например, авторы обещали полную обратную совместимость для старого пакета, и что производительность вырастет аж "до x10". Как оказалось, оба утверждения... не совсем верны — я на…

🔥63custom 52808977706039640619custom 52941076898471193768custom 52944437968078354816👍4

10 Oct 2026, 18:06 UTC≈13,900 views120 reactionsread 5 November 2026

Когда я писал статью про Go 1.27, несколько разделов очень сильно разрослись, поэтому я повыносил их в отдельные статьи. Пока не уверен, буду ли все из них дописывать в скором времени (ведь на очереди ещё серия статей про планировщик, и про память с GC), но про JSON v2 точно допишу, там самое интересное. Например, краткий экскурс в историю проблемы, а главное — наглядная демонстрация граблей, которые были в JSON v1.…

👍63custom 546063786126922608834🔥16custom 52944437968078354814custom 52808977706039640613

5 Oct 2026, 13:26 UTC≈20,300 views46 reactionsread 5 November 2026

❤️Исследование рынка Go-разработчиков от DevCrowd https://survey.devcrowd.ru/go-2026 Традиционно, уже четвертый год не устаю вам напоминать о работе этих ребят. Рынок — сложная непонятная штука, а нам хочется чтобы эта штука стала прозрачной. Единственный способ этого добиться — проводить честные опросы среди всех его участников. Чем больше выборка, тем более полную картину мы увидим. Вот эту ношу на себя и взяли …

👍32custom 52941076898471193767custom 52808977706039640613custom 52944437968078354812custom 54606378612692260882

2 Oct 2026, 09:41 UTC≈19,100 views168 reactions2 Starsread 5 November 2026

🥂Разбор Go 1.27 полностью дописан! Вы уже, наверно, забыли о том, что вышла новая версия языка, и что я пишу о ней статью.. 😩 В статье появились разделы про аллокации и рантайм, net/http, портируемый SIMD и go fix, а в самом конце чек-лист на случай, если после апгрейда у вас упал CI. Всё новое читать отсюда. А ещё я добавил в большинство запускаемых код-сниппетов, включая старые, переключатель версии, чтобы сравн…

🔥114👍27custom 529410768984711937617custom 52808977706039640616custom 54606378612692260884

15 Sept 2026, 12:19 UTC≈19,500 views146 reactions4 Starsread 5 November 2026

Дописал самый большой кусок статьи про Go 1.27 — раздел про постквантовые подписи. В 1.27 приехал пакет crypto/mldsa и вся обвязка вокруг него (сертификаты, TLS). Обмен ключами добавили ещё в 1.24, а теперь очередь дошла до аутентификации — то есть на чистом Go наконец-то полностью собирается постквантовый хендшейк 🎉 Обычно этому разделу в обзорах уделяют незаслуженно мало внимания — многие плохо понимают в чём тут…

custom 529410768984711937697👍29custom 546063786126922608815custom 52808977706039640614custom 52944437968078354811

13 Sept 2026, 07:13 UTC≈12,900 views162 reactionsread 5 November 2026

Нельзя мне браться за обзоры релизов... Вместо небольшого раздела по постквантновые подписи в Go 1.27, я написал по небольшой гайд постквантовой криптографии... Сегодня-завтра постараюсь обновить статью и опубликовать этот раздел. Ну ладно, зато было весело 👍

🔥95custom 546063786126922608846custom 529410768984711937621

27 Aug 2026, 18:34 UTC≈24,600 views234 reactions205 Starsread 5 November 2026
Photo

😐 Ультимативный разбор... Go 1.27? Честно, не знаю зачем я это сделал, но я сделал.. Ну почти. https://golang.guide/go-1-27/ Сначала я решил просто написать базовый обзор релиза. Но потом я увлёкся и не смог вовремя остановиться. Мне хотелось не просто сухо рассказать об изменениях, а добиться глубокого понимания читателя — причины этих изменений, какие проблемы они решают, как реализовано, почему именно сейчас, …

custom 528089777060396406197🔥89custom 529410768984711937640custom 54606378612692260885👍3

24 Aug 2026, 06:57 UTC≈16,700 views20 reactionsread 5 November 2026

👴 Посоветуйте хорошего бухгалтера на аутсорс в Казахстане, в идеале в Астане Рынок у нас маленький, и хороших специалистов найти сложно. При этом, сейчас многие разработчики работают по ИП, и наверняка часто делегируют ведение бухгалтерии профильным специалистам. Если у вас есть на примете хорошие проверенные специалисты, поделитесь контактом, пожалуйста. Можно в ЛС: @justskiv

custom 546063786126922608813custom 52808977706039640613custom 52944437968078354812👍1🔥1

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

Posts recorded as deleted after publishing

We recorded 2 posts on @ntuzov 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.

First seen missing
22 August 2026
Most recent seen missing
31 August 2026
Median time before seen missing
9 days
Seen missing in the last 30 days
0

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

20 Oct 2026, 18:54 UTCAnonymous Poll1,180 voters approx.

Как вам такие статьи?

  1. Интересно, делай ещё (в меру)67%
  2. Слишком подробно для такой тематики13%
  3. Не знаю / Посмотреть ответы20%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

21 May 2026, 17:21 UTCAnonymous Poll2,360 voters approx.

Насколько вы хорошо знакомы с понятием "виртуальная память"

  1. Слышу впервые 🌚10%
  2. Что-то слышал, но понимаю смутно 🗿24%
  3. В общих чертах — что у каждого процесса свое адресное пространство, и ОС это как-то разруливает 🦄54%
  4. Знаю про page tables, RSS vs VSZ и page faults 🧙11%
  5. Сам это объясняю джунам / спрашиваю на собесах 👴1%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 33 most recent posts we hold, published 8 May 2026 to 5 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

Библиотека Go-разработчика | Golang
@goproglib · 23,921
Telegram ranks this channel #3 of 91 here — alongside 90 others — read 17 September 2026
AvitoTech
@avitotech · 25,790
Telegram ranks this channel #6 of 96 here — alongside 95 others — read 14 September 2026
Ozon Tech
@ozon_tech · 30,148
Telegram ranks this channel #16 of 98 here — alongside 97 others — read 8 September 2026
Артём Шумейко
@artemshumeiko · 19,795
Telegram ranks this channel #20 of 92 here — alongside 91 others — read 29 September 2026
Рефералки в IT | Вакансии и резюме
@refer_me_it · 31,728
Telegram ranks this channel #32 of 89 here — alongside 88 others — read 7 September 2026
Alek OS
@Alek_OS · 32,332
Telegram ranks this channel #33 of 95 here — alongside 94 others — read 4 September 2026
Библиотека программиста
@proglibrary · 77,704
Telegram ranks this channel #40 of 82 here — alongside 81 others — read 19 August 2026
Timeweb Cloud Alerts
@timewebcloud_alerts · 25,857
Telegram ranks this channel #43 of 87 here — alongside 86 others — read 9 September 2026
Диджитализируй!
@t0digital · 28,601
Telegram ranks this channel #47 of 88 here — alongside 87 others — read 9 September 2026
Golang
@Golang_google · 40,475
Telegram ranks this channel #51 of 90 here — alongside 89 others — read 30 August 2026
Осознанная Меркантильность | Антон Назаров
@m0rtymerr_channel · 80,672
Telegram ranks this channel #54 of 87 here — alongside 86 others — read 18 August 2026
Dev & ML Connectable Jobs
@dev_connectablejobs · 28,996
Telegram ranks this channel #58 of 94 here — alongside 93 others — read 10 September 2026
Digital Ниндзя
@digital_ninjaa · 40,483
Telegram ranks this channel #62 of 91 here — alongside 90 others — read 30 August 2026
АйТиБорода
@itbeard · 19,012
Telegram ranks this channel #63 of 93 here — alongside 92 others — read 3 October 2026
Dev KZ | Vacancy
@devkz_jobs · 25,747
Telegram ranks this channel #63 of 86 here — alongside 85 others — read 15 September 2026
The ExtremeCode Times
@extremecode · 35,836
Telegram ranks this channel #65 of 93 here — alongside 92 others — read 2 September 2026
Linux Academy
@linuxacademiya · 28,654
Telegram ranks this channel #69 of 84 here — alongside 83 others — read 9 September 2026
Avito Career
@avito_career · 67,411
Telegram ranks this channel #74 of 98 here — alongside 97 others — read 21 August 2026
DevOps
@DevOPSitsec · 23,865
Telegram ranks this channel #75 of 90 here — alongside 89 others — read 18 September 2026
DevOps by REBRAIN
@rebrain_devops · 28,751
Telegram ranks this channel #82 of 94 here — alongside 93 others — read 9 September 2026
IT Вакансии Казахстан
@workitkz · 36,880
Telegram ranks this channel #84 of 85 here — alongside 84 others — read 2 September 2026
Ozon Team
@ozonteam · 23,466
Telegram ranks this channel #86 of 89 here — alongside 88 others — read 19 September 2026
Профсоюз работников IT
@ruitunion · 36,055
Telegram ranks this channel #86 of 94 here — alongside 93 others — read 2 September 2026
FEDOR BORSHEV
@pmdaily · 23,644
Telegram ranks this channel #90 of 97 here — alongside 96 others — read 17 September 2026

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

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

“Николай Тузов” (@ntuzov), 16,923 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/ntuzov.

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.