Telegram RegisterThe public register of Telegram
Telegram profile photo for Астрал | Цифровые решения для бизнеса

Channel

Астрал | Цифровые решения для бизнеса

@gkastral

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,838subscribers

+31 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001498675349
TypeChannel
Username@gkastral
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/gkastral

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

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 word for word on 1 other registered channel. 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/4329 · this entry3 Aug 2026, 12:59 UTC@EPD_Astral/5653 Aug 2026, 13:06 UTC0.987 minutes
@gkastral/4332 · this entry5 Aug 2026, 05:59 UTC@EPD_Astral/5685 Aug 2026, 06:18 UTC0.9819 minutes
@EPD_Astral/5696 Aug 2026, 06:55 UTC@gkastral/4338 · this entry6 Aug 2026, 07:35 UTC0.9640 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@EPD_Astral5 (5/5 hand-verifiable sample passed)0.9814 minutes@EPD_Astral (32)

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. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 31 July 2026 to 7 August 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).

Across the whole group of 2, the earliest publisher we hold is @EPD_Astral. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

2,8022,8382,8206 August 2026 — 2,807 subscribers6 August 2026 — 2,807 subscribers6 August 2026 — 2,806 subscribers10 August 2026 — 2,805 subscribers13 August 2026 — 2,808 subscribers16 August 2026 — 2,805 subscribers19 August 2026 — 2,802 subscribers22 August 2026 — 2,809 subscribers25 August 2026 — 2,807 subscribers28 August 2026 — 2,806 subscribers31 August 2026 — 2,802 subscribers4 September 2026 — 2,820 subscribers9 September 2026 — 2,827 subscribers13 September 2026 — 2,833 subscribers17 September 2026 — 2,838 subscribers6 August 202617 September 2026
15 measurements spanning 43 days, net +31. 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 2,797–2,843 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 22:152,838+5
13 Sept 2026, 20:392,833+6
9 Sept 2026, 18:202,827+7
4 Sept 2026, 13:592,820+18
31 Aug 2026, 15:132,802-4
28 Aug 2026, 12:372,806-1
25 Aug 2026, 10:372,807-2
22 Aug 2026, 11:222,809+7
19 Aug 2026, 03:242,802-3
16 Aug 2026, 04:162,805-3
13 Aug 2026, 01:042,808+3
10 Aug 2026, 07:102,805-1
6 Aug 2026, 20:462,806-1
6 Aug 2026, 05:072,807no change
6 Aug 2026, 03:082,807first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

23 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 47.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1147.8%
🔥730.4%
👍417.4%
🤝14.35%

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 16 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 55 reactions 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 31 July 2026 to 7 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

7 Aug 2026, 11:02 UTC154 views2 reactionsread 7 August 2026
Photo

⚙️ Обновление API ЭПД в «Астрал.Платформе»: работа с экспедиторскими документами С 1 сентября 2026 года транспортная экспедиция переходит на обязательный электронный документооборот через ГИС ЭПД К обязательным относятся три типа документов: ✅ ЭПЭ — электронное поручение экспедитору ✅ ЭЭР — электронная экспедиторская расписка ✅ ЭСР — электронная складская расписка Сервис Астрал.Платформа реализовал работу с новыми

🔥2

7 Aug 2026, 09:54 UTC184 views3 reactionsread 7 August 2026
Photo

📍 ГК «Астрал» на форуме «Цифровая эволюция» в Калуге 6–7 августа в Калуге проходит VII Всероссийский форум «Цифровая эволюция» — на два дня площадка технопарка стала центром диалога между представителями власти, бизнеса и IT-сообщества 🤝🌐 Центральная тема этого года — «Госуслуги. Новые вызовы», а участников форум собрал из более чем 70 регионов страны ГК «Астрал» принимает активное участие в мероприятии. На нашем с

3

7 Aug 2026, 08:59 UTC198 views2 reactionsread 7 August 2026
Photo

⚠️ Бесплатное обучение закрывается сегодня ⚠️ Это последний день, когда регистрация открывает полный доступ к курсу без оплаты 💰 С завтрашнего дня такой возможности не будет — только платный доступ и отдельный тариф 🚫 Другого шанса зарегистрироваться на этих условиях не представится. Не откладывайте регистрацию 🎓 Пройти обучение Читать в Max

🔥2

6 Aug 2026, 13:03 UTC279 views6 reactionsread 7 August 2026
Photo

Работайте с электронными перевозочными документами в сервисе Доки 🚚 Ещё один сервис оператора Астрал научился работать с перевозочными документами. Раньше в Доки был только классический ЭДО: УПД, счета, договоры и другие документы. Теперь в нем появился раздел «Логистика» и работа с ЭПД Подписывайте ЭПД откуда удобно: 🖥 В 1С — бесплатный модуль для работы с ЭДО и ЭПД 🌐 В веб-кабинете — для тех, кто ведет учет в 1С,

4🔥1🤝1

6 Aug 2026, 10:59 UTC215 views2 reactionsread 7 August 2026
Photo

