Telegram RegisterThe public register of Telegram
Telegram profile photo for ГИИС ДМДК official

Channel

ГИИС ДМДК official

@giis_dmdk_official

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

5,912subscribers

+47 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001344477313
TypeChannel
Username@giis_dmdk_official
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 live13 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/giis_dmdk_official

Topic

Other / unclassifiable — 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 87% 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

5,8655,9165,890.57 August 2026 — 5,865 subscribers7 August 2026 — 5,865 subscribers10 August 2026 — 5,868 subscribers13 August 2026 — 5,867 subscribers16 August 2026 — 5,869 subscribers19 August 2026 — 5,871 subscribers23 August 2026 — 5,874 subscribers29 August 2026 — 5,872 subscribers1 September 2026 — 5,876 subscribers10 September 2026 — 5,874 subscribers13 September 2026 — 5,872 subscribers17 September 2026 — 5,875 subscribers4 October 2026 — 5,874 subscribers10 October 2026 — 5,873 subscribers14 October 2026 — 5,869 subscribers17 October 2026 — 5,867 subscribers20 October 2026 — 5,886 subscribers22 October 2026 — 5,897 subscribers25 October 2026 — 5,901 subscribers28 October 2026 — 5,911 subscribers30 October 2026 — 5,913 subscribers5 November 2026 — 5,916 subscribers9 November 2026 — 5,909 subscribers13 November 2026 — 5,912 subscribers5,9127 August 202613 November 2026
24 measurements spanning 98 days, net +47. 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 5,857–5,924 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
13 Nov 2026, 13:565,912+3
9 Nov 2026, 06:515,909-7
5 Nov 2026, 17:175,916+3
30 Oct 2026, 23:165,913+2
28 Oct 2026, 08:575,911+10
25 Oct 2026, 18:255,901+4
22 Oct 2026, 22:565,897+11
20 Oct 2026, 00:145,886+19
17 Oct 2026, 03:405,867-2
14 Oct 2026, 11:495,869-4
10 Oct 2026, 16:585,873-1
4 Oct 2026, 19:415,874-1
17 Sept 2026, 06:205,875+3
13 Sept 2026, 16:595,872-2
10 Sept 2026, 08:405,874-2
1 Sept 2026, 00:165,876+4
29 Aug 2026, 01:465,872-2
23 Aug 2026, 02:275,874+3
19 Aug 2026, 21:225,871+2
16 Aug 2026, 18:075,869first reading

Engagement

33 posts held, back to 26 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
45.7%
avg views ÷ 5,912 subscribers
Avg views / post
2,700
7 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
7
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 28 October 2026
Posts held33 (26 September 2025 – 28 October 2026)
Views total18,900
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 01:50 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.

Recent posts

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

28 Oct 2026, 12:18 UTC≈1,790 viewsread 5 November 2026
Photo

Замена устаревших методов Уважаемые пользователи! Информируем, что с 01.12.2026 выводятся из эксплуатации устаревшие методы сервиса интеграции ГИИС ДМДК: SendBuyingupAction; SendSpecificationCancel; SendSpecificationRecover; SendSpecificationOperation; SendGemsInsert; SendGemsRemove; SendBatchReturn. После 01.12.2026 запросы к указанным методам будут отклоняться. Взамен устаревших методов требуется использовать сле…

28 Oct 2026, 12:05 UTC≈1,960 viewsread 5 November 2026
Photo

Смена устаревших методов сервиса интеграции Уважаемые пользователи! Информируем, что с 01.12.2026 выводятся из эксплуатации устаревшие методы сервиса интеграции ГИИС ДМДК: SendBuyingupAction; SendSpecificationCancel; SendSpecificationRecover; SendSpecificationOperation; SendGemsInsert; SendGemsRemove; SendBatchReturn. После 01.12.2026 запросы к указанным методам будут отклоняться. Взамен устаревших методов требуетс…

27 Oct 2026, 10:55 UTC≈2,150 viewsread 5 November 2026
Photo

ТЕХНИЧЕСКИЕ РАБОТЫ 28 ОКТЯБРЯ 2026 Уважаемые пользователи! В связи проведением технического обслуживания инфраструктуры ГИИС ДМДК работа портала ГИИС ДМДК будет временно приостановлена в среду 28 октября 2026 г. с 02:00 (МСК) до 06:00 (МСК).

26 Oct 2026, 13:24 UTC≈2,750 viewsread 5 November 2026
Photo

