Bridge PowerValencia shore power
Report · Port of Valencia · onshore power supply · feasibility and first model

Valencia shore power: what the public data says.

What public data exists on every ship calling at the Port of Valencia, how far it gets us toward an hourly shore-side electricity demand curve, and what that first curve looks like for sizing batteries and supply contracts.

Prepared 9 Nov 2026 · model v0.2.1Calls Jan 2021 to Oct 202636,689 port calls · 3,392 vesselsTimes Europe/MadridOpen the scenario workspace →
2025 energy · mid · full adoption
193GWh
Low 125 · High 563 · FuelEU 2030 scope 175
2025 average demand
22.0MW
P80 26.6 MW · P95 32.1 MW
2025 peak hour
46.1MW
21 hours above 40 MW, none above 50
Ships at berth, 2025
24median
Range 10 to 45 at once

Main finding. The Port Authority's own community system publishes, without login, every merchant call since January 2021 with actual arrival and departure times and the terminal operator. That dataset, not paid AIS, is the backbone. AIS and vessel registries are only needed to attach ship identity and size.

Main caveat. Power per ship is taken from literature and a small set of published measurements, not metered at Valencia. The low-to-high spread is a factor of four. Treat the mid curves as a central estimate to be calibrated once measured OPS data exists.

Revision. The first version of this page (same day, model v0.1.0) showed 383 GWh and a 90.7 MW peak. Those coefficients added fuel-fired boiler output to the electrical load, which shore power never supplies. Version 0.2.0 reconciles every category against TNO 2025 R12590 and the IMO benchmarks it reproduces, and starts the connection one hour after the recorded port arrival. Version 0.2.1 adds a size for 887 container vessels from the liner service they run on. The old figures survive only as the "high" case.

1. What is available online, and at what level of detail

The question was how much maritime and GIS information can be had from public sources for every ship calling at Valencia: who calls, when they arrive and leave, and how long they stay. The sources fall into three tiers.

SourcePer-vessel detailHistoryCost / accessVerdict
ValenciaportPCS historic port-call search
valenciaportpcs.net/portcalls
Vessel name, call id, voyage, status, actual arrival and departure to the minute, port, terminal operator, agent, liner service. No IMO, GT or berth number.Jan 2021 to today, plus ~7 weeks of forecast callsFree, no login. Web form with JSON inside the HTML; Excel export works too.backbone
Valenciaport cruise forecast PDFsShip, IMO, LOA, draught, scheduled hours, agent, pax capacity2026 and 2027 (264 calls in 2026)Free PDFuse
Valenciaport monthly statistical bulletinAggregates only: calls and GT by ship type and portMonthly, years backFree PDF, no CSVvalidation
Valenciaport "Average call times by phase"Waiting vs berth time by ship type, from the port's own VTS recordsPeriodic reportPublic page, embedded charts; raw data by requestrequest
PCS SOAP web service (planned calls)Planned arrivals and departures, status, agent, customs manifestForecast and current onlyDocumented for PCS users; WSDL did not answer to anonymous requestsrequest
Global Fishing Watch Events APIPort-visit events for all AIS vessel types: start, end, duration, anchorage id, at-dock flag, MMSI2012 onwardFree account; non-commercial licence (CC BY-NC); 50k requests/daylicence check
WikidataIMO, MMSI, GT, length, built year for a large share of merchant shipsn/aFree SPARQL, bulkidentity
VesselFinderWeb: expected arrivals shown free but names locked; arrivals and departures only on paid plans (30 days). API: port-call events with MMSI, IMO, timestamp, no berthWeb 30 days; API unstatedWeb 4 to 139 USD/month; API 2 credits per event, price on requestpaid
DatalasticLive positions, historical tracks, port and terminal info31 days per historical requestFrom about 99 EUR/monthpaid
MarineTraffic, MyShipTrackingPort arrivals and departures, berth-level on top tiersPaidBlocked automated access entirelyblocked
aisstream.io, AISHubLive AIS positions worldwideNone; record it yourself from now onFree (AISHub needs you to run a receiver)live only
EMODnet Human ActivitiesGridded monthly vessel density rasters2017 onwardFreeno per-vessel
EU MRV (THETIS-MRV)Per-ship annual fuel, CO₂, including emissions at berth in EU ports2018 onwardFree, browser appcalibration
EALING results bookletValencia OPS FEED studies: MVA per quay, voltage, port-wide demand estimate2024Free PDFbenchmark

