Telegram RegisterThe public register of Telegram
Telegram profile photo for 1С ЭПД: Перевозки без бумаг

Channel

1С ЭПД: Перевозки без бумаг

@EPD_Astral

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

10,608subscribers

+995 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002203159938
TypeChannel
Username@EPD_Astral
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held53
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/EPD_Astral

Topic

Education — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 79% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@gkastral/43293 Aug 2026, 12:59 UTC@EPD_Astral/565 · this entry3 Aug 2026, 13:06 UTC0.987 minutes
@gkastral/43325 Aug 2026, 05:59 UTC@EPD_Astral/568 · this entry5 Aug 2026, 06:18 UTC0.9819 minutes
@EPD_Astral/569 · this entry6 Aug 2026, 06:55 UTC@gkastral/43386 Aug 2026, 07:35 UTC0.9640 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@gkastral5 (5/5 hand-verifiable sample passed)0.9814 minutesthis entry (3–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 2 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 61 comparable posts for this entry, running 17 July 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @EPD_Astral — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 12 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

9,61310,76810,190.56 August 2026 — 9,613 subscribers6 August 2026 — 9,619 subscribers9 August 2026 — 9,662 subscribers12 August 2026 — 9,735 subscribers15 August 2026 — 9,778 subscribers19 August 2026 — 9,822 subscribers21 August 2026 — 10,132 subscribers23 August 2026 — 10,143 subscribers25 August 2026 — 10,175 subscribers26 August 2026 — 10,204 subscribers27 August 2026 — 10,237 subscribers27 August 2026 — 10,275 subscribers28 August 2026 — 10,302 subscribers29 August 2026 — 10,301 subscribers1 September 2026 — 10,354 subscribers2 September 2026 — 10,389 subscribers3 September 2026 — 10,432 subscribers4 September 2026 — 10,708 subscribers7 September 2026 — 10,723 subscribers10 September 2026 — 10,755 subscribers12 September 2026 — 10,751 subscribers15 September 2026 — 10,753 subscribers18 September 2026 — 10,768 subscribers30 September 2026 — 10,749 subscribers6 October 2026 — 10,725 subscribers10 October 2026 — 10,710 subscribers13 October 2026 — 10,708 subscribers15 October 2026 — 10,704 subscribers16 October 2026 — 10,699 subscribers17 October 2026 — 10,696 subscribers18 October 2026 — 10,693 subscribers19 October 2026 — 10,686 subscribers20 October 2026 — 10,683 subscribers21 October 2026 — 10,681 subscribers22 October 2026 — 10,677 subscribers23 October 2026 — 10,675 subscribers25 October 2026 — 10,672 subscribers26 October 2026 — 10,665 subscribers27 October 2026 — 10,662 subscribers28 October 2026 — 10,657 subscribers29 October 2026 — 10,648 subscribers30 October 2026 — 10,646 subscribers31 October 2026 — 10,641 subscribers1 November 2026 — 10,640 subscribers2 November 2026 — 10,636 subscribers3 November 2026 — 10,637 subscribers4 November 2026 — 10,635 subscribers5 November 2026 — 10,632 subscribers6 November 2026 — 10,629 subscribers7 November 2026 — 10,627 subscribers9 November 2026 — 10,626 subscribers10 November 2026 — 10,627 subscribers12 November 2026 — 10,608 subscribers10,6086 August 202612 November 2026
53 measurements spanning 99 days, net +995. 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 9,440–10,941 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 53
Measured (UTC)SubscribersChange
12 Nov 2026, 17:2010,608-19
10 Nov 2026, 16:2110,627+1
9 Nov 2026, 01:0810,626-1
7 Nov 2026, 11:3110,627-2
6 Nov 2026, 11:5710,629-3
5 Nov 2026, 14:1610,632-3
4 Nov 2026, 13:3810,635-2
3 Nov 2026, 10:4010,637+1
2 Nov 2026, 07:4010,636-4
1 Nov 2026, 04:4910,640-1
31 Oct 2026, 07:4010,641-5
30 Oct 2026, 04:3010,646-2
29 Oct 2026, 08:0110,648-9
28 Oct 2026, 09:3710,657-5
27 Oct 2026, 12:3010,662-3
26 Oct 2026, 11:2810,665-7
25 Oct 2026, 12:1510,672-3
23 Oct 2026, 17:0610,675-2
22 Oct 2026, 14:0510,677-4
21 Oct 2026, 05:3010,681first reading

Engagement

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

ERR · 30 days
26.0%
avg views ÷ 10,608 subscribers
Avg views / post
2,760
4 posts measured
Reaction rate
0.616%
reactions ÷ views · ER floor
Posts in window
4
of 63 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 11 November 2026
Posts held63 (17 July 2026 – 11 November 2026)
Views total11,040
Reactions total68
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 10:20 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
11m 30s
Average length
3m 50s

Measured directly from 3 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

687 reactions across 59 posts, in 23 distinct kinds. The most used accounts for 40.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤27840.5%
🔥14020.4%
👍12418.0%
👎466.70%
🙏263.78%
🤝142.04%
✍81.16%
🤔81.16%
👏60.873%
😁60.873%
👌40.582%
👻30.437%
😡30.437%
😭30.437%
🙉30.437%
🥰30.437%
🥴30.437%
🏆20.291%
🤡20.291%
🤯20.291%
3 further kinds30.437%

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

Measured over the 63 most recent posts we hold, published 17 July 2026 to 11 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: 1 of 4 posts held from the last 30 days (25.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).

11 Nov 2026, 10:31 UTC≈1,170 views6 reactionsread 12 November 2026
Photo

📣 Что изменится для бизнеса в налогах в 2027 году? Об этом 17 ноября расскажет Надежда Самкова, ведущий эксперт-консультант по налогообложению, на нашей ежегодной Большой конференции «Изменения 2027 для бухгалтера» Следом — Владислав Волков из ФНС России: что нового ожидается в НДФЛ и страховых взносах в 2027 году и на что обратить внимание в отчетности. Для тех, кто работает с ЭПД, Елена Слуцкая, руководитель Уче…

❤6

10 Nov 2026, 07:23 UTC≈1,710 views9 reactionsread 12 November 2026
Photo

🚛 ЭТрН уже обязательна, а вопросов по ней много Документ застрял в роуминге, грузополучатель не подписывает, непонятно, что с подписью водителя, а ошибку в отправленной накладной не исправить. Мы собрали еще 5 проблем, с которыми сталкиваются чаще всего, и дали краткий ответ Часто возникают вопросы по ЭТрН, ролям и подписанию? Все разобрано в практическом курсе по 1С-ЭПД и Доки – инструкции, видео и ответы на часты…

❤5👍3🙏1

28 Oct 2026, 07:09 UTC≈3,810 views24 reactionsread 12 November 2026
Photo

❗️️️️️️️ С 8 по 18 октября сервис 1С-ЭПД работал с перебоями из-за инцидента в дата-центре. Сейчас все восстановлено, и мы доставляем документы, которые не дошли клиентам за это время Чтобы 1С загрузила эти документы, нужно сдвинуть дату получения документов в 1С назад, на дату их отправки. Это займет 2 минуты 1️⃣️️️️️️ Откройте Администрирование → Обмен электронными документами 2️⃣️️️️️️ Разверните раздел Обмен с…

❤17🙏4✍3

14 Oct 2026, 11:29 UTC≈4,350 views29 reactionsread 12 November 2026
Forwarded from @gkastral

Обновление от 14 октября Обещали держать вас в курсе. Главное на сейчас: мы завершили перенос большей части сервисов на новую инфраструктуру и восстанавливаем их работоспособность. Восстановление еще не завершено, но по ключевым сервисам уже есть сроки. Сегодня до 18:00 планируем возобновить работу 1С:Хаба — облачной инфраструктуры, через которую пользователи 1С-ЭДО и 1С-ЭПД взаимодействуют с операторами. После зап…

👍12❤9🔥6✍1🤔1

13 Oct 2026, 14:32 UTC≈3,850 views16 reactionsread 12 November 2026
Forwarded from @gkastral

❗️ Минтранс подтвердил: на время сбоя перевозочные документы можно оформлять на бумаге 13 октября Минтранс России опубликовал сообщение о работе сервисов АО «Калуга Астрал». Министерство подтвердило: перевозчики, грузоотправители и экспедиторы, которые работают через ИС ЭПД «Калуга Астрал», на период сбоев могут оформлять перевозочные документы на бумаге Что это значит для вас Пока идет сбой, транспортные накладны…

❤8🤝6🔥2

12 Oct 2026, 11:56 UTC≈3,500 views19 reactionsread 12 November 2026
Forwarded from @gkastralPhoto

⚠️ Возможны перебои в работе сервисов ГК «Астрал»: когда заработают и что делать сейчас 📍 Что произошло 8 октября дата-центры Яндекса, где работают сервисы ГК «Астрал», пострадали от атак БПЛА. Наша система распределенного хранения данных позволила оперативно восстановить работу сервисов. Подключили резервные дата-центры, но из-за большого объема данных не в полной мере успели реализовать перенос 11 октября новые …

❤9🙏8🤔2

11 Oct 2026, 06:32 UTC≈2,930 views14 reactionsread 12 November 2026
Forwarded from @gkastralPhoto

Уважаемые клиенты! Наблюдаются временные перебои в работе сервисов ГК «Астрал», в том числе сервисов Электронной отчетности, ЭДО и ЭПД. Если при отправке или подписании документов возникает ошибка, пожалуйста, повторите попытку позднее. Документы и данные сохраняются, дополнительных действий с вашей стороны не требуется. Причина — новые атаки БПЛА повредили инфраструктуру дата-центра Яндекса во Владимире, что затр…

❤7🙏6🔥1

10 Oct 2026, 08:07 UTC≈3,220 views7 reactionsread 12 November 2026

⚡️ Обновление на 11:10 10 октября: Сервисы ГК «Астрал» работают в штатном режиме Уважаемые клиенты! Сервисы ГК «Астрал» работают в штатном режиме. Очереди накопившихся документов обработаны, задержек при отправке не наблюдается. Если вы столкнулись со сложностями при работе с сервисами 8 или 9 октября, вы можете использовать официальные письма для предоставления в контролирующие органы. Письма доступны по ссылке: …

❤6👍1

9 Oct 2026, 12:37 UTC≈2,610 views9 reactionsread 11 November 2026
Forwarded from @gkastralPhoto

Статус по работе сервисов ГК «Астрал» на 09.10.1026 10:00 Уважаемые клиенты! Сервисы электронного документооборота работают в штатном режиме, очередей нет. Сервисы электронных перевозочных документов работают. Из-за обработки накопившихся запросов сохраняются значительные очереди. Команда работает над их сокращением. Работоспособность сервиса 1С-Отчетность частично восстановлена. Передача отчетности на сервер Опер…

❤7🤔1🙏1

8 Oct 2026, 12:38 UTC≈2,950 views21 reactionsread 11 November 2026
Forwarded from @gkastralPhoto

⚡️Обновление по работе сервисов ГК «Астрал» Уважаемые клиенты! Восстановлена работоспособность сервисов ГК «Астрал», нарушенная в результате инцидента в дата-центре Яндекса. Из-за обработки накопившихся запросов возможны очереди и увеличение времени выполнения отдельных операций. Следить за актуальным статусом можно на сайте astral.ru и на ресурсах 1С. 🤩Если у вас остаются вопросы о возможных штрафах за использова…

🔥8❤5✍4🙏4

8 Oct 2026, 06:24 UTC≈2,570 views15 reactionsread 11 November 2026
Forwarded from @gkastralPhoto

Уважаемые клиенты! Сейчас возможны временные перебои в работе сервисов ГК «Астрал», в том числе в сервисах электронной отчётности, ЭДО и ЭПД. Причина – инцидент в дата-центре Яндекса, который затронул работу ряда облачных сервисов. Статус работоспособности и восстановления сервисов Яндекс: https://status.yandex.cloud/ru/incidents/2092?retpath=%2Fru%2Ftimeline Специалисты Яндекса и ГК «Астрал» работают над восстанов…

❤8🤔4🤝3

7 Oct 2026, 13:04 UTC≈2,900 views17 reactionsread 11 November 2026
Photo

Ошибки в ЭПД? Чаще всего они уже исправлены Многие ошибки при работе с ЭТрН, ЭЗЗ и поручениями экспедитору уже исправили. Чтобы их не встретить, достаточно двух проверок. Шаг 1. Проверьте, обновлена ли конфигурация Актуальные версии: 1С:Бухгалтерия 8 — 3.0.207 1С:Бухгалтерия некоммерческой организации — 3.0.206 1С:Управление нашей фирмой — 3.0.14 1С:Управление торговлей 11 — 11.6.1.70 1С:ERP Управление предприятие…

❤7👍4🔥4👏2

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

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.

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

“1С ЭПД: Перевозки без бумаг” (@EPD_Astral), 10,608 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/EPD_Astral.

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.