Telegram RegisterThe public register of Telegram
Telegram profile photo for Заказы для FF и Карго

Channel

Заказы для FF и Карго

@zakazyff

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

15,363subscribers

+14 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002127751455
TypeChannel
Username@zakazyff
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/zakazyff

Growth

15,29915,39815,348.57 August 2026 — 15,349 subscribers7 August 2026 — 15,349 subscribers8 August 2026 — 15,341 subscribers9 August 2026 — 15,337 subscribers10 August 2026 — 15,336 subscribers11 August 2026 — 15,341 subscribers13 August 2026 — 15,331 subscribers14 August 2026 — 15,329 subscribers16 August 2026 — 15,306 subscribers17 August 2026 — 15,304 subscribers18 August 2026 — 15,312 subscribers19 August 2026 — 15,307 subscribers20 August 2026 — 15,308 subscribers22 August 2026 — 15,299 subscribers24 August 2026 — 15,302 subscribers25 August 2026 — 15,381 subscribers26 August 2026 — 15,383 subscribers27 August 2026 — 15,386 subscribers28 August 2026 — 15,384 subscribers29 August 2026 — 15,380 subscribers30 August 2026 — 15,365 subscribers31 August 2026 — 15,371 subscribers1 September 2026 — 15,392 subscribers2 September 2026 — 15,397 subscribers3 September 2026 — 15,398 subscribers5 September 2026 — 15,390 subscribers8 September 2026 — 15,363 subscribers15,3637 August 20268 September 2026
27 measurements spanning 33 days, net +14. 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 15,284–15,413 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
8 Sept 2026, 22:1415,363-27
5 Sept 2026, 15:4115,390-8
3 Sept 2026, 17:1715,398+1
2 Sept 2026, 08:4215,397+5
1 Sept 2026, 06:2815,392+21
31 Aug 2026, 03:4315,371+6
30 Aug 2026, 06:5915,365-15
29 Aug 2026, 05:1815,380-4
28 Aug 2026, 04:0515,384-2
27 Aug 2026, 03:4515,386+3
26 Aug 2026, 05:2715,383+2
25 Aug 2026, 04:3515,381+79
24 Aug 2026, 04:0415,302+3
22 Aug 2026, 09:5515,299-9
20 Aug 2026, 22:3215,308+1
19 Aug 2026, 19:2815,307-5
18 Aug 2026, 20:4315,312+8
17 Aug 2026, 19:1315,304-2
16 Aug 2026, 17:3715,306-23
14 Aug 2026, 23:5315,329first reading

Engagement

615 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 53 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.781%
avg views ÷ 15,363 subscribers
Avg views / post
120
497 posts measured
Reaction rate
0.418%
reactions ÷ views · ER floor
Posts in window
497
of 615 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 32 of 497 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 3 September 2026
Posts held615 (6 August 20263 September 2026)
Views total59,610
Reactions total24
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10:50 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

Video runtime
26s
Average length
13s

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

27 reactions across 25 posts, in 3 distinct kinds. The most used accounts for 92.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2592.6%
👍13.70%
💯13.70%

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

Measured over the 615 most recent posts we hold, published 6 August 2026 to 3 September 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

3 Sept 2026, 09:40 UTC99 viewsread 3 September 2026

✅ Найти блогера, рилсмейкера или креатора теперь еще проще 👉 Тиндер для поиска блогеров и рилсмейкеров Размещай заказы, бери заказы.

3 Sept 2026, 09:00 UTC137 viewsread 3 September 2026
Photo

🚛 Новый фулфилмент в канале Название: МРЛ-ФБС Адрес: г.Санкт-Петербург ул.Салова 32 Контакты для связи: @DVLADV Отдаёте нам рутину — вы занимаетесь продажами: ✅ сборка со сканером и двойной сверкой — пересорт исключён, от 25 ₽ ✅ маркировка Честный знак — 7 ₽/этикетка ✅ отгрузка в ПВЗ и на СЦ WB/Ozon — 15 ₽ ✅ возвраты с фотоотчётом — от 50 ₽ Скидка 10% на первую отгрузку по промокоду @zakazyff ___ Заказы для FF

3 Sept 2026, 08:40 UTC105 viewsread 3 September 2026

🟢 Новый Заказ на упаковку и отгрузку: 1. Место нахождения товара: Ростов-на-Дону 2. Склад отгрузки: Казань 3. Категория товара: Другой товар 4. Размеры товара: 11x11x6 см 5. Количество товаров: 350 шт 6. Вложения: уточним при обсуждении 7. Ожидаемый вид упаковки: уточним при обсуждении 8. Дополнительные условия упаковки: уточним при обсуждении ___ Заказы для FF и Карго — @zakazyff 🔒 Получить контакты заказч

3 Sept 2026, 08:40 UTC93 viewsread 3 September 2026

🟢 Новый Заказ на упаковку и отгрузку: 1. Место нахождения товара: Москва 2. Склад отгрузки: ФБС регионы 3. Категория товара: Одежда 4. Размеры товара: 370х250х50 мм 5. Количество товаров: 1000 6. Вложения: нет 7. Ожидаемый вид упаковки: Зип-пакет, навесная бирка, маркировка 8. Дополнительные условия упаковки: уточним при обсуждении ___ Заказы для FF и Карго — @zakazyff 🔒 Получить контакты заказчика и больше

