Telegram RegisterThe public register of Telegram
Telegram profile photo for Документооборот для ресторана DocsInBox

Channel

Документооборот для ресторана DocsInBox

@docsinbox

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

10,318subscribers

-102 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-1001604723319
TypeChannel
Username@docsinbox
Created18 October 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live30 August 2026
Measurements held23
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/docsinbox

Growth

10,31710,42410,370.56 August 2026 — 10,420 subscribers6 August 2026 — 10,420 subscribers6 August 2026 — 10,424 subscribers7 August 2026 — 10,420 subscribers8 August 2026 — 10,415 subscribers9 August 2026 — 10,413 subscribers10 August 2026 — 10,411 subscribers11 August 2026 — 10,410 subscribers12 August 2026 — 10,416 subscribers13 August 2026 — 10,417 subscribers14 August 2026 — 10,414 subscribers16 August 2026 — 10,412 subscribers17 August 2026 — 10,336 subscribers18 August 2026 — 10,343 subscribers19 August 2026 — 10,340 subscribers21 August 2026 — 10,335 subscribers23 August 2026 — 10,334 subscribers24 August 2026 — 10,335 subscribers26 August 2026 — 10,333 subscribers27 August 2026 — 10,335 subscribers28 August 2026 — 10,318 subscribers29 August 2026 — 10,317 subscribers30 August 2026 — 10,318 subscribers10,3186 August 202630 August 2026
23 measurements spanning 24 days, net -102. 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 10,301–10,440 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
30 Aug 2026, 09:2810,318+1
29 Aug 2026, 11:1810,317-1
28 Aug 2026, 13:1210,318-17
27 Aug 2026, 15:4710,335+2
26 Aug 2026, 17:2810,333-2
24 Aug 2026, 20:2610,335+1
23 Aug 2026, 03:4810,334-1
21 Aug 2026, 19:3710,335-5
19 Aug 2026, 19:5810,340-3
18 Aug 2026, 16:5610,343+7
17 Aug 2026, 17:5610,336-76
16 Aug 2026, 15:2210,412-2
14 Aug 2026, 22:3710,414-3
13 Aug 2026, 16:1610,417+1
12 Aug 2026, 16:5310,416+6
11 Aug 2026, 18:3210,410-1
10 Aug 2026, 16:3410,411-2
9 Aug 2026, 17:4110,413-2
8 Aug 2026, 20:0010,415-5
7 Aug 2026, 18:0410,420first reading

Engagement

40 posts held, back to 17 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 40 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
13.1%
avg views ÷ 10,318 subscribers
Avg views / post
1,350
29 posts measured
Reaction rate
0.547%
reactions ÷ views · ER floor
Posts in window
29
of 40 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 27 of 29 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 28 August 2026
Posts held40 (17 July 202628 August 2026)
Views total39,207
Reactions total198
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 17:17 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.

Reaction mix

262 reactions across 34 posts, in 14 distinct kinds. The most used accounts for 41.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10841.2%
🔥7127.1%
😁3714.1%
custom 5425139694574796906197.25%
🍾72.67%
👍51.91%
🙏51.91%
👀20.763%
😍20.763%
😘20.763%
💯10.382%
😱10.382%
🤪10.382%
🥰10.382%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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

Measured over the 40 most recent posts we hold, published 17 July 2026 to 28 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

28 Aug 2026, 08:35 UTC650 views2 reactionsread 29 August 2026

🦷 Какие операции ресторана сегодня чаще всего вызывают вопросы у налоговой? 🦷 Как подготовиться к требованиям и камеральным проверкам ФНС без лишнего стресса? 🦷 Какие ошибки приводят к доначислениям, пеням и штрафам? Рассказали вчера на вебинаре. Смотрите запись здесь 🤓

2

27 Aug 2026, 13:27 UTC870 views2 reactionsread 29 August 2026

Если деньги улетают, как птицы на юг через пару месяцев, можно и нужно оптимизировать закупки. Но вот загвоздка: можно наворотить столько ошибок, что продукты станут только дешевле, а лучшие поставщики не захотят с вами работать 👶 В статье рассказываем, как оптимизировать закупки правильно и наконец-то работать выгоднее. ❤️ Читаем статью здесь.

1👍1

27 Aug 2026, 10:50 UTC872 views6 reactionsread 29 August 2026

Налоговый вебинар — через 10 минут. Хотите знать, как не привлекать внимание налоговой и вообще работать без оплошностей? 👌 Подключайтесь!

🔥3🙏2👀1

27 Aug 2026, 07:57 UTC925 views6 reactionsread 29 August 2026
Photo

Сегодня — о наболевшем... Но есть и хорошие новости: в 14:00 на вебинаре расскажем, как снизить налоговую нагрузку и вообще делать поменьше налоговых ошибок. Присоединяйтесь.

😁6

26 Aug 2026, 08:13 UTC≈1,000 views5 reactionsread 29 August 2026
Photo

Помните, что у DocsInBox есть книга? Можете послушать или прочитать где вам удобно 🧑‍🦱 В книге «Люди важнее бумаг» человеческим языком рассказываем, как работает бизнес, в котором хорошо всем: владельцам, сотрудникам и клиентам. А еще там прикольные истории и анекдоты 😉 Мы не семья. Это вообще ужасный штапм: в семье тебя любят просто потому, что ты есть. А вот в команде нужно приносить пользу. Доксы — это банда, мы

