Telegram RegisterThe public register of Telegram
Telegram profile photo for Новости FM Logistic Новосибирск и Владивосток 🌳🚍🌏

Channel

Новости FM Logistic Новосибирск и Владивосток 🌳🚍🌏

@novfmlogistic

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

130subscribers

-1 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-1002221463964
TypeChannel
Username@novfmlogistic
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live3 November 2026
Measurements held5
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/novfmlogistic

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 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 the other topics.

Growth

1291311307 August 2026 — 131 subscribers9 August 2026 — 131 subscribers23 August 2026 — 130 subscribers12 October 2026 — 129 subscribers3 November 2026 — 130 subscribers7 August 20263 November 2026
5 measurements spanning 87 days, net -1. 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 129–131 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 00:20130+1
12 Oct 2026, 21:40129-1
23 Aug 2026, 13:17130-1
9 Aug 2026, 01:01131no change
7 Aug 2026, 14:58131first reading

Engagement

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

What this channel posts

Video runtime
17s
Average length
17s

Measured directly from 1 video 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

42 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1535.7%
🔥1023.8%
❤716.7%
🎉716.7%
👏37.14%

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

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

19 Jul 2026, 09:52 UTC81 views12 reactionsread 9 August 2026
Photo

🚴‍♂FM NOV Постоянное развитие - двигатель прогресса Главная цель логистики — обеспечить доставку нужного товара в нужном количестве и качестве, точно в срок и с минимальными издержками. Мы совершенствуем нашу внутреннюю логистику, чтобы ресурсы могли беспрепятственно попадать из одной складской ячейки в другую - так на этой неделе под руководством Технической Службы был произведен запуск новых внутрискладских ворот…

🎉7❤2🔥2👏1

7 Jul 2026, 01:52 UTC119 views2 reactionsread 9 August 2026
Forwarded from @fmlogistic_rusPhoto

📞С Днём социальных сетей! Ловим цифровой вайб и запускаем кое-что очень интересное в честь нашей темы года «В ритме поколений». 📱 Кто вы в современном диджитал-мире — стремительный Зумер, технологичный Миллениал, осознанный Икс или мудрый Бумер? Пришло время узнать свой настоящий цифровой возраст! 🎁 Запускаем праздничный розыгрыш: Среди всех, кто пройдет тест, мы случайным образом выберем 3 победителей и подарим к…

❤2

1 Jul 2026, 02:07 UTC147 views5 reactionsread 9 August 2026
Photo

NOV Двойной стартап💫 Сразу 2 Клиента в июне начали свою деятельность на Площадке в ФМ Новосибирске! Замечательно, что во внутренней структуре Компании есть возможности для развития своих компетенций и знаний! Ирина Стаценко освоила все азы складской системы учёта и и настроила все процессы под требования Клиента. Команда FM во главе c координатором по складским операциям Ларисой Мясненко, Андрея Чернавина и Елены…

👍5

24 Jun 2026, 07:04 UTC134 views6 reactionsread 9 August 2026
Photo

NOV FM - Экология🌿 Акция - это как правило разовое мероприятие, а мы за то, чтобы поддерживать экологические привычки на постоянной основе. Уже двенадцатый* год подряд мы высаживаем цветы у входных групп, а их у нас - три. В этом году главный садовод - Лариса Мясненко заботливо рассадила петунии, добавив ещё подвесных кашпо. Такие цветники придают летнего настроения в сонме деловых забот! * Скорректировали срок с …

🔥6

20 Jun 2026, 00:26 UTC169 views5 reactionsread 9 August 2026
Photo

NOV Внутренний аудит🏹 На складе прошел ежегодный аудит по пищевой безопасности, проверка системы управления персоналом и аудит процессов на Ключевом Клиенте. Аудиторы - менеджеры по качеству Головного офиса Виктория Кузина и платформы Чехов Александр Анохин. Любой аудит позволяет оценить эффективность процессов, выявить слабые стороны, риски, угрозы и предложить пути оптимизации и улучшений. По результату проверк…

👍3🔥2

17 Jun 2026, 07:09 UTC153 viewsread 9 August 2026
Photo

Сроки проведения конкурса продлены до 30 июня. Успейте прислать рисунки! #FM_Конкурс

17 Jun 2026, 05:21 UTC114 views5 reactionsread 9 August 2026
Photo

Победителем в голосовом опросе стал Трушин Лев 3 года. Поздравляем победителя. Желаем творческих успехов и будущих побед. Фото наших участников👆. #FM_Конкурс

❤3👏2

5 Jun 2026, 08:44 UTC167 views7 reactionsread 9 August 2026
Photo

NOV FM Юбиляры🎊 В этом году 11 сотрудников FM Logistic празднуют год работы в компании, но есть и такие, кто проработал даже больше: Андрей Сидуков и Наталья Швицова отработали по три года, Яков Великий и Руслан Изюмский по 5 лет, Ирина Стасенко - 10 лет, а Сергей Истомин - 15 лет!😄 Хочется отметить, что наши юбиляры не сидят на месте, а постоянно находятся в развитии - осваивают новые позиции и не боятся открыват…

👍7

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

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

“Новости FM Logistic Новосибирск и Владивосток 🌳🚍🌏” (@novfmlogistic), 130 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/novfmlogistic.

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.