Telegram RegisterThe public register of Telegram

Channel

CTT.BY Инфоканал EDI-провайдера СТТ

@cttby

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

851subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001683918060
TypeChannel
Username@cttby
Description📝 Тут про EDI и Электронные накладные пишут интересно 👍 👉 Информационный канал для бизнеса про EDI технологии, электронный документооборот, электронные накладные от первого EDI-провайдера СТТ | Современные технологии торговли https://ctt.by
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/cttby

Growth

8517 Aug 2026, 17:29 — 851 subscribers8 Aug 2026, 01:19 — 851 subscribers7 Aug 2026, 17:298 Aug 2026, 01:19
2 measurements taken within a single day. 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 850–852 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 01:19851no change
7 Aug 2026, 17:29851first reading

Engagement

20 posts held, back to 24 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
58.4%
avg views ÷ 851 subscribers
Avg views / post
497
10 posts measured
Reaction rate
1.35%
reactions ÷ views · ER floor
Posts in window
10
of 20 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. It is computed over the 9 of 10 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 August 2026
Posts held20 (24 June 20265 August 2026)
Views total4,969
Reactions total61
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:19 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
25
Videos
5
Links
395

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

134 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 22.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤝3022.4%
2921.6%
👍2619.4%
👌2518.7%
🔥2014.9%
👏32.24%
10.746%

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

Measured over the 20 most recent posts we hold, published 24 June 2026 to 5 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

5 Aug 2026, 10:08 UTC321 views8 reactionsread 8 August 2026
Photo

Уважаемые клиенты и партнеры❗️ По инициативе Министерства по налогам и сборам РБ EDI-провайдер СТТ проводит опрос среди субъектов хозяйствования о наличии заинтересованности в трансграничном ЭДО (ТЭДО) со странами: Азербайджан, Армения, Казахстан, Кыргызстан, Таджикистан, Узбекистан. 🤩Будем вам признательны, если вы сможете найти 5 минут и заполните форму. Напоминаем, что в EDI-системе СТТ уже сейчас доступен Тран

3🤝3👍2

30 Jul 2026, 08:07 UTC462 views3 reactionsread 8 August 2026
Forwarded from @mnsrb

🇧🇾 О возврате прослеживаемого товара физическим лицом в розничный магазин В связи с поступающими запросами от субъектов хозяйствования, осуществляющих розничную торговлю, Министерство по налогам и сборам информирует, что с порядком возврата физическими лицами товаров, реализованных им в розничной торговой сети, можно ознакомиться на официальном сайте МНС.

3

29 Jul 2026, 08:07 UTC484 views7 reactionsread 8 August 2026

Онлайн-форум для белорусских производителей и экспортеров «Маркировка 2026» ✅30.07.2026 пройдет практический онлайн-форум, где примет участие Юрий Исаревич — заместитель директора по развитию бизнеса ООО «Современные технологии торговли». Юрий выступит с темой: «Трансграничный электронный документооборот для маркируемой продукции в Российской Федерации». ✅ Дата и время проведения мероприятия: 30.07.2026, 10:00-15:0

🔥51👍1

28 Jul 2026, 06:24 UTC446 views7 reactionsread 8 August 2026

Уважаемые клиенты и партнеры! 2 августа в 12:00 запланировано обновление EDI-системы СТТ. 🔄 Обновление будет длиться около 1 часа. В этот период система будет недоступна для передачи сообщений. После завершения обновления сообщения, накопившиеся в очереди, будут обработаны и доставлены вашим контрагентам. Подробно об изменениях здесь ❗️Просим вас учитывать данную информацию при планировании операционных процессов

👍3👌21🤝1

24 Jul 2026, 08:48 UTC581 views5 reactionsread 8 August 2026

❗️Уважаемые клиенты и партнеры! По информации РУП «Национальный центр электронных услуг» сообщаем, что в период с 23:00 24 июля 2026 г. до 06:00 25 июля 2026 на стороне НЦЭУ будут проводиться плановые технологические работы. В указанный период возможны перебои в доступе к информационным системам, услугам и сервисам НЦЭУ. 😒 Данные технологические работы могут повлиять на работоспособность программного комплекса сист

