Telegram RegisterThe public register of Telegram
Telegram profile photo for IT STAND

Channel

IT STAND

@ITSTAND_ORG

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

162,174subscribers

+14,175 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001252028555
TypeChannel
Username@ITSTAND_ORG
DescriptionIT STAND - Всё самое актуальное в мире IT 📣 Новости 🎙️Подкасты 👨‍🎓Обучение 🧠 Брейнштормы 📅 Ивенты 🤩 Интервью с профессионалами 🔍 Исследования и обзоры 📡 Технические трансляции 🤝 Сотрудничество @Fidelina_pro ❤️ https://www.youtube.com/@FIDELINA
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 live23 October 2026
Measurements held47
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/ITSTAND_ORG

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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

145,957162,174154,065.57 August 2026 — 147,999 subscribers7 August 2026 — 147,999 subscribers7 August 2026 — 147,923 subscribers8 August 2026 — 147,281 subscribers9 August 2026 — 146,422 subscribers10 August 2026 — 147,825 subscribers11 August 2026 — 148,335 subscribers12 August 2026 — 147,888 subscribers13 August 2026 — 145,957 subscribers14 August 2026 — 147,844 subscribers16 August 2026 — 149,503 subscribers17 August 2026 — 147,670 subscribers18 August 2026 — 147,429 subscribers19 August 2026 — 147,290 subscribers20 August 2026 — 146,905 subscribers22 August 2026 — 148,655 subscribers23 August 2026 — 148,044 subscribers25 August 2026 — 148,766 subscribers25 August 2026 — 148,356 subscribers27 August 2026 — 150,358 subscribers27 August 2026 — 151,281 subscribers29 August 2026 — 149,210 subscribers30 August 2026 — 151,614 subscribers31 August 2026 — 151,256 subscribers1 September 2026 — 150,242 subscribers2 September 2026 — 150,962 subscribers3 September 2026 — 152,857 subscribers5 September 2026 — 152,206 subscribers8 September 2026 — 152,092 subscribers11 September 2026 — 152,563 subscribers13 September 2026 — 153,309 subscribers15 September 2026 — 152,343 subscribers17 September 2026 — 153,282 subscribers19 September 2026 — 151,441 subscribers26 September 2026 — 155,546 subscribers4 October 2026 — 157,976 subscribers9 October 2026 — 158,014 subscribers13 October 2026 — 161,153 subscribers14 October 2026 — 159,799 subscribers15 October 2026 — 158,486 subscribers16 October 2026 — 162,002 subscribers18 October 2026 — 161,780 subscribers19 October 2026 — 161,650 subscribers20 October 2026 — 160,655 subscribers21 October 2026 — 158,946 subscribers22 October 2026 — 160,508 subscribers23 October 2026 — 162,174 subscribers7 August 202623 October 2026
47 measurements spanning 77 days, net +14,175. 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 143,524–164,607 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 47
Measured (UTC)SubscribersChange
23 Oct 2026, 18:08162,174+1,666
22 Oct 2026, 15:30160,508+1,562
21 Oct 2026, 09:09158,946-1,709
20 Oct 2026, 04:47160,655-995
19 Oct 2026, 04:27161,650-130
18 Oct 2026, 00:58161,780-222
16 Oct 2026, 22:59162,002+3,516
15 Oct 2026, 19:58158,486-1,313
14 Oct 2026, 17:49159,799-1,354
13 Oct 2026, 11:37161,153+3,139
9 Oct 2026, 07:02158,014+38
4 Oct 2026, 18:41157,976+2,430
26 Sept 2026, 22:01155,546+4,105
19 Sept 2026, 17:01151,441-1,841
17 Sept 2026, 01:37153,282+939
15 Sept 2026, 03:20152,343-966
13 Sept 2026, 10:19153,309+746
11 Sept 2026, 12:19152,563+471
8 Sept 2026, 20:56152,092-114
5 Sept 2026, 10:41152,206first reading

Engagement

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

ERR · 30 days
15.5%
avg views ÷ 162,174 subscribers
Avg views / post
25,100
64 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
64
of 203 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 23 October 2026
Posts held203 (30 July 2026 – 23 October 2026)
Views total1,603,896
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Oct 2026, 13:23 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
≈3,350
Videos
≈1,060
Links
≈3,540

Lifetime counters from Telegram’s own channel header, read 24 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
11m 28s
Average length
38s

Measured directly from 18 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.

Advertising

