Network
Latvia: ports, pipelines and refineries
The ports, terminals and pipelines each refinery’s operator or a register names as connected to it. These are connections, not flows: nothing here says how much oil moved, or that any did.
Which ports and pipelines serve Latvia's refineries
Latvia has no crude oil refinery (IEA, Latvia 2024 Energy Policy Review). None of the ports or pipelines we hold a citation for is in Latvia.
“There is no domestic oil production nor refinery in Latvia. The country, therefore, relies exclusively on oil imports for its domestic consumption.” (IEA, Latvia 2024 Energy Policy Review)
Eurostat nrg_cb_oilm crude-oil refinery intake (nrg_bal=RI_OBS, siec=O4100_TOT, unit=THS_T) reports exactly 0.0 thousand tonnes in 198 monthly observations 2008-01 to 2026-06 - a REPORTED zero in every month, not a gap. Fetched 2026-09-22; dataset last updated 2026-09-10. ORLEN's 2023 Integrated Report independently calls Mazeikiai 'the only refinery in the Baltic states (Lithuania, Latvia and Estonia)'. WARNING: the EEA Industrial Emissions Portal's only Latvian IED Annex I 1.2 installation is SIA Rigas satiksme, Riga's municipal public-transport operator - a national reporting misclassification, not a refinery. It must never be loaded as one.
Source: iea.blob.core.windows.net · raportzintegrowany2023.orlen.pl · ec.europa.eu
Source & method
Refinery reference listUnknown
Provenance
UnknownUnknown- Publisher
- not recorded
- Dataset id
- not recorded
- Period
- not recorded
- Retrieved
- not published
- Type
- Unknown
- Transformation
- none applied - stored exactly as published
- Licence
- not recorded
We have not established whether the licence permits redistribution. An unestablished licence is treated as a no, not as a yes.
- Infrastructure, not flows. Each line is a cited connection (CONNECTED_TO): the source says the berth or pipeline exists and serves the refinery. It does not say that any crude or product moved through it, in which direction, or how much.
Each line is a CONNECTED_TO record: the refinery’s operator, a port authority or a register names the port, terminal or pipeline as serving the refinery. It is infrastructure, never a flow (a flow would be RECEIVED_FROM, which needs a record of oil moving; none is drawn here). Columns run ports and terminals, pipelines, refineries; a port’s line passes between the pipelines because no source here links a port to a pipeline. Countries of ports and pipelines come from the geography rows that draw them on the map; the tag after a name lists them when they are not the page’s own country.
- Infrastructure, not flows. Each line is a cited connection (CONNECTED_TO): the source says the berth or pipeline exists and serves the refinery. It does not say that any crude or product moved through it, in which direction, or how much.
- Countries of ports and pipelines come only from the geography rows that draw them on the map; an asset with no geography row has no cited country, and whether it crosses a border is unknown.
- Reference rows that may describe the same real pipeline under different names are kept apart, each with its own citation. We do not merge them.
- Refinery counts are the refineries on our cited reference list, every status included.
- Summary template network.country.confirmed_none, version 1.0.