Telegram RegisterThe public register of Telegram
Telegram profile photo for Инфосистемы Джет

Channel

Инфосистемы Джет

@jetinfosystems

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

6,499subscribers

+236 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001040611026
TypeChannel
Username@jetinfosystems
CreatedBetween 1 January 2016 and 31 October 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/jetinfosystems

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

6,2276,4996,3636 August 2026 — 6,263 subscribers6 August 2026 — 6,263 subscribers9 August 2026 — 6,255 subscribers12 August 2026 — 6,249 subscribers15 August 2026 — 6,244 subscribers18 August 2026 — 6,239 subscribers20 August 2026 — 6,238 subscribers24 August 2026 — 6,244 subscribers27 August 2026 — 6,243 subscribers30 August 2026 — 6,233 subscribers1 September 2026 — 6,227 subscribers6 September 2026 — 6,239 subscribers11 September 2026 — 6,244 subscribers14 September 2026 — 6,306 subscribers18 September 2026 — 6,290 subscribers27 September 2026 — 6,292 subscribers5 October 2026 — 6,295 subscribers12 October 2026 — 6,321 subscribers15 October 2026 — 6,374 subscribers18 October 2026 — 6,381 subscribers21 October 2026 — 6,374 subscribers23 October 2026 — 6,407 subscribers26 October 2026 — 6,488 subscribers29 October 2026 — 6,493 subscribers1 November 2026 — 6,488 subscribers4 November 2026 — 6,477 subscribers7 November 2026 — 6,478 subscribers10 November 2026 — 6,499 subscribers6 August 202610 November 2026
28 measurements spanning 97 days, net +236. 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 6,186–6,540 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
10 Nov 2026, 15:596,499+21
7 Nov 2026, 12:356,478+1
4 Nov 2026, 04:216,477-11
1 Nov 2026, 02:206,488-5
29 Oct 2026, 08:586,493+5
26 Oct 2026, 10:096,488+81
23 Oct 2026, 19:376,407+33
21 Oct 2026, 06:076,374-7
18 Oct 2026, 10:066,381+7
15 Oct 2026, 07:216,374+53
12 Oct 2026, 14:566,321+26
5 Oct 2026, 19:396,295+3
27 Sept 2026, 23:376,292+2
18 Sept 2026, 17:216,290-16
14 Sept 2026, 19:026,306+62
11 Sept 2026, 07:416,244+5
6 Sept 2026, 06:206,239+12
1 Sept 2026, 21:596,227-6
30 Aug 2026, 05:366,233-10
27 Aug 2026, 10:386,243first reading

Engagement

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

ERR · 30 days
17.8%
avg views ÷ 6,499 subscribers
Avg views / post
1,160
15 posts measured
Reaction rate
1.70%
reactions ÷ views · ER floor
Posts in window
15
of 43 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 9 November 2026
Posts held43 (15 July 2026 – 9 November 2026)
Views total17,347
Reactions total295
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Nov 2026, 17:17 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
5m 45s
Average length
1m 26s

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

672 reactions across 38 posts, in 23 distinct kinds. The most used accounts for 16.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 547447155149770249910916.2%
custom 54206264656307482227010.4%
👍6810.1%
custom 5188344386471104373679.97%
😁649.52%
custom 5282964792334636962487.14%
custom 5188306586463928877466.85%
✍294.32%
🥰233.42%
custom 5474549316175564042223.27%
custom 5474453499750155858192.83%
👾172.53%
💯172.53%
😎172.53%
🤩172.53%
🆒101.49%
🤣91.34%
🎉71.04%
custom 533017581588161901950.744%
👏30.446%
3 further kinds50.744%

Custom emoji. 8 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 42 of the 43 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 764 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 43 most recent posts we hold, published 15 July 2026 to 9 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 15 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).

9 Nov 2026, 11:21 UTC614 views13 reactionsread 9 November 2026
Photo

Последний день регистрации на техническую конференцию «Бункер» и «Цитадель» У кибератаки нет расписания. Злоумышленникам уже достаточно считаных минут, чтобы поставить под угрозу критичные системы. Что останется от вашей инфраструктуры после такой атаки? И как быстро вы сможете вернуться к работе? Уже завтра, 10 ноября, на конференции «Бункер» и «Цитадель»: архитектура, которая переживет атаку» разберем самые акту…

custom 51883443864711043735👍3🥰3✍2

9 Nov 2026, 08:02 UTC705 views12 reactionsread 9 November 2026
Photo

#JetInfo Распродажи не ждут Для маркетплейсов ноябрьская распродажа 11.11 — это серьезный экзамен для инфраструктуры. ↗️В колонке для JetInfo Дмитрий Герасимов, управляющий директор по информационным технологиям Lamoda, поделился, как компания обеспечивает непрерывность бизнес-процессов в сезон пиковых нагрузок. Эксперт рассказал, как тестировать инфраструктуру под реальные сценарии распродаж и переживать сбои без…

custom 54745493161755640424✍3👍3custom 54206264656307482222

6 Nov 2026, 12:04 UTC928 views19 reactionsread 9 November 2026
Photo

