Elering Nord Pool Electricity Prices Scraper
Pricing
from $1.63 / 1,000 results
Elering Nord Pool Electricity Prices Scraper
Scrapes Nord Pool day-ahead spot prices from Elering for the Baltic and Finnish bidding zones. Returns hourly prices per MWh with zone and UTC timestamp for a date range you set.
Pricing
from $1.63 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
8 days ago
Last modified
Categories
Share
Elering Nord Pool Electricity Prices Scraper
Scrape Nord Pool day-ahead electricity prices from Elering for Estonia, Finland, Latvia, and Lithuania. Every record includes the spot price per MWh, bidding zone, and UTC timestamp. Export to CSV, JSON, Excel, or XML.
Elering publishes Nord Pool day-ahead spot prices for the Baltic and Finnish bidding zones, but pulling historical ranges by hand means clicking through a calendar and copying tables. This Actor reads the public price feed directly, so you get a clean dataset filtered by date range and zone, with no manual work. It works for recent days and historical periods alike.
| Who uses it | What they scrape Elering for |
|---|---|
| Energy analysts | Build price history datasets for Baltic and Finnish power markets. |
| Traders and portfolio managers | Pull yesterday's settlement prices into a model or spreadsheet. |
| Industrial electricity buyers | Track daily spot prices to time flexible consumption. |
| Researchers and students | Collect long price series for energy economics papers. |
What it does
This Actor collects Nord Pool day-ahead electricity spot prices from Elering for a date range and set of bidding zones, and returns each hourly price as a flat row.
- 📅 Date range control: set an inclusive start and exclusive end date, or leave both empty to default to the previous day.
- 🌍 Zone filter: pick any combination of Estonia (ee), Finland (fi), Latvia (lv), and Lithuania (lt), or leave empty to get all four.
- ⏱️ Hourly granularity: each row is one hour in one bidding zone, with the spot price in EUR per MWh.
- 📊 Flat output: every record lands in a uniform schema ready for CSV, JSON, Excel, or XML export.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Elering data
📈 Build a Baltic power price curve.
An energy analyst pulls daily spot prices for the last three years across all four zones to feed a forward curve model.
💰 Settle a day-ahead trading book.
A trader runs the Actor each morning with yesterday's date and the Finnish zone to get settlement prices for their positions.
🏭 Schedule industrial load.
A factory energy manager scrapes tomorrow's published prices for Estonia to decide when to run power-hungry processes.
📝 Feed an academic study.
A PhD student collects a decade of hourly prices for all four zones to analyze price convergence in the Nord Pool area.
Why choose this scraper
| What you get | |
|---|---|
| No API key needed | Reads the public Elering price feed directly. |
| Full zone coverage | Estonia, Finland, Latvia, and Lithuania in one run. |
| Clean timestamps | Every row carries a UTC timestamp for easy alignment. |
| Flexible date ranges | Pull a single day or years of history in one go. |
How it compares
No other Store actor targets Elering the same way, so the honest comparison is with the alternatives teams actually weigh.
| Elering Nord Pool Electricity Prices Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When Elering changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor with a start and end date, and optionally narrow the output to specific Nord Pool bidding zones. Filters run as each price is read so only matching hours reach your dataset. The Input tab lists every parameter.
A first run with the defaults:
{"maxItems": 10}
A larger pull:
{"maxItems": 200}
Pricing
Pay-per-result: $0.0036 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.36 |
| 1,000 results | $3.60 |
| 10,000 results | $36.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Elering Nord Pool Electricity Prices Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Elering through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/elering-nordpool-prices-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that your date range covers days for which Elering has already published prices. Day-ahead prices for the current day appear by early afternoon CET. Also confirm you selected at least one bidding zone.
Why are some hours missing in my output?
Daylight saving time shifts can cause a 23-hour or 25-hour day. The Actor returns exactly the hours Elering publishes. Missing hours on a transition day are expected.
The run stopped before my full date range was collected.
You may have hit the maximum records limit set in the input. Increase the limit and rerun. If the range is very large, consider splitting it into smaller chunks.
I got an error about the date format.
Use YYYY-MM-DD format like 2026-06-06, or a full ISO timestamp like 2026-06-06T00:00:00.000Z. The end date is exclusive, so 2026-06-07 will stop before that day begins.
FAQ
| Question | Answer |
|---|---|
| What bidding zones are available? | The Actor covers the four zones published by Elering: Estonia (ee), Finland (fi), Latvia (lv), and Lithuania (lt). You can pick any subset or leave the field empty to get all four. |
| How far back can I pull prices? | Elering serves several years of history. The Actor will fetch whatever the public feed returns for your date range. Very old dates may return empty if Elering no longer holds them. |
| Can I get today's prices? | Day-ahead prices for the current day are usually published by the early afternoon Central European Time. If you request today and the prices are not yet available, the run will return no records for that day. |
| What does the price field represent? | Each row contains the Nord Pool day-ahead spot price for one hour in one bidding zone, expressed in euros per megawatt-hour (EUR/MWh). |
| Do I need an API key or login? | No. The Actor reads the same public price feed that Elering serves on its website, so no registration or key is required. |
| What time zone are the timestamps in? | All timestamps are in UTC. The hour field tells you which clock hour the price applies to in local time for that zone. |
| Can I get prices for other Nord Pool areas like Sweden or Norway? | This Actor only pulls the four zones published by Elering. For other Nord Pool areas you would need a scraper that reads the Nord Pool group site or the relevant national TSO. |
| How many records can I collect in one run? | You can set a limit up to 1,000,000 records. A full year of hourly data for four zones is about 35,000 rows, so the limit is high enough for multi-year pulls. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Elering AS. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
