Identity
Current assay, origin, declared route and commercial authority.
ESPO crude reviewed through stream identity, Pacific logistics, assay and compliance.
ESPO is associated with the Eastern Siberia-Pacific Ocean system and Russian Far East export context. The useful buyer reading combines stream identity, assay, terminal documentation and Asian refinery relevance.
API, sulphur and yield figures should be treated as assay and contract data, not universal values for every cargo. Each offer needs sample basis, date, route and acceptance limits.
Availability, routing, loading programme and compliance must be verified through current counterparty documentation. ESPO review must include loading documents, inspection and compliance before any commercial step.
Identify stream, counterparty and documentary basis of the offer.
Review declared ESPO system, terminal or routing reference.
Confirm API, sulphur, density, yield and contaminants on a current sample.
Validate window, quantity, inspector, custody and loading documents.
Align refinery, compliance, delivery and contractual restrictions.
ESPO is often analysed through its Pacific refinery profile, but the buyer still needs the actual quality file: density/API, sulphur, distillation curve, salt, water, sediment and metals.
Logistics matter as much as quality. An ESPO cargo should support route, loading point, inspection and documentary compatibility with contract and destination.
Any transaction requires compliance and counterparty review, especially where origin, route or documents may be affected by regulatory restrictions.
Kozmino and Pacific-chain context help explain ESPO, but they do not replace cargo documents. The offer should connect origin, route, terminal, quantity and inspection.
The buyer should request current assay, quantity certificate, SDS, loading terms, inspector nomination and evidence of commercial authority.
KaizenGTC can organise document and counterparty diligence; it does not state proprietary terminal access, inventory or export programme.
| Element | Verification |
|---|---|
| Stream identity | Confirm that the offer is ESPO, not another Russian crude or undeclared blend. |
| Assay | API, sulphur, density, yield and sample date. |
| Route / terminal | Verify loading documentation, window, port and custody. |
| Compliance | Review counterparty, origin, sanctions, insurance and applicable restrictions. |
| Refinery destination | Match yield and contaminants with buyer slate. |
ESPO should be read as Pacific-context crude. Commercial relevance comes from logistics, differentials, compliance and refinery fit, not a generic consumption table.
| Market | Role | Context |
|---|---|---|
| Russian Far East | ORIGIN / EXPORT | ESPO system and Pacific-loading context subject to current documents. |
| Asia-Pacific refineries | PROCESSING DEMAND | Buyers evaluating yield, quality and logistics distance. |
| Regional physical market | DIFFERENTIALS / COMPLIANCE | Execution depends on contract, regulation, insurance, inspection and documented availability. |
Sources: U.S. EIA Russia country analysis; S&P Global - Russia crude oil pipeline capabilities to mainland China; OSW - Completion of ESPO pipeline to the Pacific Ocean; ExxonMobil crude oil assays; Intertek crude oil assay testing
Current assay, origin, declared route and commercial authority.
KYC, sanctions review, insurance, delivery terms and counterparty file.
Terminal, quantity, inspector, SDS, COA and custody chain.
It refers to a commercial crude associated with the Eastern Siberia-Pacific Ocean system and Pacific export logistics; each cargo still has to prove identity, route and assay.
It helps explain ESPO Pacific-loading context, although commercial acceptance depends on specific terminal, quantity and inspection documents.
API, sulphur, density, distillation curve, salt, water/sediment, metals and any destination contractual limits.
No. Availability, routing, loading programme and compliance must be verified through current counterparty documentation.