Telegram RegisterThe public register of Telegram
Telegram profile photo for Елена Ильина - НК

Channel

Елена Ильина - НК

@buh_nalog_ekab

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

547subscribers

+64 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-1001537492814
TypeChannel
Username@buh_nalog_ekab
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live6 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/buh_nalog_ekab

Growth

4835515177 August 2026 — 483 subscribers8 August 2026 — 483 subscribers23 August 2026 — 551 subscribers29 August 2026 — 550 subscribers6 September 2026 — 547 subscribers5477 August 20266 September 2026
5 measurements spanning 29 days, net +64. 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 473–561 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 03:41547-3
29 Aug 2026, 10:08550-1
23 Aug 2026, 07:12551+68
8 Aug 2026, 04:32483no change
7 Aug 2026, 18:20483first reading

Engagement

5 posts held, back to 30 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 1 page 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 5 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
8s
Average length
4s

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

14 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 28.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍428.6%
🔥428.6%
321.4%
👏321.4%

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

Measured over the 5 most recent posts we hold, published 30 July 2026 to 6 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

6 Aug 2026, 17:48 UTC44 views3 reactionsread 8 August 2026
Video

❓ СПРОСИ У БОРИСОВНЫ Вопрос: Может ли самозанятый заключить договор с ООО, если платить будет не компания ему, а он компании? ООО должно изготовить и передать ему продукцию. Ответ: Да, может. Никакого запрета на такую сделку нет. В этом случае самозанятый выступает покупателем, а ООО — исполнителем и продавцом продукции. Можно заключить договор на изготовление и передачу продукции. Но есть несколько важных моменто

🔥2👍1

5 Aug 2026, 18:46 UTC72 views3 reactionsread 8 August 2026
Photo

❗️ФНС доначислила компании 675 000 рублей из-за самозанятых. В итоге — ноль Инспекция решила, что договоры с двумя самозанятыми фактически прикрывают трудовые отношения. Аргументы знакомые: ➖ сотрудничество длительное; ➖ выплаты регулярные и одинаковые; ➖ работы выполняются лично; ➖ подрядчики экономически зависят от заказчика. Компания спорила почти год — и добилась полной отмены доначислений по НДФЛ и страховым в

👍3

4 Aug 2026, 18:04 UTC79 views2 reactionsread 8 August 2026

🚨 ФНС видит больше, чем цифры в РСВ: как не попасть на зарплатную комиссию в 2026 году Контроль за зарплатами и неформальной занятостью усиливается. Теперь налоговая сопоставляет между собой данные РСВ, 6-НДФЛ, ККТ, сведения о самозанятых и среднеотраслевые показатели. Проще говоря, ФНС собирает информацию о работодателе как пазл. И если детали не сходятся — сначала потребует пояснения, а затем материалы могут перед

🔥2

30 Jul 2026, 17:52 UTC129 views6 reactionsread 8 August 2026
Video

❓ СПРОСИ У БОРИСОВНЫ Вопрос: Компания применяет УСН «доходы минус расходы». В 2025 году оплатили поставщику товары или услуги, но расходы не учли, потому что не было документов. В 2026 году поставщик передал документы. Можно ли теперь уменьшить налог за 2026 год? 👩‍💼 Ответ Борисовны: можно, но не во всех случаях. Здесь важно определить не дату получения документа, а дату самой хозяйственной операции. ✅ Если в 202

3👏3

Showing the 5 most recent of 5 posts we hold for @buh_nalog_ekab. 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.

Mentions

Named by 5 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“Елена Ильина - НК” (@buh_nalog_ekab), 547 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/buh_nalog_ekab.

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.