О ДОСТУПЕ В ГИИС ДМДК Уважаемые пользователи! Сообщаем, что в связи с обновлением сертификата подтверждения подлинности (проверки) сервера ГИИС ДМДК для успешного входа в личный кабинет ГИИС ДМДК на клиентском компьютере должна быть установлена последняя сертифицированная версия криптопровайдера Крипто Про CSP 5.0.13003. Для взаимодействия с сервисом интеграции необходимо использовать сертифицированное приложение …

20 Oct 2026, 08:21 UTC≈3,420 viewsread 5 November 2026
Photo

О ВОССТАНОВЛЕНИИ РАБОТЫ СЕРВИСА ИНТЕГРАЦИИ Уважаемые пользователи! Информируем о полном восстановлении работы сервиса интеграции ГИИС ДМДК. Запросы в сервис интеграции, по которым ранее были получены ошибки обработки, требуется направить повторно.

19 Oct 2026, 12:46 UTC≈3,260 viewsread 5 November 2026
Photo

ОБНОВЛЕНИЕ СИСТЕМЫ 20 ОКТЯБРЯ 2026 ГОДА Уважаемые пользователи! В связи с обновлением системы работа портала ГИИС ДМДК будет временно приостановлена во вторник 20 октября 2026 г. с 06:00 (МСК) до 06:30 (МСК).

19 Oct 2026, 11:10 UTC≈3,570 viewsread 5 November 2026
Photo

ОБ ОБРАБОТКЕ ЗАПРОСОВ ИНТЕГРАЦИОННЫМ СЕРВИСОМ И ТМ Уважаемые пользователи! В настоящее время могут наблюдаться задержки и сбои при обработке запросов в сервисе интеграции и при отправке сведений о кассовых чеках из транспортного модуля в ГИИС ДМДК. Мы работаем над устранением и дополнительно сообщим о восстановлении полноценной работы сервисов. Обращаем внимание, что сведения о кассовых чеках сохраняются в трансп…

14 Oct 2026, 06:11 UTC≈3,680 viewsread 5 November 2026
Photo

ОБНОВЛЕНИЕ СИСТЕМЫ 17 ОКТЯБРЯ 2026 Уважаемые пользователи! В связи с обновлением системы до версии 7.2.1 работа портала ГИИС ДМДК будет временно приостановлена в субботу 17 октября 2026 г. с 06:00 (МСК) до 12:00 (МСК).

5 Oct 2026, 12:40 UTC≈4,070 viewsread 5 November 2026
Photo

ОБНОВЛЕНИЕ СИСТЕМЫ 06 ОКТЯБРЯ 2026 Уважаемые пользователи! В связи с обновлением системы работа портала ГИИС ДМДК будет временно приостановлена 06 октября 2026 г. с 06:00 (МСК) до 09:00 (МСК). В рамках обновления будет осуществлен запуск интеграции между ГИИС ДМДК и ГИС «Электронный знак» Республики Беларусь. О дате выхода релиза 7.2.1 будет сообщено дополнительно.

21 Sept 2026, 08:06 UTC≈5,770 viewsread 5 November 2026
Photo

ОБНОВЛЕНИЕ ГИИС ДМДК ДО ВЕРСИИ 7.2.1 Уважаемые пользователи! Готовится к выпуску новый релиз 7.2.1 ГИИС ДМДК. Среди значительных изменений функциональных возможностей системы: - интеграция с ГИС «Электронный знак» Республики Беларусь; - новый тип квитанции – «Договор ОМС»; - возможность повторного направления партий с отказом в физической маркировке на опробование и клеймение; - автоматический вывод партий из обор…

11 Sept 2026, 10:58 UTC≈3,920 viewsread 5 November 2026
Photo

О ТЕСТОВЫХ КОНТУРАХ ГИИС ДМДК Уважаемые пользователи! Информируем, что тестовый контур dmdk2.goznak.ru более недоступен для участников. Ознакомление с новым функционалом ГИИС ДМДК и его тестирование необходимо осуществлять на тестовом контуре dmdk.goznak.ru.

11 Sept 2026, 10:56 UTC≈3,320 viewsread 5 November 2026
Photo

О ТЕСТОВЫХ КОНТУРАХ ГИИС ДМДК Уважаемые пользователи! Информируем, что тестовый контур dmdk2.goznak.ru более недоступен для участников. Ознакомление с новым функционалом ГИИС ДМДК и его тестирование необходимо осуществлять на тестовом контуре dmdk.goznak.ru.

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

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.

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

“ГИИС ДМДК official” (@giis_dmdk_official), 5,912 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/giis_dmdk_official.

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.