Telegram RegisterThe public register of Telegram
Telegram profile photo for Official Jieshuo screenreader RU

Channel

Official Jieshuo screenreader RU

@official_jieshuo_ru

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

346subscribers

+2 since we began measuring on 2 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002030030654
TypeChannel
Username@official_jieshuo_ru
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live12 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/official_jieshuo_ru

Growth

3443463452 September 2026 — 344 subscribers3 September 2026 — 344 subscribers12 September 2026 — 346 subscribers2 September 202612 September 2026
3 measurements spanning 10 days, net +2. 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 344–346 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 01:56346+2
3 Sept 2026, 00:05344no change
2 Sept 2026, 04:30344first reading

Engagement

14 posts held, back to 30 September 2024 — 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 14 posts for this entry, the most recent from 5 November 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 1 post, in 2 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤375.0%
👎125.0%

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

Measured over the 14 most recent posts we hold, published 30 September 2024 to 5 November 2024, 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

5 Nov 2024, 16:06 UTC≈1,770 views4 reactionsread 2 September 2026

Всем доброго времени! Мы рады сообщить вам, о воссоеденении двух русскоязычных групп и каналов Jieshuo screenreader! Теперь будет одна группа и канал как прежде, только еще с некоторыми изменениями и дополнениями. Данная группа и канал будут существовать до тех пор, пока все подписчики не перейдут в новую группу и канал. Мы ценем и уважаем каждого нашего подписчика, и в связи с этим, мы вам предлогаем осуществить…

❤3👎1

5 Nov 2024, 15:23 UTC≈1,520 viewsread 2 September 2026

Внутренняя бета версия Jieshuo 20241105. Разработчик не предоставил информацию.

4 Nov 2024, 14:26 UTC≈1,380 viewsread 2 September 2026

Внутренняя бета версия Jieshuo 20241104. Оптимизирована скорость объявления громкости.

1 Nov 2024, 15:22 UTC≈1,040 viewsread 2 September 2026

Внутренняя бета версия Jieshuo 20241101. Добавлена функция описания видео ( находится на этапе тестирования). Теперь к имени файла перед экспортом текста добавляется расширение txt.

26 Oct 2024, 07:23 UTC853 viewsread 2 September 2026

Внутренняя бета версия Jieshuo 20241025. Оптимизированно скорость подробного и простого описания изображения, распознавание значков, распознавание лиц. Заменена большая модель в голосовом запросе на Blue Heart.

18 Oct 2024, 14:17 UTC≈1,380 views0 reactionsread 2 September 2026

Внутренняя бета версия Jieshuo 20241018. Заменён движок автоматического распознавания OCR. (Поддерживается Английский, Китайский, Японский, Корейский, Русский, Немецкий, Французский, Итальянский, Португальский и Испанский). Оптимизировано отображение элементов при навигации Jieshuo. Оптимизировано скорость ответа в диалоге с генеративной большой моделью. @official_jieshuo_ru

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

Mentions

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.

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.

"О ТОМ О СЁМ" о Xiaomi, Android и Технике
@otomosem · 33,136
Telegram ranks this channel #32 of 40 here — alongside 39 others — read 4 September 2026
AndroidInsider.ru #новости
@androidinsider_ru · 24,549
Telegram ranks this channel #70 of 86 here — alongside 85 others — read 16 September 2026
AdGuard [RU]
@adguardru · 35,978
Telegram ranks this channel #88 of 89 here — alongside 88 others — read 2 September 2026

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

“Official Jieshuo screenreader RU” (@official_jieshuo_ru), 346 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/official_jieshuo_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.