💡 ЭПД — это просто, когда есть те, кто объяснит Мы собрали всё, что нужно для уверенного перехода на электронные перевозочные документы. Без воды, на понятном языке, с разбором реальных ситуаций. 👥 А как это на деле — расскажут те, кто уже с нами. До 7 августа — обучение бесплатное. С 8 августа — только платный доступ 🎓 Хочу на обучение Читать в Max

1👍1

6 Aug 2026, 10:44 UTC179 views1 reactionsread 7 August 2026
Forwarded from @EPD_AstralPhoto

5 августа в рамках дискуссионного блока «От ЭПД к логистическим сервисам» обсуждали, что происходит с рынком после 1 сентября 2026 года, когда электронные перевозочные документы становятся обязательными для всех участников коммерческих грузоперевозок. Модерировала дискуссию Елена Кондратьева, эксперт в транспортной логистике и цифровой трансформации СТМЛК. В сессии приняли участие: представители цифровых транспортн

🔥1

6 Aug 2026, 07:35 UTC242 views3 reactionsread 7 August 2026
Photo

⚡️ До 1 сентября — 26 дней. Успеем разобраться? 10 августа в 11:00 — открытое обсуждение ЭПД для зерновой отрасли. Разберём: — что обязательно с 1 сентября и как работает переходный период — как ЭПД и ФГИС Зерно работают в связке — полевые сценарии: уборочная, ночные отгрузки, нет связи — как подготовиться, если ещё не начали Формат живой — вопросы принимаем прямо в эфире. 🌾 Зарегистрироваться

👍21

5 Aug 2026, 10:59 UTC359 viewsread 7 August 2026
Photo

Многие бухгалтеры до сих пор печатают документы из сервисов ЭДО и хранят их в папках, считая это оригиналом ❌ Но для налоговой бумажная копия электронного документа — это не полноценная замена электронного комплекта 📌 Юридическую силу и доказательственное значение имеет электронный комплект документов в установленном формате Если архив собран неправильно, возрастает риск споров по НДС и расходам 🛠 Как настроить хран

5 Aug 2026, 09:59 UTC250 views4 reactionsread 7 August 2026
Photo

📍 Практическая конференция по ЭДО и ЭПД при поддержке ФНС России 5–6 августа в Нижнем Новгороде проходит практическая конференция «Внедряем ЭДО. Нижний Новгород» при поддержке ФНС России. Главная тема — электронные перевозочные документы. ГК «Астрал», как оператор №1 Минтранса России, не могла пропустить это мероприятие. Здесь собрались и другие операторы, и представители бизнеса: крупные грузоотправители, перевозч

2👍1🔥1

5 Aug 2026, 08:33 UTC≈215 views5 reactionsread 6 August 2026
Photo

🚀 Новый канал поддержки «1С-Отчетность» в MAX Мы создали этот чат, чтобы сделать нашу помощь еще доступнее и удобнее для вас. В чате работает ИИ-помощник, обученный на реальных обращениях. По типовым вопросам он дает быстрый ответ. Если вопрос нестандартный, помощник сразу же подключит к диалогу нашего технического специалиста. Привычные каналы поддержки продолжают работать 💬 Открыть чат поддержки в MAX

5 Aug 2026, 05:59 UTC≈631 views3 reactionsread 6 August 2026
Photo

🌾 Зерно едет — а документы за ним успевают? В зерновой логистике свои правила: сезонность, объёмы, маршруты. И на переходе к ЭПД именно здесь больше всего вопросов 🤔 🎙Сегодня в 10:00 разбираем все отраслевые нюансы с экспертом Денисом Шалимовым, менеджером по продукту ЭПД SmartSeeds 📊 «ЭТрН в зерновой логистике» — Денис разберёт отраслевую практику и расскажет, как электронные перевозочные документы работают именн

4 Aug 2026, 12:05 UTC≈217 views1 reactionsread 6 August 2026
Photo

Пересчет НДФЛ при утрате сотрудником налогового резидентства — частая и непростая задача для бухгалтерии Нередко работодатель узнает об этом постфактум, и тогда возникают риски недоимки, риск штрафов и сложности с удержанием налога Ниже — пошаговый алгоритм действий: от пересчета налога до уведомления ФНС 📌 Шаг 1. Механика перерасчета Как только факт нерезидентства подтвержден, нужно определить статус сотрудника и

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

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.

Контур
@skbkontur_official · 25,242
Telegram ranks this channel #20 of 97 here — alongside 96 others — read 14 September 2026
Бухучет, налоги, 1С
@buhru · 35,379
Telegram ranks this channel #21 of 95 here — alongside 94 others — read 2 September 2026
Контур для бухгалтера
@externjournal · 43,297
Telegram ranks this channel #61 of 94 here — alongside 93 others — read 28 August 2026
Бухэксперт
@buhexpert8 · 75,798
Telegram ranks this channel #69 of 94 here — alongside 93 others — read 19 August 2026

This channel appears in 4 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Астрал | Цифровые решения для бизнеса” (@gkastral), 2,838 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/gkastral.

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.