Finn No Scraper

What does Finn No Scraper do?

Finn No Scraper extracts structured data from FINN.no — Norway's largest online marketplace — across real estate (homes for sale and rentals), used cars, and jobs. For every listing it captures the price, address, beds/baths/sqm, photos, seller/dealer contact, ad ID, and timestamps, pulling from both the search results pages and each listing's detail page.

The actor runs on the Apify platform, which gives you API access, scheduling, integrations, proxy rotation, and monitoring out of the box. You can run it once or on a schedule to track the Norwegian market over time.

Why use Finn No Scraper?

• Nordics-focused investors can track property prices, rental yields, and market trends across Norwegian cities.
• Realtors and property analysts get structured listing data (price, sqm, rooms, location) for comps and market reports.
• Auto dealers can monitor used-car inventory, pricing, and seller types (private vs. dealer).
• Recruiters and market researchers can pull job postings with company, location, and application deadlines.

How to use Finn No Scraper

1. Open the actor in Apify Console.
2. Pick a vertical (homes for sale, rentals, cars, or jobs).
3. Optionally enter a search query (e.g. Oslo, Toyota, sykepleier) and set max pages.
4. Click Start. The actor crawls the search pages, then each listing's detail page.
5. Download the dataset as JSON, HTML, CSV, or Excel.

Input

Field	Type	Default	Description
vertical	enum	realestate_homes	realestate_homes, realestate_lettings, cars, or jobs
searchQuery	string	empty	Optional keyword filter (e.g. Oslo, Toyota)
maxPages	integer	5	Max search result pages to crawl (~50 listings/page)
includeDetails	boolean	true	Also crawl each listing's detail page for full data
useApifyProxy	boolean	true	Route requests through the Apify residential proxy

Output

Each dataset row is one listing. Search-page rows carry the source: "search" summary; detail-page rows carry source: "detail" with the full key-info table, description, seller, and photos.

{
  "source": "detail",
  "vertical": "realestate_homes",
  "adId": "475553698",
  "title": "Innholdsrik 3-roms i 3.etg - Sentral beliggenhet i attraktivt område",
  "price": "3 750 000 kr",
  "priceNumber": 3750000,
  "address": "Havstadvegen 11 B, Trondheim",
  "keyInfo": {
    "Boligtype": "Leilighet",
    "Eieform": "Eier (Selveier)",
    "Soverom": "2",
    "Bruksareal": "75 m²",
    "Etasje": "3",
    "Byggeår": "2021"
  },
  "sellerName": "EiendomsMegler 1 Melhus",
  "photos": ["https://images.finncdn.no/dynamic/1280w/..."],
  "url": "https://www.finn.no/realestate/homes/ad.html?finnkode=475553698"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data table

Field	Description
adId	FINN ad ID (finnkode)
title	Listing title
price / priceNumber	Price as text and as a numeric NOK value
address / location	Street address and city/area
area	Square meters (real estate)
rooms	Number of rooms/bedrooms
keyInfo	Full key-value table from the detail page (beds, baths, sqm, year, fuel, mileage, etc.)
company / sellerName	Seller or dealer company
publishedAt	Publish timestamp (jobs)
photos	Array of image URLs
url	Canonical listing URL

Pricing / Cost estimation

This is a CheerioCrawler actor — it uses plain HTTP requests, no browser rendering — so it is very cheap to run. A typical run of 5 search pages + detail pages for one vertical costs a fraction of a compute unit. Free Apify users get a capped preview of 10 items; paid users get unlimited runs.

Technical notes — how the scraping works

FINN.no renders its search results server-side in the HTML. Recon showed:

• No __NEXT_DATA__ / __NUXT__ embedded JSON blobs with listing data.
• No Algolia/Meilisearch/Elasticsearch backend for listings (the searchContext API only returns market statistics).
• The listing data is fully present in the raw served HTML of the search and detail pages.

Therefore the actor uses CheerioCrawler (plain HTTP + HTML parsing) against the server-rendered pages:

• Search pages: https://www.finn.no/realestate/homes/search.html, /realestate/lettings/search.html, /mobility/search/car, /job/search — parsed for listing cards (article.sf-search-ad, article.job-card).
• Detail pages: /realestate/homes/ad.html?finnkode=XXXX, /mobility/item/XXXX, /job/ad/XXXX — parsed for the key-info table, pricing, description, seller, and photos.

Requests go through the Apify residential proxy (BUYPROXIES94952) to avoid IP blocks. This keeps the actor fast, cheap, and reliable — no browser needed.

Tips / Advanced options

• Limit cost: set maxPages to 1-2 for a quick sample, or disable includeDetails to only get search-card summaries.
• Track the market: schedule the actor to run weekly and compare priceNumber over time.
• Filter by location: use searchQuery with a city name (e.g. Bergen) to narrow results.

FAQ, disclaimers, and support

Is scraping FINN.no legal? FINN.no's robots.txt states that automated crawling requires written permission. Please review FINN.no's terms of service and applicable Norwegian law before using this actor at scale. This actor is provided for research and personal use; you are responsible for compliance.

Known limitations: FINN.no serves different page layouts per vertical, so field availability varies (e.g. jobs have no price; cars have no sqm). Some detail pages (external lettings) may lack the full key-info table.

For feedback or feature requests, open an issue on the actor's Issues tab. Need a custom solution or a different Norwegian data source? Contact us — we build custom scrapers on request.