Uzbekistan Post Tracking. Free & Online.

TrackParcel looks up a track code with the same tracking service that the tracking page on UzPost's website, uz.post, uses. Its answer arrives either as an international mail item from the IPS system, carrying origin and destination countries, or as a shipment record naming the sender's and recipient's countries.

Only the tracker's reply for an unknown code has been captured for real; no genuine UzPost parcel has been followed through it yet. The fields described below are therefore the ones uz.post's tracking page itself reads, and no delivered history is described.

The uz.post FAQ, as TrackParcel's integration notes record it, describes a single track code layout, a pair of letters either side of nine digits, and documents no alternative. TrackParcel's own check follows that layout but lets any ending through, not just UZ, and skips the check digit.

Pasted text is tidied in the search box first: an English label such as Track code, brackets, spaces, hyphens and dots go, and letters become capitals. A cleaned code of 13 letters and digits outside that layout is reported as not found, and uz.post is not asked. For an inbound code with another ending, such as RU, Uzbekistan Post is missing from the suggestions, so choose it from the list yourself.

For an international item, TrackParcel lists each IPS scan with the office that made it, the event name and the stamp, and names the origin and destination countries the answer gives. Any retention reason or non-delivery reason recorded on a scan is added beside it as a remark.

A shipment record works differently. When it holds UzPost's own scans, those are shown alone, as on uz.post; otherwise TrackParcel merges the partner legs by the moment each happened, keeping each stamp's offset, and names the partner courier beside its checkpoints. Addresses, postcodes and any signatory, driver or contact details are never read.

An unknown code draws an answer with all sections blank; TrackParcel treats that, and the page's own not-found code, as not found. A code of 13 letters and digits outside the two-nine-two layout is also reported as not found, without a lookup.

A maintenance page or other non-data reply counts as the tracker being down, and an unexpected answer as an error. A bare page-not-found reply without the empty answer never counts as a missing item, since every code would get one if the tracker moved.

Uzbekistan Post's site at uz.post is built in the browser, and its plain pages carry no contact details TrackParcel could cite, so no channel is named here. Questions about a delay, a retention reason or a non-delivery reason on a scan need UzPost itself, since TrackParcel only passes on the tracker's wording. Keep the 13-character track code and the scan's remark to hand when you ask.