Ad load
1.48%
3 of 203 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
19,400
over 3 measured posts
Median views · rest
22,500
over 200 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
2W5zFHejStH111 August 202611 August 2026
2W5zFJYxXtM128 September 202628 September 2026
CQH36pWzJqVHp7WN6xtqq7QuZoM4vnKXoW2x9gvXf7fCHz11 September 20261 September 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 203 most recent posts we hold, published 30 July 2026 to 23 October 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

23 Oct 2026, 16:27 UTC≈42,200 viewsread 24 October 2026
Photo

Деплоим любые сайты за один клик — Cloudflare обновил сервис Drop, который поможет мгновенно выложить ваш веб-проект в сеть. • Максимально просто: перетаскиваем папку или ZIP-архив в браузер, и сайт сразу (!) появляется в интернете. • Без ограничений, без регистрации, без дополнительных установок, кода в терминале и прочих манипуляций. • Нюанс: без регистрации сайт проживет лишь час, но этого хватит, чтобы посмотрет…

22 Oct 2026, 07:00 UTC≈38,900 viewsread 24 October 2026
Photo

KuBeer Talks #4: год вместе с K8s-комьюнити 🍻 5 ноября снова собираемся в Москве на KuBeer Talks. Участников ждут короткие технические доклады, живые обсуждения и, конечно, общение с единомышленниками. В программе: 🔘Екатерина Низовцева — «Опыт работы с VTEP-схемой в Cilium» 🔘Артём Горячев — «Закон Гудхарта для бекапов K8s» 🔘 Открытый микрофон — для всех, кому есть чем поделиться И это не всё — скоро анонсируем е…

20 Oct 2026, 18:10 UTC≈25,900 viewsread 24 October 2026
Photo

«Ваш звонок очень важен для нас» Наверняка многим из вас эта фраза знакома. Запрос к нейросети тоже может застрять: одна копия модели перегружена, другая свободна, а запрос стоит в очереди к первой. В Deckhouse Platform теперь можно направлять запросы с учётом загрузки каждой копии модели. Как настроить это с помощью Gateway API Inference Extension, читайте на Хабре →

19 Oct 2026, 10:04 UTC≈47,400 viewsread 24 October 2026
Photo

Всем привет! На связи LordDeVops и я анонсирую цикл из 15 статей, в которых постараюсь вложить 1.5 года своей работы в роли Lead DevSecOps! На примере создания конвейера разработки безопасного ПО, мы рассмотрим самые актуальные практики на текущий момент, познакомимся с регулирующими документами и стандартами, а главное рассмотрим их пересечение с современной историей инцидентов! https://habr.com/ru/companies/rubyte…

19 Oct 2026, 09:44 UTC≈37,800 viewsread 24 October 2026
Photo

🔥 Фотоотчет по итогам DevOpsDays Almaty'26 Это было незабываемо! Благодарим каждого гостя, участника, спикера, спонсоров и представителей всех компаний — без вас такой конференции невозможно представить. Делимся фотоотчетом 📸 Увидите коллегу — перешлите фотку ему 😎 Скоро нарежем и зальем доклады на YouTube-канал 🫶

17 Oct 2026, 18:41 UTC≈31,600 viewsread 24 October 2026
Video

PHDays Fest 2027 🌟 Юбилейный киберфестиваль пройдет с 20 по 22 мая в «Лужниках». И мы сделаем его великолепным. В следующем году PHDays исполнится 15 лет. За это время изменился сам фестиваль, изменились технологии и то, насколько сильно они вошли в нашу жизнь. Но одно осталось прежним: интерес к людям, которые хотят понять, как все устроено, и попробовать сделать по-своему. Именно эта идея легла в основу концепц…

15 Oct 2026, 15:14 UTC≈26,900 viewsread 24 October 2026
Photo

Live: Kubernetes v1.37: Garhwal Рассмотрим нововведения: Storage Version Migration включён по умолчанию: больше никаких ручных миграций объектов в etcd после смены версии API Pod Certificates и ClusterTrustBundles: короткоживущие сертификаты для подов прямо из kubelet. Прощай, самописный mTLS на костылях? kube-proxy в режиме ipvs отправлен на пенсию. Это первый шаг к удалению, переезд на nftables больше не откладыва…

14 Oct 2026, 17:43 UTC≈28,600 viewsread 24 October 2026
Photo

