Channel
@perfilevblog
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,218subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001682192073 |
|---|---|
| Type | Channel |
| Username | @perfilevblog |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/perfilevblog |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 07:36 | 2,218 | -5 |
| 7 Aug 2026, 07:00 | 2,223 | no change |
| 7 Aug 2026, 06:58 | 2,223 | first reading |
12 posts held, back to 23 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 2 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 12 (23 July 2026 – 6 August 2026) |
| Views total | 10,197 |
| Reactions total | 167 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:49 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.
167 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 43.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 73 | 43.7% | |
| 🔥 | 46 | 27.5% | |
| 💯 | 25 | 15.0% | |
| ❤ | 10 | 5.99% | |
| 👏 | 10 | 5.99% | |
| 😢 | 2 | 1.20% | |
| 😁 | 1 | 0.599% |
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 12 of the 12 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 167reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 23 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.
Отладили процессы на складе, докрутили софт, время сборки заказа сильно сократилось — 6 часов в среднем по суткам на все заказы. Следующий шаг: отгрузка 2 раза в день. Запустим где-то на стабильных 1500 заказов в день (уже скоро, получается). Последние 2 дня на нашем СЦ сортировка была 20 и 25 минут: это время, как мы сдали заказ на ворота и таймер у вас в ЛК остановился. Я такого ещё не видел. Бывало, и пара суток…
🔥11
Кто спрашивал про оборудование у нас на складе: ТСД используем Urovo DT40 и DT50 — вот купил сейчас еще один в FBS-зону. Сканеры абсолютно все Zebra DS2208 и DS2278 — проводные и беспроводные. Это лучшие сканеры, какими приходилось пользоваться. Дорогие, но стоят своих денег. А вчера ездил сдавать поставку — хотел по электронике выяснить и нашу штуку для водителя показать. Поставку отсортировали за час после сдачи,…
🔥9👍5
Согласно опросу среди фулфилментов, которые возят ФБС, довольно часто на воротах, если сдаешь больше одной поставки, приемщики могут случайно не отсканировать QR какой-нить поставки. Если что, потом концов не найдёшь и таймер не останавливается (хотя, поговаривают, таймер всё равно в момент сортировки тормозится). Вчера так у нас поставку не пропикали — хорошо, что уже через 5 часов отсортировали и товар все-таки п…
🔥9
FBS работает. Надо только нормально отвозить в нормальные СЦ. Сутки от заказа до ПВЗ.
👍7❤1
Сейчас все кинулись открывать FBS склады по России, чтобы отгружать из Москвы, так как штрафы отменили. Просто подумайте о том, что клиенты из Новосибирска видят доставку 3 дня, а товар едет неделю. Будет много отказов. Это настолько очевидный трюк, что я бы не вписывался в схемку.
💯17
FBS. Ну что, неплохо начали. Загрузка склада, благодаря автоматизации, пока минимальная. Специально не стал агрессивно привлекать клиентов — в течение недели постепенно подключаем своих. Главная цель — обеспечить высокий уровень сервиса и быстрые отгрузки. Сейчас отлаживаем процессы на большом потоке и количестве артикулов — быстро и дёшево набили много шишек. Перестраиваем половину склада. Сейчас зоне FBS 277 ко…
👍17❤5👏1
Регистрация знаков заняла 7 месяцев
👍13👏6😁1
Вчера сдал обе поставки по FBS в ПВЗ и через час в СЦ. Обратите внимание, что таймер на СЦ не останавливается до момента сортировки, но на скидку влияет момент скана QR на воротах. Товар из ПВЗ уже на пути к клиенту. Товар на СЦ ещё даже не отсортирован и лежит там же. Мы возим ежедневно что можем на ПВЗ, а если у вас 50+ заказов, то на СЦ: стоимость приёмки до 50 заказов на сегодняшний день одинаковая в большиств…
👍6🔥1
Начали отгружать FBS: сегодня допилил софт — теперь всё собирается автоматом без участия вашего менеджера, КИЗы передаются на WB. Можно, конечно, не передавать КИЗы, но тогда отказы поедут прямиком в ваш ПВЗ. Обратите внимание, что многие ФФ сейчас кидаются на FBS без автоматизации, предлагая низкие цены, а потом с ними можно прикурить. Съездил сдал две поставки для теста: в ПВЗ и СЦ. В ПВЗ всё залетело за минуту.…
👍10❤4👏3
Я всю жизнь следил за языком: что в оффлайне, что в онлайне. Причём в онлайне часто набирал комментарий или пост. Думал и стирал, не отправляя. Времена тяжёлые, ребят. Думайте головой, чтобы потом не жалеть. Всем сил 🙏
👍14💯7😢2
Сделал полный разбор перехода на FBS: как поднять FBS-склад в кабинете, куда сдавать заказы, какие этикетки не перепутать, сколько времени на отгрузку без штрафа и как считать логистику. Если вы сейчас в смятении, прочитайте статью, разложил всё по полочкам. Все тарифы актуальны на сегодняшний день. 👉 nitropack.ru/blog/fbs
🔥11
Как посмотреть сумму компенсации по сгоревшему товару в Электростали. Кто хочет снизить риски — мы возим FBS и ежедневно подсорт в Коледино по FBO от одной коробки. Пишите Анастасии: 👉 @mpr_sales
🔥5👍1💯1
Showing the 12 most recent of 12 posts we hold for @perfilevblog. 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 — 146,633 of 1,481,217entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Перфильев отгружает” (@perfilevblog), 2,218 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/perfilevblog.
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.