Finn.no Scraper — Norwegian Property Listings | No Proxy
Pricing
from $0.97 / 1,000 finn.no scraper — norwegian property listings | no proxies
Finn.no Scraper — Norwegian Property Listings | No Proxy
Scrape Finn.no Norwegian property listings. Returns price, total price, shared expenses, address, ownership type, viewing schedule, bedrooms and photos. No proxy needed. Pay per listing.
Pricing
from $0.97 / 1,000 finn.no scraper — norwegian property listings | no proxies
Rating
0.0
(0)
Developer
Vitalii Bondarev
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
7 days ago
Last modified
Categories
Share
Finn.no Scraper — Norwegian Property Listings | $1.50/1K | No Proxy
For Norwegian real estate investors, buyer's agents, and Nordic PropTech platforms who need structured data from Finn.no — Norway's dominant property portal with 95%+ market share.
$1.50 per 1,000 listings.
Scrape Finn.no — Norway's #1 classifieds and real estate portal. Extracts structured listing data from any search URL: price, total cost, shared expenses, address, area, ownership type, property type, bedrooms, viewing times, and photos.
No proxy required. No authentication. Parses HTML listing cards with parsel — stable field extraction.
What you get
| Field | Description |
|---|---|
listing_id | Finn code (finnkode) |
title | Listing title |
price | Asking price in NOK |
price_raw | Raw price text |
total_price | Total price including fees (NOK) |
shared_expenses | Monthly shared expenses (NOK) |
currency | Always "NOK" |
area_m2 | Living area in m² |
ownership_type | "Selveier", "Aksje", "Andel", etc. |
property_type | "Leilighet", "Enebolig", "Rekkehus", etc. |
bedrooms | Number of bedrooms |
address | Street address |
city | City name |
viewing | Next viewing date/time |
url | Full Finn ad URL |
image_url | Main listing photo (960px) |
scraped_at | Scrape timestamp (ISO 8601 UTC) |
parse_confidence | Data quality score 0.0–1.0 |
warnings | Quality issue codes |
How it works
Finn.no renders listing cards server-side as <article> elements with full data in text content. The actor fetches search pages and parses each card using parsel CSS/text selectors. Pagination via ?page=N parameter.
~50 listings per page. No detail-page fetches needed.
Input
{"searchUrl": "https://www.finn.no/realestate/homes/search.html?location=0.20061","maxItems": 50}
Works with any Finn.no real estate search URL — location, price, size filters all work.
Output sample
{"listing_id": "382814524","title": "Lys og pen 3-roms leilighet med balkong og garasjeplass","price": 5490000,"total_price": 5742500,"shared_expenses": 4200,"currency": "NOK","area_m2": 72,"ownership_type": "Aksje","property_type": "Leilighet","bedrooms": 2,"address": "Pilestredet 75C","city": "Oslo","viewing": "Lørdag 15. juni kl. 13:00","url": "https://www.finn.no/realestate/homes/ad.html?finnkode=382814524","parse_confidence": 0.95,"warnings": []}
Pricing example
| Run size | Cost |
|---|---|
| 50 listings | ~$0.075 |
| 1,000 listings | ~$1.50 |
| 10,000 listings | ~$15.00 |
| + viewing schedule | +$0.50/1K |
FAQ
Do I need a Finn.no account or proxy? No account, no proxy. Works from Apify cloud IPs.
What output formats are available? JSON, CSV, Excel, XML — all via Apify dataset download or API.
Are GPS coordinates included?
Coordinates are not available from Finn.no search pages (search page only). Use the listing url to open the detail page for exact map location.
What if it returns empty results?
Check that your searchUrl is a valid Finn.no real estate search URL (must include /realestate/). The actor logs the issue and exits cleanly with 0 results rather than crashing.
Why this actor vs. competitors
| Feature | This actor | epctex/finn-scraper ($3/1K) | Typical Finn.no scraper |
|---|---|---|---|
| total_price (incl. fees) | Yes | No | Rarely |
| shared_expenses | Yes | No | No |
| ownership_type (Selveier/Aksje) | Yes | No | No |
| Viewing schedule | Yes | No | No |
| parse_confidence | Yes | No | No |
| Price per 1K listings | $1.50 | $3.00 | varies |
Note: GPS coordinates not available in current version (search-page only). Use the listing URL for exact location.
Legal note: ownership_type (Selveier vs Aksje/Andel) is a legally critical field in Norway — cooperative (Aksje/Andel) ownership affects financing options. This field is unique to Norwegian real estate and rarely available in competing scrapers.
parse_confidence
Every listing includes a parse_confidence score (0–1). Score < 0.8 means one or more critical fields are missing — check the warnings array before relying on those records.
Use with AI agents (MCP)
Tag: MCP_SERVERS. Returns clean JSON — drop into any n8n / Make / LangChain workflow without post-processing.
{"mcpServer": "https://mcp.apify.com/?tools=bovi/finn-listings"}
Competitive edge
parse_confidence+warningson every record- total_price + shared_expenses (full cost transparency)
- ownership_type (Selveier vs Aksje/Andel distinction)
- viewing date extracted
- No proxy COGS
Pricing
Pay-Per-Event (PPE):
| Event | Price |
|---|---|
listing-item (primary) | $1.50 / 1,000 listings |
viewing-schedule (premium) | $0.50 / 1,000 listings with viewing dates |
Listings with an upcoming viewing date fire the viewing-schedule event in addition to the base charge. Buyer's agents and buyer-coordination platforms use this field to track open-house schedules.
Integrations
Built for Norwegian real-estate investors and PropTech platforms monitoring Finn.no property prices and inventory — the JSON/dataset output drops into the tools you already run, no glue code:
- n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
- Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
- MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
- API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.
See all Apify integrations.