Друзья, Kuber Conf переносится на 18 ноября АОТ создана для того, чтобы объединять инженеров и компании, развивать и распространять облачно-ориентированные технологии. Сейчас, без преувеличения, все специалисты нашей индустрии работают на пределе возможностей. Мы сосредоточены на самом необходимом — стабильной работе инфраструктуры и решении текущих проблем. Поэтому 22 октября мы не сможем провести конференцию тако…

13 Oct 2026, 18:22 UTC571 viewsread 24 October 2026
Photo

Фотографии DevOops 2026 готовы — ищите себя на снимках и делитесь в соцсетях с хештегом #devoops Ссылка на альбом

12 Oct 2026, 15:22 UTC≈45,300 viewsread 24 October 2026
Photo

Чем заняться вечером на DevOops Приходите на вечеринку в 18:00 в зале 2, чтобы поболтать в неформальной обстановке с другими участниками. А в 18:30, в зале 3 — можно выступить с докладом на Fail Talks или послушать коллег. Приходите откровенно поговорить о провалах в DevOps-практиках. Никакой записи и хейта — только полезный опыт.

12 Oct 2026, 14:25 UTC≈63,900 viewsread 24 October 2026
Photo

Хорошая книга может сэкономить недели костылей на проде. Собрали с Программным комитетом и издательством «Питер» подборку книг, к которым стоит обратиться при проектировании архитектуры, выстраивании CI/CD и защите инфраструктуры. А к двум из них ребята из ПК даже приложили руку в качестве научных редакторов. 1. Высоконагруженные приложения. Программирование, масштабирование, поддержка. 2-е изд. — М. Клеппман, К. Ри…

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

