Telegram RegisterThe public register of Telegram
Telegram profile photo for Новости ФНС России

Channel

Новости ФНС России

@fnsru

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

7,257subscribers

-161 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001190461523
TypeChannel
Username@fnsru
DescriptionНеофициальный канал с новостями Федеральной налоговой службы Купить рекламу: https://telega.in/c/fnsru
Created15 January 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/fnsru

Topic

Other / unclassifiable — 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 70% 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. 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
@fnsru/7435 · this entry1 Nov 2026, 09:01 UTC@nalog_gov_ru/34761 Nov 2026, 09:02 UTC0.96under a minute
@fnsru/7443 · this entry3 Nov 2026, 12:42 UTC@nalog_gov_ru/34813 Nov 2026, 13:51 UTC0.9568 minutes
@nalog_gov_ru/34938 Nov 2026, 09:00 UTC@fnsru/7457 · this entry8 Nov 2026, 09:05 UTC0.955 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
@nalog_gov_ru8 (8/8 hand-verifiable sample passed)0.974 minutes@nalog_gov_ru (5–3)

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. 2 of the 2 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 58 comparable posts for this entry, running 27 July 2026 to 10 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).

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

Growth

7,2577,4187,337.56 August 2026 — 7,418 subscribers6 August 2026 — 7,417 subscribers9 August 2026 — 7,410 subscribers12 August 2026 — 7,401 subscribers16 August 2026 — 7,395 subscribers19 August 2026 — 7,387 subscribers22 August 2026 — 7,377 subscribers25 August 2026 — 7,370 subscribers28 August 2026 — 7,366 subscribers1 September 2026 — 7,363 subscribers4 September 2026 — 7,358 subscribers10 September 2026 — 7,347 subscribers13 September 2026 — 7,336 subscribers18 September 2026 — 7,329 subscribers27 September 2026 — 7,310 subscribers5 October 2026 — 7,294 subscribers11 October 2026 — 7,281 subscribers15 October 2026 — 7,279 subscribers17 October 2026 — 7,275 subscribers20 October 2026 — 7,272 subscribers27 October 2026 — 7,271 subscribers30 October 2026 — 7,267 subscribers1 November 2026 — 7,262 subscribers4 November 2026 — 7,260 subscribers7 November 2026 — 7,257 subscribers6 August 20267 November 2026
25 measurements spanning 94 days, net -161. 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 7,233–7,442 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
7 Nov 2026, 16:567,257-3
4 Nov 2026, 17:497,260-2
1 Nov 2026, 21:097,262-5
30 Oct 2026, 00:087,267-4
27 Oct 2026, 03:557,271-1
20 Oct 2026, 22:557,272-3
17 Oct 2026, 20:007,275-4
15 Oct 2026, 06:007,279-2
11 Oct 2026, 18:577,281-13
5 Oct 2026, 11:387,294-16
27 Sept 2026, 14:597,310-19
18 Sept 2026, 04:597,329-7
13 Sept 2026, 22:007,336-11
10 Sept 2026, 10:207,347-11
4 Sept 2026, 21:217,358-5
1 Sept 2026, 03:277,363-3
28 Aug 2026, 20:127,366-4
25 Aug 2026, 11:427,370-7
22 Aug 2026, 19:347,377-10
19 Aug 2026, 04:247,387first reading

Engagement

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

ERR · 30 days
3.72%
avg views ÷ 7,257 subscribers
Avg views / post
270
25 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
25
of 89 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 10 November 2026
Posts held89 (27 July 2026 – 10 November 2026)
Views total6,747
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 02:45 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
≈3,350
Videos
≈184
Links
≈4,790

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
4m 31s
Average length
1m 30s

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.

Recent posts

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

10 Nov 2026, 07:33 UTC125 viewsread 11 November 2026

ФНС: оформление перевозочной документации на бумаге не лишает права на вычеты и учет затрат https://www.v2b.ru/2026/11/10/fns-oformlenie-perevozochnoy-dokumentatsii-na-bumage-ne-lishaet-prava/ С сентября текущего года вступила в силу норма, обязывающая участников грузоперевозок составлять перевозочную документацию в электронной форме (п. 4 ст. 5 Закона № 149-ФЗ от 07.06.2025). В связи с этим ФНС России выпустила раз…

10 Nov 2026, 07:11 UTC121 viewsread 11 November 2026
Photo

🌐 ФНС России Хотите узнать больше о налоге на прибыль❓ ▶ Тогда приглашаем на вебинар с нашим специалистом. 👆 Участие бесплатное. Информация о регистрации на сайте: clck.ru/3WprMB Подробная программа вебинара — в карточках ➡

9 Nov 2026, 14:04 UTC121 viewsread 11 November 2026

