Data collection since 1st Jan 2026. Exclude shipping contracts which origin and destination are both in Hortus (VH-331) system. Release previous month’s report within first 7 days of a month.
Feel free to ask and discuss under this post, I would link my reports in original post so they won’t get lost 
| Abbreviation / Term | Description |
|---|---|
| MPC | Multiple Packages CONT A shipping CONT which have multiple packages. Shipping CONTs sent via CONTD can have multiple packages. |
| WPC | Whole Package CONT If a MPC’s all packages are shipped together during the entire time of being handled by shipper, it is considered to be a “Whole Package CONT”, as if it’s one SHPT consists of different MATs. A normal shipping CONT with just one SHPT package is also considered as a WPC. |
| EWPC | Equivalent Whole Package CONT Sometimes, due to capacity restriction, individual packages from a MPC cannot be shipped together. Instead, these packages are split and loaded on different ships. In such situation, only some packages are shipped together during the entire time of being handled by shipper. Those packages forms an “Equivalent Whole Package CONT”. A WPC is considered as an EWPC. A nomal shipping CONT with just one SHPT is also considered as an EWPC. For example, a customer sent a MPC with 4 packages: #3, #7, #11, #15 (as stated in CONT). Due to capacity restriction, those packages are shipped as so:* #3 & #11 on ship A * #7 on ship B * #15 on ship C This makes this single MPC same as one MPC of #3 & #11 plus two CONTs for #7 and #15 separately, adds up to three EWPCs. |
| TT | Transit Time Length of time elapsed from customer completes “provision of SHPT at origin” to shipper completes “deliver SHPT to destination”. Time between “provision” and “pick up” is included since MATs being shipped are no longer accessible to customer and exists in inventory as BLCK item when “provision” step is completed. |
| Delivery Distance | Minimum distance required to travel to deliver the SHPT The minimum distance from origin to destination in parsecs. * For locations in different systems, this distance is same as the shortest distance in parsec given by SFC & BTF. If there is a complete gateway link (such that a STL only ship can travel from origin to destination), length of gateway route is considered as well. If there is an incomplete gateway link, length of gateway route is NOT considered UNLESS such route is commonly recognised as a faster route with a similar cost (of fuel, damage and fee altogether).* For locations in the same system, this distance is 1. Example: Delivery distance for ANT-MOR as of 5th Feb 2026 is 81 pc, as the gateway route is both incomplete and generally slower, despite the gateway route is only 74 pc. |
| TTPD | Transit Time Per Delivery Distance Transit time spent per parsec of minimum distance required to travel to deliver the SHPT. For example: a SHPT’s transit time is 36h, delivery distance is 20pc, TTPD for this SHPT is 36/20=1.8=1h48m |
| P-k | k-th Percentile A value that has a k percentage of scores below it. In this report it’s using nearest-rank method. P80 means a value that has a 80% of scores below it. |
| Under Expected Time | SHPT is delivered within expected time Formula to calculate Expected time (in hours) is given as: t = d/1.5+12where d is Delivery Distance.For locations in the same system, this value is always 12h. This metric is independent from On Time. |
| On Time | SHPT is delivered without exceeding due time specified by “delivery SHPT” term in CONT No overdue DOES NOT mean SHPT is on time, since the due timer only starts after “pickup SHPT” term is completed by shipper. This metric is independent from Under Expected Time. |