What the port-call records look like

Each PCS record is one call. The arrival and departure flags distinguish estimates from actual times, and for completed calls both are actual. A check against the cruise schedule shows the stored times are UTC, and that the recorded arrival is roughly 1.3 hours before the scheduled berth time, so the arrival is at the port or pilot station rather than all-fast at the quay.

FieldExampleUse in the model
VesselCIUDAD DE GRANADAJoin key to the vessel master list (IMO, GT, type)
PortCall / Voyage1202605687 · 80 / 80Unique call id
StatusCodeFIN (also PRV, AUT, OPE)Keep completed calls only
TimeArrival, TimeArrivalType2025-06-30 18:17 UTC, 1 = actualStart of stay
TimeDeparture, TimeDepartureType2025-06-30 22:35 UTC, 1 = actualEnd of stay; dwell = departure minus arrival
TerminalTRASMED GLE, S.L.Terminal grouping and ship class rules
RegularLineTRASMED-GLE SERVICIO BALEARESShip class (ferry, container service, cruise)
VesselAgent, CarrierAgentsGRIMALDI LOGISTICA ESPAÑA S.L.Context only

Across the 71 months the download returned between 435 and 582 calls per month for Valencia alone, with no failed months. After removing forecast calls, estimated times, harbour craft, and stays over 240 hours, 35,570 calls and 1.05 million ship-hours remain for the model.

2. The fleet that calls

3,412 distinct vessel names appear, 3,392 after merging renamed ships on their IMO number. Identity was resolved by bulk Wikidata lookup, the cruise forecast PDFs, and a rate-limited pass over a free vessel search for the ships with the most berth time. Coverage is measured in ship-hours because a handful of large container ships matter far more than hundreds of one-off callers.

Ship classVesselsCalls 2021–26Share of ship-hoursVessels with IMOHow classified
Container1,90317,06558.6%1,053CSP Iberian, APM, MSC terminals and container liner services
Service craft and other11167112.5%37Tugs, mooring boats, dredgers, lay-ups; excluded from the model
RoPax ferry4511,8568.2%42Balearia, Trasmed, GNV lines to the Balearics and Algeria
Tanker4961,8898.2%313TEPSA, Galp, liquid bulk lines
Bulk5046196.0%294Ership, Temagra, dry bulk lines
RoRo cargo1523,0935.0%116Valencia Terminal Europa (Grimaldi) short-sea services
Cruise1901,4801.4%188Names in the port's cruise forecasts
General cargo11160.1%5Erhardt, Berge and "varios"

Two thirds of ship-hours are tied to a confirmed IMO number and 64% to a registry gross tonnage. Ferries and cruise ships are essentially complete. The gap was in container ships: 942 vessels, 41% of container visits, had no size and fell to a default bin.

Container services run sister-size ships, so the model now takes the median GT of the sized vessels on the same liner service. Of 104 services with at least three sized ships, the middle one has a size spread (75th to 25th percentile) of only 1.14. This fills 887 vessels and leaves 313 container visits unsized, under 2%. The imputed sizes range from 8,000 to 211,000 GT, median 45,000. Each such visit is tagged in its evidence reference so it can be audited or replaced by registry data later. The effect on energy was small, a 5% reduction, because the IMO at-berth curve for container ships is flat: a 1,000 TEU feeder is rated at 370 kW and a 20,000 TEU ship at 1,400 kW. Size matters less than the kW-per-size coefficients themselves.

3. How long ships stay

Ship classCallsMedian stay (h)p90 stay (h)Pattern
RoPax ferry11,8094.524.7Arrive 17:00 to 18:00, sail 22:00 to 23:00; a sharp evening block
Cruise1,47311.213.4Daytime calls, 07:00 to 19:00, strongest on Saturdays
RoRo cargo3,07514.537.1Half-day to day-and-a-half
Container16,82332.185.9Multi-day; flat around the clock; 2025 median rose to 43 h
Tanker1,79242.6101.3Long, with cargo heating load
Bulk54786.5179.2Longest stays, lowest power