⚖️ Подборка правовых каналов в Telegram и MAX Сделали для вас подборку полезных каналов в Telegram и Макс, которые помогут вам регулярно получать ценную информацию и уверенно ориентироваться в правовом поле. ▫️Новости ВС РФ - Telegram | MAX ▫️Конституционный Суд РФ - Telegram | MAX ▫️Правовые акты РФ - Telegram | MAX ▫️Законопроекты РФ - Telegram | MAX ▫️Кадровику - Telegram | MAX ▫️Госзакупки и тендеры - Telegram …

8 Nov 2026, 14:05 UTC185 viewsread 11 November 2026

🌐 ФНС России 🧐 МИФ: Если у квартиры несколько собственников, налог на имущество уплачивает только один из них Пояснение: Если квартира находится в общей долевой собственности, каждый собственник самостоятельно уплачивает налог на имущество физических лиц пропорционально своей доле. Например, если квартира принадлежит двум собственникам в равных долях, каждому из них начисляется налог исходя из 1/2 доли в праве соб…

8 Nov 2026, 09:05 UTC197 viewsread 11 November 2026
Photo

🌐 ФНС России Что публиковали на прошедшей неделе❓ ⚪ Опубликовали рекомендации по отражению в ЭПД товаров, подлежащих учету в ГИС ⚪ Утвердили изменения в форматы фискальных данных ⚪ Опубликовали заключительную серию видео об изменениях в налоговых уведомлениях за 2025 год ⚪ Напомнили, что не позднее 1 декабря необходимо оплатить налог по налоговым уведомлениям за 2025 год ⚪ Ответили на вопросы по кассовым чекам …

6 Nov 2026, 09:28 UTC219 viewsread 11 November 2026

‌Некоторые реквизиты в формате грузовой накладной стали необязательными: рекомендация ФНС С 1 сентября этого года перевозить грузы можно только при наличии электронной накладной, в том числе на перевозку грузов авиатранспортом. Документ должен соответствовать утвержденному формату. Для грузовой накладной его разработала и утвердила ФНС приказом № ЕД-1-26/276@ от 27.04.2026. Все цифровые перевозочные документы посту…

6 Nov 2026, 08:30 UTC152 viewsread 11 November 2026
Photo

🌐 ФНС России Напоминаем, как рассчитывается НДФЛ с процентов по банковским вкладам В налоговых уведомлениях за 2025 год граждане могут увидеть не только общую сумму НДФЛ к уплате, но и детализацию налога с указанием источников дохода и применяемых ставок. Подробную информацию смотрите в видео. 📆 Напоминаем, что срок оплаты налоговых уведомлений за 2025 год – не позднее 1 декабря 2026 года.

6 Nov 2026, 08:00 UTC169 viewsread 11 November 2026

В УФНС рассказали, как и за что могут заблокировать счет УФНС Ямало-Ненецкого автономного округа напоминает: несвоевременная уплата налога превращает его в задолженность. Тогда применяются меры, регламентированные Налоговым кодексом РФ. Если срок внесения обязательного платежа пропущен, начисляются пени и возникает риск приостановки операций по счёту. По статье 46 НК РФ после вступления в силу решения о взыскании б…

5 Nov 2026, 14:24 UTC188 viewsread 11 November 2026
Photo

🌐 ФНС России Сегодня узнаем детали оформления кассовых чеков 🔎 Читайте их в статье.

4 Nov 2026, 07:30 UTC212 viewsread 11 November 2026
Photo

🌐 ФНС России 🇷🇺 С Днём народного единства! Россия – многонациональная страна с богатым историческим и культурным наследием. Представители более 190 народностей и этнических групп, говорящие на более чем 270 языках и диалектах, вместе составляют единое целое. Нас объединяют общая история, уважение к традициям, любовь к Родине и ответственность за ее будущее. День народного единства напоминает о силе сплоченности, …

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

Posts recorded as deleted after publishing

We recorded 5 posts on @fnsru as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
4 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
1

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 9 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.

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.

ЛьготОтвет
@lgototvet · 21,865
Telegram ranks this channel #13 of 51 here — alongside 50 others — read 21 September 2026
Детские пособия I ЛьготОтвет
@detskoe_posobie · 48,406
Telegram ranks this channel #18 of 62 here — alongside 61 others — read 26 August 2026
Конституционный Суд
@ksrf_ru · 28,083
Telegram ranks this channel #67 of 85 here — alongside 84 others — read 10 September 2026
ФНС России
@nalog_gov_ru · 89,464
Telegram ranks this channel #69 of 96 here — alongside 95 others — read 17 August 2026
Юридические Тонкости
@sivakovairina · 109,170
Telegram ranks this channel #78 of 83 here — alongside 82 others — read 2 September 2026

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

“Новости ФНС России” (@fnsru), 7,257 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/fnsru.

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.