Время отвлечься от рабочих задач Сделали небольшую игру, чтобы хорошо завершить неделю. Правила простые: открывайте карточки, ищите совпадения и проверяйте, насколько хорошо работает ваша память. Никаких созвонов, дедлайнов и сложных ТЗ в эту пятницу. 💎Джет |🔥За хорошую память 💙 IT Elements|💬MAX

👾8custom 51883443864711043736🥰4custom 54206264656307482221

5 Nov 2026, 13:57 UTC≈1,110 views13 reactionsread 9 November 2026
Photo

#мероприятие Как выполнить требования приказа № 117 ФСТЭК России, если на рынке пока нет всех необходимых сертифицированных средств защиты? Какие средства защиты необходимо использовать, как подтвердить выполнение требований при аттестации и что изменится в регулировании? 11 ноября на вебинаре мы расскажем об опыте реализации требований, взаимодействии с регулятором и предстоящих изменениях. В программе: ▫️Выбор …

custom 51883443864711043737✍3👍3

5 Nov 2026, 11:26 UTC≈1,070 views11 reactionsread 9 November 2026
Photo

#экспертиза Резервные копии есть. А бизнес точно восстановится после атаки? Сегодня в 17:00 эксперты «Инфосистемы Джет» обсудят это в эфире программы «Деловой Гамбит» на радио Mediametrics. Наши спикеры: 💫Юрий Семенюков, директор центра инфраструктурных решений; 💫Антон Шипулин, руководитель направления непрерывности ИТ. Вместе с ведущей Екатериной Ярцевой поговорят о том: ↗️какие сценарии атак бизнес до сих пор не…

custom 51883443864711043734custom 54206264656307482224custom 51883065864639288773

4 Nov 2026, 07:03 UTC≈1,190 views13 reactionsread 9 November 2026

Posted without readable text

💯5custom 51883443864711043735custom 54745493161755640423

3 Nov 2026, 12:17 UTC≈1,580 views13 reactionsread 9 November 2026
Photo

#экспертиза Серверы становятся мощнее, а дата-центры — горячее И дело не только в охлаждении: на кону электроснабжение, архитектура и сама логика строительства ЦОД. ИИ требует все больше вычислительных мощностей. А значит, дата-центрам приходится меняться: выдерживать новые нагрузки, потреблять больше энергии и отводить всё больше тепла. Но просто поставить более мощные серверы не получится. Российский рынок уже по…

👍5custom 51883443864711043734✍3custom 54206264656307482221

2 Nov 2026, 15:23 UTC≈1,020 views16 reactionsread 9 November 2026
Video message

Video message, posted without a caption

😁9🎉4custom 51883443864711043733

2 Nov 2026, 15:23 UTC≈1,230 views24 reactionsread 9 November 2026
Photo

#мероприятие Он родился! Наши партнеры из «Лаборатории Числитель» отмечают первый день рождения KuBeer Talks. Это место, где эксперты и кубер-энтузиасты собираются вместе в неформальной обстановке. Участников ждут короткие технические доклады, живые обсуждения, споры, шутки и общение с единомышленниками. Присоединяемся к празднику вместе с нашими коллегами: ⬆️Артем Горячев, начальник отдела DevOps-решений, принес…

custom 518834438647110437312👍6✍5custom 54206264656307482221

30 Oct 2026, 15:14 UTC≈1,360 views25 reactionsread 9 November 2026
Photo

#мероприятие Не можем отпустить вас на выходные без полезного Атака на Binance с оценкой ущерба в $6,3 млрд. Вредоносный экземпляр расширения Claude Code с SSH-бэкдором. Две свежие новости и один важный вопрос — насколько защищена инфраструктура, в которой создается и поставляется ваше ПО? GitLab, Jenkins, CI/CD-раннеры, Registry, Kubernetes — все эти компоненты связаны между собой через сервисные учётные записи, т…

custom 51883065864639288779👍7custom 54206264656307482225custom 51883443864711043734

30 Oct 2026, 11:39 UTC≈1,430 views84 reactionsread 9 November 2026
Photo

ДомОфис с привидениями Хотели предложить неожиданным экскурсантам помощь, но не смогли их догнать — все-таки сквозь стены и серверные мы ходить не умеем.

😁48custom 542062646563074822214👍8custom 51883443864711043737😱3👏2🌚1🤩1

29 Oct 2026, 13:17 UTC≈1,340 views10 reactionsread 7 November 2026
Photo

#мероприятие Собираемся обсуждать нагрузку Мы в нашем центре сетевых решений провели независимое тестирование отечественного сетевого оборудования — проверили заявленные вендорами возможности в условиях, максимально приближенных к реальной эксплуатации. 12 ноября на митапе Network Scream разберем результаты испытаний, обсудим выводы и ответим на вопросы. Когда: 12 ноября, начало в 18:30 Где: Москва, м. Лубянка, оф…

custom 51883443864711043735custom 52829647923346369623custom 51883065864639288772

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

Named by 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

Kaspersky
@kasperskylab_ru · 28,873
Telegram ranks this channel #47 of 96 here — alongside 95 others — read 9 September 2026
Positive Technologies
@Positive_Technologies · 29,469
Telegram ranks this channel #54 of 87 here — alongside 86 others — read 9 September 2026
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,134
Telegram ranks this channel #90 of 98 here — alongside 97 others — read 4 October 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Инфосистемы Джет” (@jetinfosystems), 6,499 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/jetinfosystems.

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.