✅ Position: AFTERHOURS 📍Location: Samarkand Smart City ❗️Requirements: ✅ Experience: at least 6 months experienced ✅ Must have fluent English ✅ Must work with Street loads DAT ✅ Knowledge of USPS is a plus ✅ Shift: afterhours ✅ Salary will be discussed in Interview ❗️ NO REMOTE ❗️ Must be responsible Contact: @Steve_Walterr

Channel
Samarkandlik Logistlar 👩🏻💻👨🏻💻
@samarkandlik_logistlar
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
2,236subscribers
+19 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001999903811 |
|---|---|
| Type | Channel |
| Username | @samarkandlik_logistlar |
| Created | Between 1 November 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/samarkandlik_logistlar |
Topic
Job listings — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 18 Sept 2026, 00:20 | 2,236 | -4 |
| 13 Sept 2026, 13:59 | 2,240 | +2 |
| 10 Sept 2026, 03:17 | 2,238 | +7 |
| 4 Sept 2026, 19:18 | 2,231 | +5 |
| 31 Aug 2026, 21:33 | 2,226 | +2 |
| 29 Aug 2026, 02:13 | 2,224 | +6 |
| 26 Aug 2026, 11:54 | 2,218 | +1 |
| 23 Aug 2026, 14:16 | 2,217 | no change |
| 22 Aug 2026, 04:15 | 2,217 | first reading |
Engagement
20 posts held, back to 25 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 20 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
🚨 HIRING: DISPATCH / UPDATE / FLEET/SAFETY We are urgently looking for motivated candidates to join our team in Samarkand. Both men and women are welcome to apply! Requirements: 1+ year of relevant experience Experience with DAT / Van / Power Only IELTS 6.0+ Strong English communication skills Excellent negotiation skills Responsible, motivated, and willing to grow We Offer: 💰 Competitive salary — discussed during th…
Experienced Amazon Dispatchers Wanted 🏢 Company:Future Logistics 👨💼 Position: Amazon Dispatcher / Updater 🕐 Flexible shifts 📌 Experience required: 1–2 years ⚠️ Important:Please do not contact us if you have no previous Amazon dispatching experience. ✅ Requirements: Office-based work only No remote option Good communication skills with drivers and brokers 1–2 years of relevant experience 📍 Location: Samarkand 💸 Salar…
🚛 HIRING EXPERIENCED DRY VAN DISPATCHER 📍 Location: Samarqand 🕒 Schedule: Full Time (Office) 👤 Age Requirement: 20+ years old Requirements: ✅ Minimum 1.5 year of Dry Van dispatch experience ✅ Experience is required ✅ Good knowledge of DAT, Truckstop, and broker relations ✅ Strong negotiation and communication skills ✅ Ability to manage drivers and loads efficiently ✅ English proficiency is a plus We Offer: 💰 Compe…
Company name: A TO Z UNIVERSAL INC Position: Dispatcher , 2 vacancies available Region and Location: Samarqand( Frunze) Salary: Up to 2% Based on experience. NO REMOTE, ONLY OFFICE if dispatcher brings his owner operators we pay %2.5 At least 1- 2 years experience required. Dont text without experience! Need to work with Dry van reefers flatbeds hazmat loads Contact : @kebato662 or @shaxramshuxratov
Reefer dispatch Experience: More than 1 year Any gender Any age No remote Salary: KPI Apply with CV Location:Samarqand City Contac @Arnold_Dylan
🚛 HIRING EXPERIENCED DRY VAN DISPATCHER 📍 Location: Samarqand ⏰ Schedule: Full Time (Office) Requirements: ✅ Minimum 1 year of Dry Van dispatch experience ✅ Experience is required ✅ Good knowledge of DAT, Truckstop and broker relations ✅ Strong negotiation and communication skills ✅ Ability to manage drivers and loads efficiently ✅ English proficiency is a plus We Offer: 💰 Competitive salary + bonuses 📈 Career gro…
Experienced Amazon Dispatchers Needed 🏢 Company name: AD FREIGHT INC 👨💼Position: Amazon Dispatchers and Updaters flexible shifts Required experience: 1 - 2 years ✅Requirements: - Must work at the office - No remote option - Good communication skills with drivers and brokers 📍Samarkand 💸Expected Salary: Based on percentage and it will be discussed during the interview ✅Contacts: @hrdep777
Company name: Logistics company Position: updater, 2 vacancies available Region and Location: Samarqand( close to Bellis restaurant) Salary: after interview, fixed. NO REMOTE, ONLY OFFICE At least 1 years experience required. Dont text without experience! Contact :@alexx1116
🚛 WE ARE HIRING – EXPERIENCED AMAZON & OTR DISPATCHER 🚛 We are looking for a professional dispatcher with 2+ years of experience in both Amazon Relay and OTR (street loads). Requirements: ✅ Minimum 2 years of dispatch experience ✅ Strong knowledge of Amazon Relay ✅ Experience with Chime and Post A Truck ✅ Good network of OTR brokers and ability to find profitable street loads ✅ Capable of handling at least 6 truck…
📢 В нашу команду требуются сотрудники на позицию Safety Assistant! Требования: • Опыт работы не обязателен • Знание русского,английского и узбекского (на разговорном уровне). Знание русского обязателен. • Ответственность, внимательность и готовность обучаться и расти. • Рассматриваем только на долгий срок работы. Условия: • Работа из офиса. • Обед на работе Включен. • Ночная смена: с 18:00 до 03:00. • Обучение и по…
Company name: Brothers dispatch team Position: Amazon dispatcher Region and Location: Samarqand Salary: after interview NO REMOTE, ONLY OFFICE At least 2 years experience required. Dont text without experience! Contact : @strong_dispatch
Showing the 12 most recent of 20 posts we hold for @samarkandlik_logistlar. 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 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@dispatchhunter · 27,934
Telegram ranks this channel #13 of 45 here — alongside 44 others — read 10 September 2026
@newvacancylogistics · 26,931
Telegram ranks this channel #14 of 44 here — alongside 43 others — read 12 September 2026
@truckchi_togalar · 43,079
Telegram ranks this channel #23 of 33 here — alongside 32 others — read 29 August 2026
@huntmejob · 35,939
Telegram ranks this channel #24 of 42 here — alongside 41 others — read 2 September 2026
@rabota_samarkand_samarqand_ish · 61,202
Telegram ranks this channel #35 of 59 here — alongside 58 others — read 22 August 2026
@clozjobs · 137,204
Telegram ranks this channel #42 of 49 here — alongside 48 others — read 2 September 2026
This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Samarkandlik Logistlar 👩🏻💻👨🏻💻” (@samarkandlik_logistlar), 2,236 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/samarkandlik_logistlar.
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.