By terminal the medians are 34 h at CSP Iberian, 27 h at APM, 33 h at MSC, around 5 h at the Trasmed and Balearia ferry berths, and 12 h at Valencia Terminal Europa. The 2025 container jump, with slightly fewer calls, looks like congestion and waiting counted inside the stay rather than longer working time, so 2025 container energy is best read as an upper bound.

4. From calls to megawatts

Every call becomes a visit with a connection window: the recorded port arrival plus one hour to reach the berth (1.3 h for cruise ships, from the schedule comparison), minus half an hour at each end to connect and disconnect. Each visit's power is then resolved through a five-level evidence waterfall: a consultant override, a measurement of the same ship at this port, a measurement of the same ship elsewhere, a category and size model, and finally installed generator capacity times a demand factor. Today every visit resolves at level four because no overrides or measurements exist yet; the tables for them are in place and tested.

The category models carry three power levels. Mid follows the IMO at-berth benchmarks as reproduced in TNO 2025 R12590, replaced by TNO's own measured values where it has them (cruise, RoPax, RoRo, large tankers, general cargo). Low is roughly two thirds of mid. High keeps the EMSA ranges and the EALING Valencia design values, and is close to what version 0.1.0 of this page called mid. Energy, within-call profile shape and peak power are resolved independently, so a supply limit can expose unmet demand instead of hiding it.

Ship classSize binLow kWMid kWHigh kWPeak kWBasis for mid
Container<1,000 TEU2403701,000500IMO benchmark (TNO App. A)
Container3,000–5,000 TEU (default bin)7201,1003,0001,480IMO benchmark; TNO per-visit medians 800 to 1,400 kW agree
Container8,000–12,000 TEU7501,1504,0001,550IMO benchmark; TNO time series imply 1.2 to 2.5 kW per connected reefer
Container>14,500 TEU9101,4006,0001,890IMO benchmark; TNO 18 to 20k TEU ships averaged 780 to 1,900 kW
RoPax ferry20,000–40,000 GT9001,9504,0002,240IMO benchmark; EALING "ferries up to 4 MVA" as high
RoPax ferry>40,000 GT1,2002,0504,0002,750TNO measured 65,000 GT sisters at 1,900 to 2,200 kW
RoRo cargo<50,000 GT5207002,500830TNO measured about 690 kW
Cruise60,000–100,000 GT3,7004,40012,0005,000TNO measured three ships at 4,200 to 4,700 kW; IMO says 11,500
Cruise>150,000 GT7,7409,10016,00010,460TNO fit of 50.7 kW per 1,000 GT; EALING Perfecto Palacio 20 MVA
Tanker40,000–60,000 DWT4105902,0001,300TNO measured 45,000 DWT chemical tanker; boiler heat excluded
Bulk<35,000 DWT80110600160IMO benchmark, no TNO sample

The full table has 36 rows across nine categories and is in the project as an editable register with source, scope note and an "is assumption" flag per row. Peak kW is a separate column: measured interval maxima where TNO gives them, otherwise 1.35 to 2 times the mid average, marked as an assumption. The biggest judgement call is cruise: the mid rests on three ships of one owner, probably in mild weather, and Valencia summer air-conditioning could push real loads back toward the IMO figure.

5. The demand curve

Average day in 2025 by ship class

Mean shore-power demand per local hour, mid case, 100% connection. Dashed lines are the low and high totals.

Container ships form a flat 16 MW base around the clock. Cruise adds up to 4 MW between 08:00 and 17:00. Ferries add up to 10 MW between 18:00 and 22:00 as the Balearic night boats load, and are the clearest daily feature. The port-wide average swings between 19 MW at night and 28 MW at 20:00.

One week in July 2025, hour by hour

14 to 20 July 2025, mid case stacked by class, with low and high totals.

Individual days are far lumpier than the average. Cruise calls arrive in blocks of two or three ships and, with the evening ferries, push the total toward 37 MW for a few hours, then disappear. A weekday with no cruise ship sits near 20 MW all day.

Load duration curve, 2025

Hours of the year at or above a given demand. Reference lines at 20, 30, 40 and 60 MW.

Hour of day by day of week, 2025

Mean MW, mid case. Darker is higher.

