FinnNo Property Scraper
DeprecatedPricing
from $0.80 / 1,000 results
FinnNo Property Scraper
DeprecatedExtract real estate listings from FinnNo in seconds. Scrape property data including prices, locations, descriptions & images. Perfect for market analysis, competitor tracking & lead generation on Norway's largest property portal.
Pricing
from $0.80 / 1,000 results
Rating
5.0
(2)
Developer
Shahid Irfan
Maintained by CommunityActor stats
1
Bookmarked
24
Total users
5
Monthly active users
5 days ago
Last modified
Categories
Features
Share
What does Finn.no Property Scraper do?
Finn.no Property Scraper collects homes for sale from Finn.no, Norway's largest property marketplace, and saves them as a clean dataset. Give it a search URL from Finn.no and it returns the listings on that page: address, asking price, total price, monthly shared costs, property type, ownership type, bedrooms, living area, coordinates, broker, photos, and viewing times.
Every listing comes from the search payload: address, asking price, total price, monthly shared costs, property type, ownership type, bedrooms, area, price and bedroom ranges for new-build projects, coordinates, broker, photos, features, flags, and viewing times. The Actor never opens a listing page, so a run costs one request per search page.
The output is ready for spreadsheets, dashboards, price monitoring, or a property database. No Finn.no account and no API key are needed.
Why use Finn.no Property Scraper?
- Structured property data - One row per listing with consistent field names, not copied page text.
- Filters that stay on Finn.no - Area, price range, ownership type, and listing status are applied by Finn.no itself when you pass the search URL.
- Search-only, one request per page - Finn's own search payload already carries the price, area, bedroom, broker, photo, and viewing data, so runs stay small and fast.
- Scheduled runs - Run daily or hourly to track new listings and price changes, export to CSV, Excel, or JSON, or call the dataset from your own system.
Typical uses: tracking asking prices in a city, watching new listings in a neighbourhood, feeding a valuation model, building a broker lead list, or collecting market data for analysis.
What data can you extract from Finn.no?
| Field | Description |
|---|---|
finnkode | Finn.no listing identifier |
url | Direct link to the listing |
title | Listing headline |
address | Street address, postal code, and city |
local_area_name | Neighbourhood name |
price_currency | Currency code, normally NOK |
asking_price | Asking price as text, for example 4 500 000 kr |
asking_price_nok | Asking price as a number |
asking_price_from, asking_price_to | Asking price range on new-build projects |
total_price | Total price including shared debt |
total_price_from, total_price_to | Total price range on new-build projects |
shared_costs_month | Monthly shared costs (felleskostnader) |
property_type | Apartment, house, townhouse, and so on |
ownership_type | Owner, housing cooperative, or share |
bedrooms | Number of bedrooms |
bedrooms_from, bedrooms_to | Bedroom range on new-build projects |
usable_area_sqm | Usable area in square metres |
usable_area_sqm_from, usable_area_sqm_to | Area range on new-build projects |
lot_area_sqm | Plot size for houses |
latitude, longitude | GPS coordinates when published |
broker_company | Estate agency name |
broker_logo_url | Estate agency logo |
image_url | Main photo |
image_urls | All listing photos |
viewing_times | Published viewing times |
next_viewing | First upcoming viewing |
features | Feature codes such as has_balcony |
listing_flags | Finn highlight flags |
ad_type | Finn ad type |
document_type | realestate or realestate_project |
published_at | Listing date |
scraped_at | When the record was collected |
How to use Finn.no Property Scraper
- Open Finn.no and set the filters you want: area, price, ownership type, or listing status.
- Copy the search URL from the address bar.
- Paste it into
startUrl. - Set
results_wantedandmax_pages. - Run the Actor and download the dataset.
If you leave startUrl empty, the Actor uses the general homes-for-sale search
in Oslo and the rest of Norway.
Input Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
startUrl | String | No | https://www.finn.no/realestate/homes/search.html | Finn.no property search URL, including any filters |
results_wanted | Integer | No | 20 | Maximum number of listings to save |
max_pages | Integer | No | 5 | Maximum number of search pages to read |
proxyConfiguration | Object | No | Apify Proxy | Proxy settings for the run |
startUrl accepts any Finn.no real-estate search page, for example
https://www.finn.no/realestate/homes/search.html?price_from=3000000&price_to=6000000.
Filters in the URL are kept as they are, so the results match what you see on
Finn.no.
Output Data
| Field | Type | Description |
|---|---|---|
finnkode | String | Listing identifier |
url | String | Listing URL |
listing_type | String | Real-estate section, for example homes |
status | String | Listing status, Til salgs for active listings |
title | String | Listing headline |
address | String | Full address |
local_area_name | String | Neighbourhood name |
price_currency | String | Currency code |
asking_price | String | Asking price as text |
asking_price_nok | Number | Asking price as a number |
asking_price_unit | String | Price unit, for example kr |
asking_price_from, asking_price_to | String | Asking price range on new-build projects |
total_price | String | Total price as text |
total_price_nok | Number | Total price as a number |
total_price_from, total_price_to | String | Total price range on new-build projects |
shared_costs_month | String | Monthly shared costs as text |
shared_costs_month_nok | Number | Monthly shared costs |
property_type | String | Property type |
ownership_type | String | Ownership form |
bedrooms | Integer | Bedroom count |
bedrooms_from, bedrooms_to | Integer | Bedroom range on new-build projects |
usable_area_sqm | Number | Usable area |
usable_area_sqm_from, usable_area_sqm_to | Number | Area range on new-build projects |
area_unit | String | Area unit, for example m² |
area_description | String | Finn area label |
lot_area_sqm | Number | Plot area |
lot_area_unit | String | Plot area unit |
lot_area_description | String | Plot area label |
latitude | Number | GPS latitude |
longitude | Number | GPS longitude |
coordinate_accuracy | Number | Finn coordinate accuracy code |
broker_company | String | Estate agency |
broker_logo_url | String | Estate agency logo |
image_url | String | Main photo |
image_path | String | Main photo path on Finn's CDN |
image_width, image_height, image_aspect_ratio | Number | Main photo dimensions and ratio |
image_urls | Array | Photo URLs |
viewing_times | Array | Viewing times |
next_viewing | String | First upcoming viewing |
features | Array | Feature codes such as has_balcony |
features_text | String | Feature codes as comma-separated text |
listing_flags | Array | Finn highlight flags |
labels | Array | Finn labels |
styling | Array | Finn styling hints |
extras | Array | Finn extras |
is_private_broker | Boolean | Private seller, when labelled |
ad_type | String | Finn ad type |
search_id | String | Finn search key |
document_type | String | realestate or realestate_project |
published_at | String | ISO date from the listing timestamp |
published_epoch_ms | Number | Listing timestamp in milliseconds |
scraped_at | String | ISO timestamp |
Empty values are dropped, so a missing key means Finn does not publish that field for the listing. Range fields appear on new-build project ads only.
Usage Examples
Basic run
Collect the first 20 homes for sale:
{"startUrl": "https://www.finn.no/realestate/homes/search.html","results_wanted": 20}
Filtered search across several pages
Read a filtered Oslo search over three pages:
{"startUrl": "https://www.finn.no/realestate/homes/search.html?location=0.20061&price_to=6000000","results_wanted": 50,"max_pages": 3}
Another real-estate section
Collect plots for sale instead of homes:
{"startUrl": "https://www.finn.no/realestate/plots/search.html","results_wanted": 10,"max_pages": 1}
Sample Output
{"finnkode": "480441498","url": "https://www.finn.no/realestate/homes/ad.html?finnkode=480441498","listing_type": "homes","status": "Til salgs","title": "Lys og attraktiv 2-roms fra 2024! Lave FK, heis og solfylt balkong","address": "Vollebekkveien 2 G, 0598 Oslo","local_area_name": "Vollebekk","price_currency": "NOK","asking_price": "4 500 000 kr","asking_price_nok": 4500000,"asking_price_unit": "kr","total_price": "4 638 898 kr","total_price_nok": 4638898,"total_price_unit": "kr","shared_costs_month": "3 200 kr","shared_costs_month_nok": 3200,"property_type": "Leilighet","ownership_type": "Eier (Selveier)","bedrooms": 1,"usable_area_sqm": 39,"area_unit": "m²","latitude": 59.9471,"longitude": 10.8752,"broker_company": "Nordvik","image_url": "https://images.finncdn.no/dynamic/default/2026/8/vertical-2/example.jpg","image_urls": ["https://images.finncdn.no/dynamic/default/2026/8/vertical-2/example.jpg"],"viewing_times": ["22. mars 2026, 12:00"],"next_viewing": "22. mars 2026, 12:00","features": ["has_balcony", "has_elevator"],"ad_type": "realestate","document_type": "realestate","published_at": "2026-03-18T09:00:00.000Z","scraped_at": "2026-11-07T09:12:44.115Z"}
Tips for Best Results
- Copy the search URL after applying filters on Finn.no, so the Actor reads exactly what you see.
- Start with
results_wantedaround 20 to check the output before scheduling a large run. - Keep
max_pageslow for new-listing monitoring; use higher values for a full market snapshot. - Each search page holds up to 50 listings, so
results_wantedabove 50 needsmax_pagesabove 1. - Long runs can hit rate limits near the end; on a challenge the Actor retries once on a fresh proxy session, but a smaller batch per run is more stable.
- Proxy addresses that Finn has challenged stay blocked for a while. Space out repeated runs, and use residential proxies when datacenter ranges start getting challenged.
- When a field is empty, check the listing on Finn.no before assuming the run failed.
Integrations
- Google Sheets - Send each run to a spreadsheet for filtering and charts.
- Webhooks - Trigger your own system when a run finishes.
- Make or Zapier - Route new listings to email, Slack, or a CRM.
- API - Read the dataset from your own application or data warehouse.
- Schedules - Run daily or hourly to track new listings and price changes.
Frequently Asked Questions
Can I export Finn.no property data to CSV or Excel?
Yes. Apify datasets download as CSV, Excel, JSON, XML, and other formats from the Console or from the dataset API.
Can I run this Actor on a schedule?
Yes. Create a schedule in Apify Console with your search URL and filters. The Actor saves new listings into a dataset on each run.
Can I scrape other property types, such as plots or holiday homes?
Yes, if Finn.no publishes that search as a real-estate page. Use the matching search URL, for example a plots or holiday-home search page.
Can I use my own filters from Finn.no?
Yes. Filters in the startUrl are kept, so price range, area, ownership type, and listing status apply exactly as they do on Finn.no.
Why are some fields empty?
Fields such as build_year, energy_label, and agent_phone are not part of
Finn's search payload, so they are not collected. Fields that do appear follow
the values Finn publishes on the search results page.
Does this Actor require a Finn.no login?
No. It reads public listing pages. No account, cookie, or API key is needed.
Is it legal to collect data from Finn.no?
Collecting public web data can be legal, but you are responsible for following Finn.no's terms, Norwegian law, and privacy rules. Use the data for legitimate purposes and do not republish personal contact details without a legal basis.
Support
Report a problem or request a field through the Issues tab on the Actor page. Include the search URL, the input you used, and the run log so the issue can be reproduced.
Legal Notice
This Actor collects publicly available property listings from Finn.no. The developer is not affiliated with Finn.no. Users are responsible for how the data is used and for complying with applicable law and the website's terms.