DevOps community for love
@devopsforlove · 44,598
#1
Технологический Болт Генона
@tech_b0lt_Genona · 10,279
#2
Мониторим ИТ
@monitorim_it · 8,562
#3
DeusOps
@deusops · 3,092
#4
Пятничный деплой
@count0_digest · 4,809
#5
DevOps Factory
@devops_factory · 1,723
#6
Мир ИТ c Антоном Павленко
@worlditech · 7,263
#7
Библиотека девопса | DevOps, SRE, Sysadmin
@devopsslib · 10,355
#8
Ever Secure
@ever_secure · 4,917
#9
🌚Пятисотые на проде😱
@code500 · 10,775
#10
The After Times
@theaftertimes · 16,855
#11
Синицын, бл🤬
@boombah_in_da_house · 1,688
#12
Кадровый Болт Генона
@kadr_b0lt_Genona · 2,054
#13
The Art Of Programming
@taoplive · 2,491
#14
Админим с Буквой
@bykvaadm · 6,521
#15
Yet Another Engineer
@engineer_another_yet · 558
#16
Слёрм
@slurmnews · 8,008
#17
Хабр
@habr_com · 133,497
#18
AppSec Journey
@AppSecJourney · 3,519
#19
Мишка на сервере
@jtprogru_channel · 1,335
#20
Inside Yandex Cloud
@cloud_track · 8,363
#21
что-то на техпиарном /Alina B.
@devsmm · 601
#22
Yandex Cloud
@yandexcloudnews · 24,023
#23
Управляемый нетворкинг
@ruleyournetworking · 441
#24
Уставший техдир
@tired_glebmikheev · 17,421
#25
Стачка [официальный канал]
@nastachku_ru · 1,810
#26
23derevo (18+)
@channel_23derevo · 1,844
#27
Yandex Infrastructure
@yandex_infrastructure · 4,818
#28
Полезняшки от "Разбора Полетов"
@razborfeed · 1,484
#29
Деплой | Ваня Ботанов
@dev_yttg · 7,201
#30
ProIT Fest
@proitfest · 2,485
#31
AppSec & Compliance
@AppSec_C8e · 578
#32
Подслушано в hoster.by
@hosterforpeople · 978
#33
DevOps MemOps
@devops_memops · 6,422
#34
DevOops — канал конференции
@devoops_channel · 521
#35
{ между скобок } анонсы 📣
@megdu_skobok · 4,643
#36
Профессиональная ИТ-конференция Синтез | Merge
@mergeconf · 2,450
#37
Эчпочмак, оставленный на послевчера
@achpochmac_yesterday · 3,273
#38
Лукоморье
@lukit_ru · 1,170
#39
IT-KB 🤖
@ITKB_channel · 8,067
#40
Pentest, AppSec, DevSecOps - Вакансии безопасников
@pentest_appsec_devsecops_job · 1,314
#41
WMX | Web & API Security
@WMXWAS · 679
#42
DevOps FM
@devops_fm · 5,291
#43
k8s (in)security
@k8security · 13,294
#44
DevOps&SRE Library
@devopslibrary · 19,887
#45
ITTales :(){ :|:& };:
@ittales · 1,790
#46
DevOps
@i_DevOps · 8,847
#47
DevSecOps Talks
@devsecops_weekly · 8,068
#48
Кубернетичек
@k8sjust · 1,082
#49
DevOps | Вопросы собесов
@easy_devops · 5,574
#50
Ænix.io
@aenix_io · 542
#51
Флант | Специалисты по DevOps и Kubernetes
@flant_ru · 2,178
#52
AWS Notes
@aws_notes · 5,849
#53
Devops Jobs — вакансии и резюме
@devops_jobs_feed · 22,178
#54
DevOps by REBRAIN
@rebrain_devops · 28,794
#55
Job for Sysadmin & DevOps
@fordevops · 5,016
#56
DevOps | Тесты
@easy_devops_tests · 2,691
#57
ArturKryukov video
@arturkryukov · 1,761
#58
Кубертатный период
@kubertat · 510
#59
Георгота в треде
@georgota · 964
#60
Вокруг Kubernetes в VK
@k8s_vk · 4,324
#61
Useful Tools | Linux | GitOps | DevOps
@gitgate · 6,794
#62
DevOps Deflope News
@devops_deflope · 5,837
#63
Hilbert Team | Эксперты в DevOps
@hilbertteam · 648
#64
GARDEN | DevOps
@devopsgarden · 4,369
#65
Bash Days | Linux | DevOps
@bashdays · 23,620
#66
Otabek Ismoilov
@Otabek_Ismoilov · 640
#67
linkmeup
@linkmeup_podcast · 17,457
#68
Кубернетика
@kubernetika · 752
#69
ДЕВОПСИНА | DevOps | Linux
@devopsina · 23,587
#70
DevOpsConf Channel
@DevOpsConfChannel · 1,924
#71
Вакансии по DevOps & SRE
@devopssjob · 4,515
#72
KazDevOps
@DevOpsKaz · 6,994
#73
Библиотека собеса по DevOps | вопросы с собеседований
@devops_interview_lib · 3,468
#74
DevOps
@DevOPSitsec · 23,918
#75
DevOpsMeets
@devopsmeets · 926
#76
Devops Bootcamp с Федосеевым
@devopsupgrade · 5,318
#77
Sysadmin Tools 🇺🇦
@sysadmin_tools · 4,237
#78
DevOps | Вакансии
@devops_vakansii · 3,903 (as read 9 September 2026)
#79
DevOps & SRE notes
@devops_sre_notes · 13,331
#80
DevOps для ДевоПсов
@devo_pes · 3,192
#81
Security Wine (бывший - DevSecOps Wine)
@sec_devops · 7,067
#82
Kubesploit
@Kubesploit · 2,135
#83
VK Cloud
@vk_cloud_news · 3,269
#84
/usr/bin
@usr_bin_linux · 4,956
#85
Холиварные аналитические посиделки
@holivarno · 1,123
#86
Вакансии DevOps и системных администраторов
@devops_job_geeklink · 3,981
#87
Devops
@dev_ops_info · 2,187
#88
sysadmin_jobs
@sysadmin_jobs · 4,501
#89
Богатый Программист
@rich_developer · 378
#90
Это работа для DevRel’a и Employer Brand менеджера
@devrel_jobs · 1,794
#91
Архитектура распределённых систем
@rsa_enc · 1,832
#92
Ксения Романова | DevRel и другие коммуникации в IT
@devrel_sklad · 909
#93
DevopsTrain
@devopstrain · 1,236
#94
realmanual.ru
@realmanual · 667
#95
ServerAdmin.ru
@srv_admin · 32,690
#96
Kubernative by Palark | Kubernetes news and goodies
@kubernative · 1,793
#97
Записки админа
@SysadminNotes · 12,772
#98

Read from Telegram’s recommendation API, most recently 9 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

DevOps community for love
@devopsforlove · 44,598
Telegram ranks this channel #14 of 95 here — alongside 94 others — read 9 September 2026
Devops Jobs — вакансии и резюме
@devops_jobs_feed · 22,178
Telegram ranks this channel #94 of 95 here — alongside 94 others — read 22 September 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 23 October 2026 — this entry's latest reading, not the date you are reading this.

“IT STAND” (@ITSTAND_ORG), 162,174 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/ITSTAND_ORG.

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.