Almost a year ago, at the end of one of my shifts, I had an idea: what if we started live streams with people from logistics — dispatchers, updaters, drivers, managers, and others working in the industry? I never really took the idea seriously, but I’m thinking about it again. The idea is to have 2 live streams a month, or maybe even one every week, where we talk about logistics, work, real experiences, problems, u…

Channel
Dispatching Insights
@dispatching_insights
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Polls · Citations · Cite this entry
799subscribers
+12 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 | -1002659835796 |
|---|---|
| Type | Channel |
| Username | @dispatching_insights |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/dispatching_insights |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 19:37 | 799 | +9 |
| 8 Sept 2026, 18:59 | 790 | +2 |
| 29 Aug 2026, 11:35 | 788 | -1 |
| 23 Aug 2026, 12:08 | 789 | +5 |
| 15 Aug 2026, 00:08 | 784 | -3 |
| 8 Aug 2026, 01:46 | 787 | no change |
| 7 Aug 2026, 17:43 | 787 | first reading |
Engagement
16 posts held, back to 30 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 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
60 reactions across 10 posts, in 9 distinct kinds. The most used accounts for 28.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5258045100025476789 | 17 | 28.3% | |
| 🔥 | 11 | 18.3% | |
| 🤣 | 11 | 18.3% | |
| 😁 | 9 | 15.0% | |
| ❤ | 4 | 6.67% | |
| 😭 | 4 | 6.67% | |
| 👍 | 2 | 3.33% | |
| 💯 | 1 | 1.67% | |
| 😱 | 1 | 1.67% |
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 is Telegram’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 13 of the 16 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 60 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 30 June 2026 to 7 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.
Telegram Stars
- Stars received
- 2
- across the posts below
- Posts paid on
- 2
- of 16 we hold a reading for · 13%
- Most on one post
- 1
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dispatching_insights. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 16 most recent posts we hold for this entry, published 30 June 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Posted without readable text
🔥1
When market is slow... JUST BOOK IT!
Posted without readable text
I just need your feedback guys. Do you find this bot useful?
- Yes79%
- No21%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Ads are removed. Now the tool is completely free for our community. @LoadInfoParserBot
#Insights 🥸 IDROCK by MSS — HOS MONITORING UPDATE Alhamdulillah, the new HOS Monitoring System in IDROCK is already showing promising results. During our internal side-by-side testing with another well-known refresher in the market, our IT team noticed differences in the displayed statistics. IDROCK reflected the more accurate HOS result in this case. The system is also designed to be cleaner and more practical f…
❤2🔥2custom 52580451000254767892
The bot has received several improvements: • Fixed an issue where dispatch information wasn't sent if a trip contained a canceled leg. • Fixed an issue that caused incorrect trip rate parsing in certain cases. • Applied several minor bug fixes and performance improvements. If you notice any bugs or unexpected behavior, please report them to @ameerkhanx. Your feedback helps us improve the bot and make the updater's …
How real dispatchers wish their coworkers a happy birthday. @dispatching_insights
😁8🤣4👍2💯1
By the way, this tool is free until July 15. Share it with accountants you know.
🔥1
I started my career in logistics 5 years ago. Last year, I almost burned out from spreadsheets. We started a small dispatch team. We had no accountant. So all the numbers became my job. Every month, same work: enter every load one by one. Calculate each dispatcher’s gross and commission. Make invoices for clients. Make weekly reports. This took 10 hours every week. And mistakes happened. Wrong numbers. Wrong commis…
❤2custom 52580451000254767892
🎉InstaSheet da yangi funksiya! Endi Amazon Relaydan yuk ma'lumotlarini ko'chirish yanada qulay. Yuk detallarini belgilab nusxa olasiz va Relay Load Parser bo'limiga ko'chirasiz. InstaSheet yuk ma'lumotlarini kerakli formatda tayyorlab beradi. Siz esa tayyor yuk detallarini shunchaki Google Sheets jadvaliga ko'chirib qo'yasiz. Bur orqali yanada ko'rpoq vaqtingiz tejaladi! @InstaSheet - Dispatch Service uchun TMS
🔥4
Showing the 12 most recent of 16 posts we hold for @dispatching_insights. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Polls
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
I just need your feedback guys. Do you find this bot useful?
- Yes79%
- No21%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Let’s see where our community is located 📍 Where do you work from? 👀
- Tashkent59%
- Andijan8%
- Ferghana4%
- Namangan0%
- Samarkand6%
- Bukhara3%
- Navoiy0%
- Kashkadarya2%
- Surkhandarya0%
- Other18%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 16 most recent posts we hold, published 30 June 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Dispatching Insights” (@dispatching_insights), 799 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/dispatching_insights.
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.