Scenarios run on two separate axes. The power axis (low, mid, high) says how much a connected ship draws. The adoption axis says which ships connect: only those with confirmed OPS today (none, since no installation evidence has been entered yet), the FuelEU 2030 obligation set, a phased ramp, or every merchant visit.

Adoption case, 2025PowerGWhMean MWP80 MWP95 MWP99 MWMax MW
Current confirmed OPSany000000
Phased, 50% of FuelEU set (2028)mid9010.313.417.720.624.7
FuelEU 2030 set (container, RoPax, cruise > 5,000 GT)low11212.815.519.623.831.0
mid17520.024.429.834.743.2
high50657.769.382.994.8123.6
Full adoption (every merchant visit)low12514.217.121.325.533.0
mid19322.026.632.136.746.1
high56364.376.289.9101.6131.4

The power axis moves the answer far more than the adoption axis: high is 2.9 times mid, while going from the FuelEU set to every ship adds only 10%. Calibrating kW per ship against real meters is therefore worth more than refining who connects.

Monthly energy, 2021 to 2026, by ship class

GWh per month, mid case. 2026 ends in October.

Energy grew from 135 GWh in 2021 to 193 GWh in 2025, almost entirely from longer container stays rather than more calls. Cruise energy tripled between 2021 and 2022 as the season returned and has held at about 12 GWh a year since. Ferries are a steady 17 to 26 GWh.

Ships at berth per terminal, 2025 average by hour

Mean number of ships alongside, by terminal operator. The ferry terminals empty out overnight; the container terminals do not.

6. What this means for batteries and contracts

The table shows, for a given contracted-power cap, how much energy above the cap a battery would have had to supply in 2025 under the mid, full-adoption case, assuming perfect foresight and full recharge whenever demand is below the cap.

Cap MWHours above capDays with exceedanceMWh/day p50 (exceedance days)MWh/day p95 (all days)MWh/day maxLongest run above cap (h)Annual MWh above cap
205,2553646122233321028,646
252,377312151142141599,819
30774152642135272,451
3515336547110421
402166028664

Three conclusions follow, all conditional on the mid power assumptions.

  • Shore power at Valencia is a base-load problem first. Container ships alone hold the floor near 16 MW day and night. A cap at or below the 22 MW average would be exceeded for hundreds of consecutive hours, which no battery can carry.
  • Storage starts to make sense against caps between the 90th and 99th percentile, 30 to 40 MW. At 35 MW the cap is exceeded on 36 days, at most 10 hours in a row, and the worst day needs 71 MWh. At 40 MW it is 6 days, 6 hours and 28 MWh. The 45 MWh battery Steven just delivered for one ferry is the right order of magnitude for the whole port at a 35 to 40 MW cap.
  • The two load shapes a battery could usefully shave are the ferry evening block and cruise days. Both are scheduled months ahead, which favours contract design and day-ahead scheduling over oversized storage.

Under the high power case none of this holds: the average is 64 MW and 60 MW is exceeded for 5,113 hours. Until Valencia meters its first connections, the contract decision should be framed as a range, with the mid case as the planning basis and the high case as the stress test.

7. How the model compares with the port's own studies

SourceFigureThis model, 2025 mid
EALING FEED studies (2024)Port-wide shore power of 20 to 70 MVA average through the day; over 90 MVA if every berthed ship peaked at onceMid average 22 MW sits at the bottom of the band; high average 64 MW near the top. Mid hourly peak 46 MW; the sum of connected ships' peak ratings reaches 61 MW; high case peaks at 131 MW.
EALING per-quay designTransversal de Costa 10 MVA (container, 6.6 kV, two 5 MVA points); Poniente 16 MVA (cruise, ferries up to 4 MVA); Perfecto Palacio 20 MVARecorded as berths and study-status connections in the register. Per-berth loads cannot be checked without berth numbers in the call data.
OPS Valenciaport project (2024 to 2028)1.33 TWh over 2028 to 2051 across roughly 49,000 connected calls, about 55 GWh a year175 GWh a year for the FuelEU set at mid power and full uptake. The project figure implies three terminals and a slow ramp; the gap is mostly connection rate.
Net-zero plan 203031 supply points at 8 terminals, over 200 M EURConsistent with up to 45 ships alongside at once in 2025.
New substation ST2 (tendered Aug 2026)110 MW installed, two 55 MW transformers, 15.6 M EUR; doubles port supplyAmple for the mid case; the high case plus terminal and reefer load would approach it.

