Telegram RegisterThe public register of Telegram
Telegram profile photo for Nvda.ru

Channel

Nvda.ru

@nvda_ru

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

1,342subscribers

+19 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001255114179
TypeChannel
Username@nvda_ru
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live28 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 28 September 2026
On Telegramt.me/nvda_ru

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 18 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 why it has no browse page of its own yet.

Growth

1,3231,3421,332.57 August 2026 — 1,323 subscribers7 August 2026 — 1,324 subscribers12 August 2026 — 1,327 subscribers16 August 2026 — 1,328 subscribers19 August 2026 — 1,329 subscribers25 August 2026 — 1,332 subscribers1 September 2026 — 1,334 subscribers10 September 2026 — 1,333 subscribers18 September 2026 — 1,336 subscribers28 September 2026 — 1,342 subscribers7 August 202628 September 2026
10 measurements spanning 52 days, net +19. 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 1,320–1,345 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Sept 2026, 04:411,342+6
18 Sept 2026, 05:191,336+3
10 Sept 2026, 11:581,333-1
1 Sept 2026, 03:481,334+2
25 Aug 2026, 22:451,332+3
19 Aug 2026, 12:071,329+1
16 Aug 2026, 18:431,328+1
12 Aug 2026, 22:421,327+3
7 Aug 2026, 10:461,324+1
7 Aug 2026, 04:461,323first reading

Engagement

10 posts held, back to 1 July 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 10 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

15 reactions across 10 posts, in 2 distinct kinds. The most used accounts for 93.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1493.3%
🔥16.67%

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

Measured over the 10 most recent posts we hold, published 1 July 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

6 Aug 2026, 09:23 UTC271 views1 reactionsread 7 August 2026

NVDA 2026.2beta10 доступна для тестирования Десятая бета-версия NVDA 2026.2 теперь доступна для загрузки и тестирования. Изменения, внесенные в Beta 10: • Обновления переводов. • Исправлен ввод с сенсорного экрана, тачпада и мыши для Лупы. • Добавлены жесты для команд автоматической прокрутки Брайля. • Удалены режимы «Центрирование» и «Граница» из Лупы из-за ошибок в дизайне. • Удалена неработающая опция «Пользова…

👍1

28 Jul 2026, 12:19 UTC578 views1 reactionsread 7 August 2026

NVDA 2026.2beta9 доступна для тестирования Девятая бета-версия NVDA 2026.2 теперь доступна для загрузки и тестирования. Изменения, внесенные в Beta 9: • Обновлены переводы. • Обновлены разделы «Чтение по Брайлю» и «Скорость автоматической прокрутки» в руководстве пользователя. • Перемещение по предложениям в Word (alt+Стрелка вниз/alt+Стрелка вверх) в начале или конце документа теперь останавливается на месте вме…

👍1

21 Jul 2026, 08:08 UTC798 views2 reactionsread 7 August 2026

NVDA 2026.2beta8 доступна для тестирования Восьмая бета-версия NVDA 2026.2 теперь доступна для загрузки и тестирования. Изменения, внесенные в Beta 8: • Обновления переводов. • Улучшено поведение лупы при использовании высокого DPI-масштабирования. • Исправлена проблема, из-за которой лупа мешала открытию диалогов словарей. • Улучшена обработка ошибок при неудачной активации лупы. • По возможности блокируется ввод…

👍2

14 Jul 2026, 07:37 UTC817 views1 reactionsread 7 August 2026

NVDA 2026.2beta7 доступна для тестирования Седьмая бета-версия NVDA 2026.2 теперь доступна для загрузки и тестирования. Изменения, внесенные в Beta 7: • Обновлены переводы. • Исправлено: NVDA теперь предлагает перезапустить программу после обновления вместо выхода из системы. • Отменено исправление ошибки SAPI5 из бета-версии 6, которое вызывало проблемы при загрузке синтезаторов. • Исправлено чтение содержимого P…

👍1

8 Jul 2026, 08:21 UTC900 views1 reactionsread 7 August 2026

NVDA 2026.2beta6 доступна для тестирования Шестая бета-версия NVDA 2026.2 теперь доступна для загрузки и тестирования. Изменения, внесённые в бета-версии 6: • Обновления переводов. • Отображение диалога перезапуска после обновления из NVDA и обеспечение возможности сохранить текущую работу при перезапуске. • Исправление ошибки SAPI5: пропуск некорректных голосов вместо того, чтобы вызывать сбой всего драйвера. • …

👍1

4 Jul 2026, 08:51 UTC994 views3 reactionsread 7 August 2026

ChangeSounds (Изменение стандартных звуков NVDA). Дополнение ChangeSounds позволяет легко и быстро заменять стандартные звуковые сигналы NVDA на пользовательские звуки из выбранного звукового пакета. Дополнение предоставляет удобный диалог для выбора звукового пакета, предварительного прослушивания всех звуковых файлов и их автоматической замены в папке звуков NVDA. Звуковые пакеты хранятся в папке sound_packages вн…

👍2🔥1

4 Jul 2026, 08:14 UTC748 views1 reactionsread 7 August 2026

NeuralVoiceManager (Управления нейронными голосами Microsoft). Дополнение NeuralVoiceManager для NVDA предоставляет удобный интерфейс для управления нейронными голосами Microsoft. Вы можете просматривать голоса с фильтрацией по языку и стране. Установка выбранных голосов выполняется автоматически с отображением прогресса. Удаление установленных голосов происходит с подтверждением действия. Доступна загрузка голосовы…

👍1

1 Jul 2026, 17:37 UTC≈1,140 views2 reactionsread 7 August 2026
File

Собранные голоса для драйвера NeuralVoices. Норвежский букмал (Норвегия). Шведский (Швеция). Урду (Индия). Урду (Пакистан). Вьетнамский (Вьетнам). Валлийский (Великобритания). @nvda-ru @nvda_group

👍2

1 Jul 2026, 17:35 UTC963 views1 reactionsread 7 August 2026
File

Собранные голоса для драйвера NeuralVoices. Африкаанс (ЮАР). Каталонский (Испания). Исландский (Исландия). Ирландский (Ирландия). Японский (Япония). Корейский (Южная Корея). @nvda-ru @nvda_group

👍1

1 Jul 2026, 17:33 UTC665 views2 reactionsread 7 August 2026
File

Собранные голоса для драйвера NeuralVoices. Кантонский диалект (Китай). Китайский (Китай (Хэнань)). Китайский (Китай (Ляонин)). Китайский (Китай (Шэньси)). Китайский (Китай (Шаньдун)). Китайский (Китай (Сычуань)). Китайский (Китай). Китайский (Гонконг). Китайский (Тайвань). @nvda-ru @nvda_group

👍2

Showing the 10 most recent of 10 posts we hold for @nvda_ru. 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 4 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.

Mrutyunjaya Kabbur
@mrutyunjaya_kabbur · 20,731
Telegram ranks this channel #27 of 42 here — alongside 41 others — read 26 September 2026
АБАДДОН. Аудиокниги. УЖАСЫ. МИСТИКА. ТРИЛЛЕРЫ.
@abaddoyoutube · 56,962
Telegram ranks this channel #44 of 51 here — alongside 50 others — read 23 August 2026

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

“Nvda.ru” (@nvda_ru), 1,342 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/nvda_ru.

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.