👌3🤝2

23 Jul 2026, 10:13 UTC537 views9 reactionsread 8 August 2026
Photo

✈️ Новый сервис от EDI-провайдера СТТ. Конвертер, помогающий превратить белорусскую эТН/эТТН или документ DESADV в готовый черновик ДОПП для подачи в систему СПОТ. ✅Предлагаем пройти короткий опрос, так мы будем знать, как сделать ЭДО удобнее: https://docs.google.com/forms/d/e/1FAIpQLSe2JiZSBC1eRp_6f9pBD8Y8mbSzbtSCrDhJnCHxSa5hgw2-FA/viewform?usp=dialog

7🔥2

22 Jul 2026, 13:51 UTC435 viewsread 8 August 2026
Forwarded from @mnsrb

⚠️ МНС ИНФОРМИРУЕТ ⚠️ О технических работах, проводимых в ГИС «Электронный знак» ❗️По информации, поступившей от РУП «Издательство «Белбланкавыд», в период с 25.07.2026 по 26.07.2026 в ГИС «Электронный знак» будут проводиться плановые технические работы, в связи с чем доступ ко всем сервисам ГИС «Электронный знак» (в том числе API, личные кабинеты, мобильные приложения) будет отсутствовать. 🔴 После завершения осно

20 Jul 2026, 14:41 UTC510 views9 reactionsread 8 August 2026

📱С 1 августа 2026 года в РФ вступают в силу новые требования по обязательной маркировке мяса и мясной продукции. Для белорусских производителей и экспортеров это означает необходимость перестройки процессов документооборота и учета. В I этап обязательной маркировки (с 01.08) попадают готовые или консервированные продукты из мяса, мясных субпродуктов или крови прочие. Что нужно сделать: 〰️ зарегистрироваться/быть за

👍43🤝2

16 Jul 2026, 15:47 UTC602 views8 reactionsread 8 August 2026

UPD: работоспособность ПК СПТ восстановлена. Обмен электронными накладными с прослеживаемыми товарами работает в штатном режиме.

👍5👌3

16 Jul 2026, 14:36 UTC591 views5 reactionsread 8 August 2026

❗️Уважаемые клиенты и партнеры! Сегодня 16.07.2026 с 16:35 зафиксированы проблемы работоспособности программного комплекса «Система прослеживаемости товаров». У некоторых пользователей возможны ошибки при отправке электронных документов с прослеживаемыми товарами. О восстановлении работоспособности передачи информации в ПК СПТ сообщим дополнительно. ___ С уважением, команда техподдержки EDI-системы СТТ

🤝4👌1

8 Jul 2026, 10:36 UTC870 views8 reactionsread 8 August 2026

❗️Уважаемые клиенты! По сообщению Министерства по налогам и сборам сегодня 08.07.2026 в период с 18:00 по 20:00 запланировано проведение технических работ на серверах программного комплекса «Система прослеживаемости товаров». В связи с проведением работ в ПК СПТ в указанный период у некоторых пользователей EDI-системы СТТ возможны ошибки при отправке электронных документов с прослеживаемыми товарами. __ С уважение

👌4🤝4

7 Jul 2026, 09:12 UTC580 views4 reactionsread 8 August 2026

❗️Уважаемые клиенты! 😒7 июля 2026 года (сегодня) в 18:00 в EDI-системе СТТ будут проводиться технические работы длительностью до 10 минут. В этот период сервис будет недоступен. Просим вас учитывать данную информацию в планировании своей работы. В случае возникновения вопросов просьба обращаться в службу технической поддержки. Приносим извинения за возможные неудобства. __ С уважением, команда техподдержки EDI-сис

👌2🤝2

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

Citation-graph rank

Citation-graph rank — 777,515 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 1 registered channel — 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.

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

“CTT.BY Инфоканал EDI-провайдера СТТ” (@cttby), 851 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/cttby.

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.