8. What to treat with care

  • No berth numbers. PCS names the terminal operator, not the quay, so per-connection-point peaks cannot be derived yet.
  • Arrival precedes all-fast. The recorded arrival is about 1.3 h before the scheduled berth time for cruise ships; a one-hour offset (1.3 h for cruise) is now applied, but container stays in 2025 may still include anchorage waiting.
  • Literature power values, thin measured base. TNO's measured samples are a few ships per category at unnamed northern ports, read from charts. Measured container loads vary by up to 300% with reefers and season. The low-to-high spread (125 to 563 GWh) is the honest range until Valencia meters its first OPS connections.
  • Adoption is a scenario, not a forecast. No vessel has installation evidence yet, so "current confirmed" is zero and the FuelEU and full-adoption cases bracket the outcome. The register has the fields to hold installation status as it is learned.
  • Timezone. Stored times were shown to be UTC by comparison with the cruise schedule across the daylight-saving change, and converted to local time.
  • Identity gaps. A third of ship-hours still lack a confirmed IMO. Their size now comes from the liner service rather than a default bin; 452 of the 887 imputed vessels sit on services that mix ship sizes and are flagged low confidence.

9. The data structure behind the numbers

The pilot is organised as the registers and workflow in the Bridge Power development brief, so that better evidence replaces assumptions row by row without rebuilding anything. Every hourly value can be traced back to the visits and the evidence level that produced it.

ComponentStatus at ValenciaFilledStill empty
Vessel register3,392 vessels keyed on IMOName and previous names, category, GT (registry for 1,793 vessels, imputed from liner service for 887), LOA, built year, estimated TEU, cruise passenger capacityOperator, reefer plugs, generator ratings, OPS installation status (all "unknown"), retrofit forecasts
Port, terminal, berth, connection registers1 port, 22 terminals, 3 berths, 6 connectionsTerminal mapping for every raw call string, approximate coordinates for four terminals, the three EALING quays with rated MVA, voltage and frequency as study-status connectionsBerth geometry and identifiers, operational connections, baseline port load profile, grid limits
Visit register36,689 calls, 35,553 includedPlanned and actual times, alongside window, connection window, quality flags, time zone, sourceBerth per visit, anchorage vs manoeuvring split from the port's own phase times
Evidence waterfallFive levels implemented and testedLevel 4 category models (36 rows, TNO and IMO based), within-call profile shapes, service-imputed sizes tagged in the evidence referenceOverrides, measured profiles (same port or elsewhere), installed-capacity fallback inputs
Scenarios4 adoption cases × 3 power levelsHourly totals and per-visit components, P50 to P99 capacity levels, unmet demand under 30 to 70 MW limitsBerth compatibility, traffic growth, existing OPS netting
Export24 draft files for 2021 to 2026 and 24 for calendar 2025, hourlyStart-of-interval timestamps in local and UTC, average kW, kWh, peak potential, splits by category and terminal, metadata sheet; 15-minute optionConfirmation of the format with Gridcog

10. Next steps and the data request to the Port Authority

A bilingual data-request letter to the Autoridad Portuaria de València has been drafted. It asks for six things, in order of value to the model:

  1. Call-level data with IMO, GT, berth number and the phase times the port already records (pilot on board, all fast, last line), plus anchorage waiting and whether OPS was used.
  2. The underlying tables of the "Average call times by phase" report.
  3. A GIS layer of quays, berths and terminal concessions with identifiers matching the call data.
  4. Electrical data: metered OPS energy per connection once the MSC quay installation runs, the port's hourly demand at the existing substation, rated power per planned connection point, and the EALINGWorks demand study datasets.
  5. The structure of current and planned supply contracts, as far as shareable.
  6. Access to the planned-calls web service or a bulk export of the historic search.

In return it offers the model, the hourly curves per terminal and the battery scenarios, under a data-sharing agreement. With items 1 and 4 the model moves from literature values to calibrated, berth-level curves; without them it remains a well-grounded envelope.

Two decisions are open with Steven and Gridcog: the export interval and format (hourly or 15-minute, kW or kWh, totals or components), and the pilot period (calendar 2025 or the full 2021 to 2026 history).

11. Sources