Telegram RegisterThe public register of Telegram

Channel

Delivery Cargo

@Forwardlogisticscargo

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

44subscribers

+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-1003818763759
TypeChannel
Username@Forwardlogisticscargo
Created29 April 2026measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held3
On Telegramt.me/Forwardlogisticscargo

Growth

434443.57 August 2026 — 43 subscribers8 August 2026 — 44 subscribers10 August 2026 — 44 subscribers7 August 202610 August 2026
3 measurements spanning 3 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 43–44 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 15:4544no change
8 Aug 2026, 06:0944+1
7 Aug 2026, 12:4643first reading

Engagement

4 posts held, back to 29 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 4 posts for this entry, the most recent from 10 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Videos
3

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
18s
Average length
18s

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.

Recent posts

10 Jun 2026, 06:57 UTC345 views0 reactionsread 10 August 2026
Photo

🇺🇿 Весь Узбекистан на одной карте. А для нас — это ежедневные маршруты. 📍 Ташкент 📍 Самарканд 📍 Бухара 📍 Навои 📍 Фергана 📍 Андижан 📍 Наманган 📍 Нукус 📍 Термез Где бы ни находился ваш груз — Delivery Cargo доставит его точно в срок. 🚛 Межгородние перевозки 🏢 Переезды офисов и складов 🏦 Перевозка банкоматов и оборудования DELIVERY CARGO Мы не перевозим грузы. Мы двигаем бизнес. 📞 +998 88 113 4040

12 May 2026, 07:06 UTC231 viewsread 10 August 2026
Photo

🔴🔵 МЫ ИЗМЕНИЛИСЬ. ВСТРЕЧАЙТЕ — DELIVERY CARGO Да, это мы. Но теперь — быстрее, сильнее и масштабнее. Мы провели ребрендинг и открываем новую главу 🚀 Gruzovichkof → Delivery Cargo Новое имя. Новые возможности. Тот же надёжный сервис, которому вы доверяете. 🔴 Скорость в каждом заказе 🔵 Надёжность в каждой доставке Мы обновили всё, чтобы делать логистику проще, быстрее и удобнее для вас. Добро пожаловать в новую

Showing the 4 most recent of 4 posts we hold for @Forwardlogisticscargo. 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 — 323,164 of 1,160,990entries 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 1 registered channel — 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.

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

“Delivery Cargo” (@Forwardlogisticscargo), 44 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Forwardlogisticscargo.

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.