🔥32

25 Aug 2026, 08:05 UTC≈1,110 views3 reactionsread 29 August 2026

Топ-3 вебинара лета 🧓 Если вы были в отпуске или просто пропустили полезный контент — ничего, разберемся! Ловите записи: ЭТрН без страшилок 🔵Основное про ЭТрН: что это, как с ним работать, кому понадобится 🔵Разбор конкретных кейсов настоящих ресторанов 🔵Ответы на распространенные и нестандартные вопросы про ЭДО в ресторанах Проверки Роспотребнадзора 2026: разбираемся в ХАССП 🔵Как связаны ХАССП и СанПиНы 🔵Определяе

3

24 Aug 2026, 09:58 UTC≈1,110 views3 reactionsread 29 August 2026
Photo

Хоть бизнес вести непросто тебе, Ресторатор, не охай, не ахай! Продал карбонару — налоги плати, Не платишь — тогда иди… Вот так вот вдохновляет ФНС... А еще она вдохновила нас на вебинар с Натальей Горячей о том, как в 2026 году заплатить налоги правильно, не переплатить и не вызвать излишний интерес у налоговой. И мы вас на него приглашаем! Налоговые ошибки ресторана 2026: что сегодня привлекает внимание ФНС и как

3

21 Aug 2026, 11:04 UTC≈1,380 views5 reactionsread 29 August 2026
Photo

Дорогие наши бухгалтеры 🧑‍🦱 Напоминаем, что двери нашего закрытого сообщества бухгалтеров-калькуляторов всегда для вас открыты. Читайте подробнее и регистрируйтесь здесь 💙

4🔥1

21 Aug 2026, 07:56 UTC≈1,360 views6 reactionsread 29 August 2026

Вчера был вебинар про ошибки в учёте, и вот что мы на нем обсудили: 🔵Топ-5 критических ошибок бухгалтера-калькулятор 🔵Как перестать тушить пожары в конце каждого периода 🔵В основе любого корректного ТСУ лежат 5 основных блоков: детально разберем каждый из них 🔵От проблем, которые лежат на поверхности до скрытых «подводных камней» на каждом участке, которые всплывают в самый неподходящий момент 🤓 Смотреть запись

👍3🔥3

20 Aug 2026, 10:55 UTC≈1,270 views3 reactionsread 29 August 2026

5 минут до вебинара, на котором мы с вами разберем топ ошибок в учете и научимся больше никогда их не делать 👌 Подключайтесь.

🔥21

20 Aug 2026, 07:51 UTC≈1,380 views12 reactionsread 29 August 2026
Photo

Бывали у вас в учете такие вот ошибки? 👆 Очень надеемся, что нет, потому что в такой ситуации вообще хз что делать. Но про всякое другое расскажем! 🧓 В 14:00 разберем топ ошибок в ТСУ с Юлией Левицкой. Присоединяйтесь.

😁93

Showing the 12 most recent of 40 posts we hold for @docsinbox. 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 — 14,142 of 1,626,935entries 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.

Mentions

Named by 21 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.

Named by

Channels on the register whose posts name this channel's handle.

Стойкий Ресторатор
@the_restorator · 20,120
15 posts
РЕСТОРАТОР👨‍🍳
@restorator_channel · 14,558
10 posts
🔥Эндорфин для ресторатора
@endorestorator · 8,088
6 posts
Летучий Копцев
@fly_koptsev · 8,048
4 posts
🥗 Юрист в ресторане
@juristvrestorane · 10,687
4 posts
Ресторанам надо
@restoranamnado · 8,317
4 posts
Бизнес-кухня 2.0 с Еленой Власовой
@velenaQSR · 3,388
4 posts
Артем Чубуков про Яндекс еду
@agregator_rost · 2,099
3 posts
PRO Общепит с Калентьевой
@kalentevapro · 4,431
3 posts
OFD24 | ККТ, Маркировка, ЕГАИС, Меркурий, Честный ЗНАК, ДМДК, СБП, ЦТО, ОФД, 1С
@ofd24 · 20,831
3 posts
Алкогольное Право
@alco_law · 3,444
2 posts
Фудтех в России
@foodtech_russia · 4,770
2 posts
Ресторан в кармане
@restoranvkarmane · 4,599
2 posts
BarSolution | Барные решения
@barsolutionnews · 8,556
1 post
Наталья Горячая. #МСПживи
@doingbusinesstogether · 13,018
1 post
HoReCa-юрист Юлия Вербицкая | Право для рестораторов
@horeca_lawyer · 3,509
1 post
Маркировка Про
@markirovka_pro · 3,083
1 post
METRO СТУДИЯ НН
@metro_nino_horeca · 1,240
1 post
Бухгалтер, милый мой бухгалтер
@mybuhgalter · 4,418
1 post
Санитария головного мозга | Про СанПин, ХАССП и Роспотребнадзор
@sanitaria_mozga · 2,536
1 post
ikpi Ресторатор: экономика и управление
@stuffy_girl · 2,604
1 post

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

“Документооборот для ресторана DocsInBox” (@docsinbox), 10,318 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/docsinbox.

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.