3 Sept 2026, 08:40 UTC129 viewsread 3 September 2026

🟢 Новый Заказ на упаковку и отгрузку: 1. Место нахождения товара: Москва 2. Склад отгрузки: ФФ в Новосибирске 3. Категория товара: Мужское бельё (трусы) 4. Размеры товара: Короб: 60×60×40 см; объём одной упаковки: 1,74 л 5. Количество товаров: до 5 коробов 6. Вложения: нет 7. Ожидаемый вид упаковки: не надо 8. Дополнительные условия упаковки: нет 9. Готовность товара: Товар полностью готов к отгрузке 10. Сх

3 Sept 2026, 07:20 UTC161 views1 reactionsread 3 September 2026

🟢 Новый Заказ на упаковку и отгрузку: 1. Место нахождения товара: Москва 2. Склад отгрузки: Фбс любой склад 3. Категория товара: Кардиганы / джинсы 4. Размеры товара: 30х 40 макс 5. Количество товаров: 5000 6. Вложения: Нет 7. Ожидаемый вид упаковки: Зип ваш 8. Дополнительные условия упаковки: Тз фбс под ключ Товар готов ___ Заказы для FF и Карго — @zakazyff 🔒 Получить контакты заказчика и больше заказов

1

3 Sept 2026, 06:40 UTC148 viewsread 3 September 2026

🟢 Новый Заказ на упаковку и отгрузку: 1. Место нахождения товара: Москва ЮВ 2. Склад отгрузки: Москва фбс 3. Категория товара: Товарка разная 4. Размеры товара: 20х30х5-10 5. Количество товаров: 8000 6. Вложения: Нет 7. Ожидаемый вид упаковки: Не нужно 8. Дополнительные условия упаковки: Нужен фбс под ключ полностью ___ Заказы для FF и Карго — @zakazyff 🔒 Получить контакты заказчика и больше заказов + При

3 Sept 2026, 05:45 UTC146 views1 reactionsread 3 September 2026

🚚 Новая заявка на карго / логистику: 1. Откуда забрать груз: не надо 2. Куда доставить: склад ответственного хранения в радиусе 40 км от Минска 3. Что за груз: пищевое сырьё 4. Объём / вес / количество мест: 2 европаллеты 5. Когда нужно забрать: до конца сентября 2026 г. 6. Температурный режим: +2…+8 °C (холодильная зона) ___ Заказы для FF и Карго — @zakazyff 🔒 Получить контакты заказчика и больше заказов + П

1

3 Sept 2026, 05:40 UTC113 viewsread 3 September 2026

🟢 Новый Заказ на упаковку и отгрузку: 1. Место нахождения товара: Обухово 2. Склад отгрузки: Обухово, Софьино 3. Категория товара: Мука, крупы 4. Размеры товара: 200х100х200 5. Количество товаров: От 100 комплектов в день 6. Вложения: Только товар 7. Ожидаемый вид упаковки: Пвд рукав под запайку, картонная коробка поставляется с товаром. 8. Дополнительные условия упаковки: Указание срока годности ___ Заказ

3 Sept 2026, 05:20 UTC98 viewsread 3 September 2026

🟢 Новый Заказ на упаковку и отгрузку: 1. Место нахождения товара: Нужен ФФ в Краснодарском крае, Новосибирске, в Казани 2. Склад отгрузки: ближайший ПВЗ по модели ФБС 3. Категория товара: косметика 4. Размеры товара: 10х10х8 и 4х4х12 5. Количество товаров: 1000 6. Вложения: нет 7. Ожидаемый вид упаковки: нет (уже упакованы) 8. Дополнительные условия упаковки: наклейка всех куар-кодов и шк для отгрузке + отгру

3 Sept 2026, 05:16 UTC78 viewsread 3 September 2026

🚚 Новая заявка на карго / логистику: 1. Откуда забрать груз: г. Орёл 2. Куда доставить: СЦ Краснодар 3. Что за груз: Одежда (анорак, бомбер, платье) 4. Объём / вес / количество мест: 300 шт (анорак 40x30x5 680г, бомбер 35x43x6 640г, платье 30x20x2 200г) 5. Когда нужно забрать: уточним при обсуждении ___ Заказы для FF и Карго — @zakazyff 🔒 Получить контакты заказчика и больше заказов + Приоритетное получение за

3 Sept 2026, 05:16 UTC56 viewsread 3 September 2026

🟢 Новый Заказ на упаковку и отгрузку: 1. Место нахождения товара: г. Подольск 2. Склад отгрузки: Wildberries (FBS, Москва) 3. Категория товара: Одежда (взрослая и детская) 4. Размеры товара: Размеры одежды: S/M/L (взрослая), 74–110 (детская); Габариты коробок: 41×20×3 см, 20×15×5 см, 30×20×5 см 5. Количество товаров: 150 шт/день 6. Вложения: Бирки и листовка 7. Ожидаемый вид упаковки: Вакуум, коробка, наклейка

Showing the 12 most recent of 615 posts we hold for @zakazyff. 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 8 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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“Заказы для FF и Карго” (@zakazyff), 15,363 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/zakazyff.

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.