Loading…
CO₂e reports
Platform-generated drafts and previews, aligned with the EN ISO 14083:2023 methodology that CountEmissions EU sets for transport-service emissions. Saved Transport Emissions Statement workspace drafts are listed here for internal or partner review — not official certificates, not customs filings, and not accredited verification. Representative planning examples appear when no saved drafts exist.
EU documentation workspace
Sustainability documentation here sits on the same shipment workspace as preferential origin and transport-emissions (TES) evidence — see how it maps to EU rules.
Workspace preview of a platform-generated Transport Emissions Statement draft — prepared for documentation workflows, not an official certificate or filing. When a saved draft exists it loads here; otherwise you see a planning estimate preview from representative examples or defaults.
Planning estimate · platform-generated Transport Emissions Statement preview · not an official certificate or customs filing · data quality: estimated
Route-leg emissions breakdown
Estimated, modelled per-leg factors for audit review only. Sum of legs is an illustrative decomposition of the corridor total — platform-generated estimate, not an accredited verification. Factors are Corridor OS planning defaults by corridor segment; carrier/operator-provided factors should override these when available. Leg rows show kg CO₂e; report totals are summarised in tonnes.
| Leg | Mode | Distance | Factorkg CO₂e/t-km | CO₂e (kg) | Data quality |
|---|---|---|---|---|---|
| Xi'an → Lanzhou | Rail | 676 km | 0.032 | 519.2 kg | estimatedCorridor OS default · China rail (WTW, GLEC-aligned)corridor_os_iso14083_glec_regionalized_v2 |
| Lanzhou → Korla | Rail | 2,194 km | 0.032 | 1685.0 kg | estimatedCorridor OS default · China rail (WTW, GLEC-aligned)corridor_os_iso14083_glec_regionalized_v2 |
| Korla → Khorgos | Rail | 1,295 km | 0.032 | 994.6 kg | estimatedCorridor OS default · China rail (WTW, GLEC-aligned)corridor_os_iso14083_glec_regionalized_v2 |
| Khorgos → Almaty | Rail | 369 km | 0.034 | 300.7 kg | estimatedCorridor OS default · Kazakhstan rail / KTZ corridor (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Almaty → Shymkent | Rail | 746 km | 0.034 | 608.7 kg | estimatedCorridor OS default · Kazakhstan rail / KTZ corridor (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Shymkent → Aktau | Rail | 2,066 km | 0.034 | 1685.9 kg | estimatedCorridor OS default · Kazakhstan rail / KTZ corridor (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Aktau → Baku | Sea | 469 km | 0.045 | 506.5 kg | estimatedCorridor OS default · Caspian RoRo/rail ferry (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Baku → Tbilisi | Rail | 551 km | 0.026 | 343.8 kg | estimatedCorridor OS default · Azerbaijan / Georgia rail (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Tbilisi → Poti | Rail | 310 km | 0.028 | 208.3 kg | estimatedCorridor OS default · Georgia feeder rail/road (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Poti → Constanța Port | Sea | 1,093 km | 0.035 | 918.1 kg | estimatedCorridor OS default · Black Sea short-sea (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Constanța Port → Bucharest | Rail | 225 km | 0.024 | 129.6 kg | estimatedCorridor OS default · EU rail (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Bucharest → Budapest | Rail | 870 km | 0.024 | 501.1 kg | estimatedCorridor OS default · EU rail (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Budapest → Vienna | Rail | 252 km | 0.024 | 145.2 kg | estimatedCorridor OS default · EU rail (WTW)corridor_os_iso14083_glec_regionalized_v2 |
| Vienna → Rotterdam Port | Rail | 1,131 km | 0.024 | 651.2 kg | estimatedCorridor OS default · EU rail (WTW)corridor_os_iso14083_glec_regionalized_v2 |
Hub transshipment (5 modelled lifts): +220.8 kg CO₂e — included in the statement total, outside the per-leg rows (GLEC hub scope, estimated).
Factor column: kg CO₂e per tonne-km — values shown with three decimals (planning defaults by segment). Hover a cell for factor-source label. A future Route Optimiser may swap route options (fastest / cheapest / green) and refresh this breakdown without changing saved drafts in this preview phase.
Factor sources & provenance
Published frameworks and bands the planning factors are anchored to. “Regionalized estimate” entries are Corridor OS adjustments for grid/traction mix — not figures quoted by the source. Verify against the licensed copy before treating any value as accredited.
WTW transport-chain accounting basis; the reference standard underpinning the EU CountEmissions EU initiative.
Rail freight default intensities, electric + diesel traction, WTW.
Value set to 0.032 by lifting the electric-rail base toward the high end for China's coal-weighted grid plus diesel feeders — a Corridor OS planning estimate, not a figure quoted by the source.
Rail freight WTW default intensities, mixed electric/diesel traction.
Value 0.034 derived for Kazakhstan's coal-heavy grid + diesel on non-electrified steppe segments; Corridor OS planning estimate pending KTZ primary data.
Sea — RoRo / vehicle ferry, HFO, WTW default intensity.
Short, small, low-utilisation ferry classes; 0.045 sits inside the published RoRo HFO band rather than being scaled down to box-ship values.
Electric rail freight WTW default intensities.
Value 0.026 set just above the EU electric-rail band for the AZ gas-weighted / GE hydro-heavy grids on the electrified spine; Corridor OS planning estimate.
Electric rail freight + short road-drayage WTW defaults.
Value 0.028 blends Georgia hydro-grid electric rail with a small road-drayage share on short feeders; Corridor OS planning estimate, candidate for a rail/road split.
Sea — container feeder & short-sea vessel classes, WTW.
Value 0.035 placed mid-band for small, lower-utilisation Black Sea feeder/RoRo families; Corridor OS planning estimate, not a quoted single-vessel figure.
EU policy anchor; confirms ISO 14083 as the methodological basis for reported transport emissions.
EU electric rail freight, EU grid average, WTW.
0.024 sits inside the published EU electric-rail WTW band.
Report draft content
Populated
Methodology notes
In draft
Baseline comparison
Shown in draft
Dossier documents
Workflow review required
Partner verification
Separate accredited process
Loading saved workspace shipments…
Save or select a workspace shipment before saving this workspace report draft.
This view is a platform-generated workspace preview of Transport Emissions Statement data sourced from Corridor OS planning inputs. It supports internal readiness and sustainability workflows — Corridor OS does not issue official certificates from this preview.
It is not a customs filing or CBAM declarable record on its own. Verification, attestations, and regulator submissions remain your responsibility and proceed through authorised partners separately.
Export actions open packaging steps so PDF, spreadsheets, buyer sharing drafts, or verifier-ready bundles can be reviewed before anything leaves the workspace — final filing decisions stay with your team.
Phase 2 · Partner review
Not yet submitted for partner review.
Example report records
6
CO₂e in example reportsi
352.5 t
Baseline · representative planning examplesTonnes (value above) · example report CO₂eSaving % · calculated where baseline is availableData quality · estimated
Renewals in window
2
Representative planning examples · filter by lifecycle status
Loading saved workspace report drafts…
| ID | Record | Standard | Linked ref | Created | Expires | CO₂e (t)i | Status |
|---|---|---|---|---|---|---|---|
| TES-2041 | Corridor low-carbon lane | GLEC Framework v3 | SHP-4891 · Xi'an–Aktau | 12 Jan 2026 | 12 Jan 2027 | 42.6 | Active |
| TES-1988 | Caspian Ro-Ro documentation record | ISO 14083 / GLEC-aligned | SHP-5061 · Aktau–Baku | 03 Nov 2025 | 03 May 2026 | 18.2 | Renewal due |
| TES-2112 | Black Sea short-sea bundle | Smart Freight Centre | SHP-5104 · Baku–Constanța | 28 Feb 2026 | 28 Feb 2028 | 56.0 | Active |
| TES-1876 | EU rail last-mile | EN 16258 | SHP-4988 · Khorgos–Duisburg | 08 Jun 2024 | 08 Jun 2025 | 31.4 | Expired |
| TES-2099 | Reefer energy profile | Product carbon footprint | SHP-5150 · Tbilisi–Istanbul | 15 Mar 2026 | 15 Sep 2026 | 9.8 | Renewal due |
| TES-2134 | Block train mass-balance | ISCC EU | Lane contract · CRL-882 | 01 Apr 2026 | 01 Apr 2027 | 120.5 | Active |
| TES-2055 | Port electrification scenario | GHG Protocol · Scope 3 | Poti terminal · FY25 | 20 Dec 2025 | 20 Dec 2026 | 74.0 | Active |
Showing 7 of 7 records · Representative planning examples
Corridor OS generates workspace Transport Emissions Statement drafts, previews, and supporting evidence narratives. Outputs are intended for internal review or partner-ready packages — verification, customs, filings, or accredited attestations remain separate processes handled by your organisation and authorised third parties.
Transport Emissions Support File (TES) generator
Enter corridor endpoints, cargo class, and chargeable weight. We quantify CO₂e leg-by-leg (green routing profile) and compile a documented PDF suitable for customer documentation and green-lane / Scope 3 evidence workflows under the CountEmissions EU regime.
This is not a CBAM document — CBAM prices the production emissions of covered goods and sits with the EU importer. For CBAM obligations and how this report sits beside preferential origin, see the EU trade desk.
Report (PDF)
$95
per PDF
Equipment and commodity refinements use Route Optimizer defaults for this cargo class.
Generation uses the same corridor model as Route Optimizer (green profile).
Total CO₂e
9.419 t
Distance
12246 km
This calculator preview uses the same Route Optimizer green-profile model; detailed saved-report evidence is shown in the Transport Emissions Statement above. Uses Corridor OS planning defaults by corridor segment; carrier/operator-provided factors should override these when available.
| Leg | Segment | Mode | km | CO₂e (kg) |
|---|---|---|---|---|
| 1 | Xi'an → Lanzhou | 🚂 Rail | 676 | 519.2 |
| 2 | Lanzhou → Korla | 🚂 Rail | 2194 | 1685.0 |
| 3 | Korla → Khorgos | 🚂 Rail | 1295 | 994.6 |
| 4 | Khorgos → Almaty | 🚂 Rail | 369 | 300.7 |
| 5 | Almaty → Shymkent | 🚂 Rail | 746 | 608.7 |
| 6 | Shymkent → Aktau | 🚂 Rail | 2066 | 1685.9 |
| 7 | Aktau → Baku | 🚢 Sea | 469 | 506.5 |
| 8 | Baku → Tbilisi | 🚂 Rail | 551 | 343.8 |
| 9 | Tbilisi → Poti | 🚂 Rail | 310 | 208.3 |
| 10 | Poti → Constanța Port | 🚢 Sea | 1093 | 918.1 |
| 11 | Constanța Port → Bucharest | 🚂 Rail | 225 | 129.6 |
| 12 | Bucharest → Budapest | 🚂 Rail | 870 | 501.1 |
| 13 | Budapest → Vienna | 🚂 Rail | 252 | 145.2 |
| 14 | Vienna → Rotterdam Port | 🚂 Rail | 1131 | 651.2 |
Certificate of Origin support
DCFTA preferential corridor · Georgia to European Union
Draft a platform-generated support PDF with exporter and goods details on a DCFTA basis. Customs authority endorsement remains required for regulatory filings. Checkout delivers platform support documentation only — it does not create an official Certificate of Origin.
PDF (platform)
$50
per PDF
DCFTA basis
Preferential treatment under the EU-Georgia Association Agreement (Deep and Comprehensive Free Trade Area). Movement: Georgia to European Union member states, subject to rules of origin and supporting documents.
EU trade desk — how Corridor OS maps DCFTA origin documentation support to the EU CBAM regime and the shipment checklist.
Prepared for review by the relevant issuing authority. Header and layout are for documentation guidance only.
Revenue Service of Georgia
Customs Department
Authority information shown for documentation guidance only.
Certificate of Origin support (DCFTA)
Draft reference is generated by Corridor OS. Official certificate numbers are assigned only by the relevant issuing authority where applicable (reference format CO-YYYY-…).