Finn.no Mobility Scraper - Cars, MC, Boats & More avatar

Finn.no Mobility Scraper - Cars, MC, Boats & More

Pricing

from $3.00 / 1,000 results

Go to Apify Store
Finn.no Mobility Scraper - Cars, MC, Boats & More

Finn.no Mobility Scraper - Cars, MC, Boats & More

Scrape finn.no/mobility - Norway's largest vehicle marketplace with 100,000+ active listings. Extract make, model, year, price, mileage, and full spec sheets from 6 categories: cars, motorcycles, boats, B2B machinery, caravans, and mobilehomes.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

Black Falcon Data

Black Falcon Data

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

1

Monthly active users

11 hours ago

Last modified

Share

What does Finn.no Mobility Scraper do?

Finn.no Mobility Scraper extracts structured listing data from finn.no — including full descriptions. It supports keyword search, location filters, and controllable result limits, so you can run the same query consistently over time. The actor also offers detail enrichment (full descriptions) where the source provides them.

Key features

  • Incremental mode — recurring runs emit and charge only for listings that are new or whose tracked content changed. First run builds the baseline state; subsequent runs emit only new or changed records.
  • Detail enrichment — full descriptions where the source provides them.
  • Compact mode — AI-agent and MCP-friendly payloads with core fields only.

What data can you extract from finn.no?

Each result includes Core listing fields (listingId, adId, title, make, model, series, modelSpec, and year, and more) and detail fields when enrichment is enabled (description, motorTypeDetail, hoursUsedDetail, and detailImages). In standard mode, all fields are always present — unavailable data points are returned as null, never omitted. In compact mode, only core fields are returned.

Enable detail enrichment in the input to get richer fields such as full descriptions where the source provides them.

Input

The main inputs are a search keyword, an optional location filter, and a result limit. Additional filters and options are available in the input schema.

Key parameters:

  • category — Vehicle category to scrape. (default: "car")
  • query — Free-text search keywords (e.g. "Toyota HiLux"). Leave empty to browse all listings.
  • make — Filter by vehicle make (e.g. "Toyota", "BMW").
  • location — City or region (e.g. "Oslo", "Bergen").
  • yearFrom — Minimum model year.
  • yearTo — Maximum model year.
  • priceFrom — Minimum asking price in NOK.
  • priceTo — Maximum asking price in NOK.
  • maxResults — Maximum number of listings to return (0 = unlimited). Memory scales with this: ≤1000 results uses 256 MB, >1000 uses 512 MB. (default: 50)
  • fetchDetails — Fetch individual listing pages for full specs, description, and images. Slower but richer output. (default: false)
  • descriptionMaxLength — Truncate description text to N characters. 0 = no truncation. Only relevant when fetchDetails is true. (default: 0)
  • compact — Return core fields only (listingId, make, model, year, price, mileage, fuel, transmission, location, url). Ideal for AI-agent and MCP workflows. (default: false)
  • ...and 3 more parameters

Input examples

Basic search — Keyword-driven search with a result cap.

→ Full payload per result — all standard fields populated where the source provides them.

{
"query": "developer",
"maxResults": 50
}

Incremental tracking — Only emit jobs that changed since the previous run with this stateKey.

→ First run builds the baseline state. Subsequent runs emit only records that are new or whose tracked content changed. Set emitUnchanged: true to include unchanged records as well.

{
"query": "developer",
"maxResults": 200,
"incrementalMode": true,
"stateKey": "developer-tracker"
}

Compact filtered output — Combine filters with compact mode for a lightweight AI-agent or MCP data source.

→ Core fields only — ideal for piping into LLMs or downstream tools without token overhead.

{
"query": "developer",
"category": "car",
"maxResults": 50,
"compact": true
}

Output

Each run produces a dataset of structured listing records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.

Example listing record

{
"listingId": "c66ef363bf828396ffedebd7724557fb02343458ffa5ca71b12ad39b7555619c",
"adId": "458875842",
"title": "Tesla Model 3",
"make": "Tesla",
"model": "Model 3",
"series": null,
"modelSpec": "Long Range AWD",
"year": 2020,
"price": 234532,
"currency": "NOK",
"mileage": 76971,
"mileageUnit": "KILOMETER",
"fuel": "El",
"transmission": "Automat",
"registrationClass": {
"id": 1,
"value": "Personbil"
},
"sellerType": "Privat",
"salesForm": 1,
"registrationNumber": "EB24030",
"hasServiceDocuments": [],
"imageUrl": "https://images.finncdn.no/dynamic/default/item/458875842/cc17849f-dc4d-44c0-9717-4f0d3e66bd9b",
"lat": 59.9548,
"lon": 10.64009,
"location": "Oslo",
"drivingRange": 560,
"engineVolume": null,
"warrantyDuration": null,
"hoursUsed": null,
"associationMemberships": null,
"dealerGroupId": null,
"boatClass": null,
"boatLength": null,
"boatWidth": null,
"maxSpeed": null,
"motorFuel": null,
"motorSize": null,
"motorType": null,
"description": null,
"bodyType": null,
"power": null,
"engineSize": null,
"co2": null,
"driveType": null,
"color": null,
"seats": null,
"doors": null,
"weight": null,
"maxTowingWeight": null,
"euInspectionDue": null,
"condition": null,
"previousOwners": null,
"motorIncluded": null,
"motorManufacturer": null,
"motorTypeDetail": null,
"topSpeed": null,
"lengthFt": null,
"sleepingBerths": null,
"totalWeight": null,
"emptyWeight": null,
"payload": null,
"conditionReport": null,
"lengthCm": null,
"interiorLengthCm": null,
"widthCm": null,
"bedType": null,
"firstRegistered": null,
"registeredSeats": null,
"hoursUsedDetail": null,
"detailImages": null,
"url": "https://www.finn.no/mobility/item/458875842",
"portalUrl": "https://www.finn.no/mobility/item/458875842",
"publishedAt": "2026-04-06T20:55:53.448Z",
"scrapedAt": "2026-04-06T20:56:12.706Z",
"source": "finn.no",
"changeType": null
}

Incremental fields

When incremental: true, each record also carries:

  • changeType — one of NEW, UPDATED, UNCHANGED, REAPPEARED, EXPIRED.
  • firstSeenAt, lastSeenAt — ISO-8601 timestamps tracking the listing across runs.
  • isRepost, repostOfId, repostDetectedAt — populated when a new listing matches the tracked content of a previously expired one. Set skipReposts: true to drop detected reposts from the output.

How to scrape finn.no

  1. Go to Finn.no Mobility Scraper in Apify Console.
  2. Enter a search keyword and optional location filter.
  3. Set maxResults to control how many results you need.
  4. Enable includeDetails if you need full descriptions, contact info, or company data.
  5. Click Start and wait for the run to finish.
  6. Export the dataset as JSON, CSV, or Excel.

Use cases

  • Extract listing data from finn.no for market research and competitive analysis.
  • Track pricing trends across regions and categories over time.
  • Monitor new and changed listings on scheduled runs without processing the full dataset every time.
  • Feed structured data into AI agents, MCP tools, and automated pipelines using compact mode.
  • Export clean, structured data to dashboards, spreadsheets, or data warehouses.

How much does it cost to scrape finn.no?

Finn.no Mobility Scraper uses pay-per-event pricing. You pay a small fee when the run starts and then for each result that is actually produced.

  • Run start: $0.005 per run
  • Per result: $0.003 per listing record

Example costs:

  • 10 results: $0.03
  • 100 results: $0.3
  • 500 results: $1.5

Example: recurring monitoring savings

These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of listings that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency — the scenarios below are examples, not predictions.

Example setup: 200 results per run, daily polling (30 runs/month). Event-pricing examples scale linearly with result count.

Churn rateFull re-scrape run costIncremental run costSavings vs full re-scrapeMonthly cost after baseline
5% — stable niche query$0.60$0.03$0.57 (94%)$1.05
15% — moderate broad query$0.60$0.10$0.51 (84%)$2.85
30% — high-volume aggregator$0.60$0.18$0.42 (69%)$5.55

Full re-scrape monthly cost at daily polling: $18.15. First month with incremental costs $1.62 / $3.36 / $5.97 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.

FAQ

How many results can I get from finn.no?

The number of results depends on the search query and available listings on finn.no. Use the maxResults parameter to control how many results are returned per run.

Does Finn.no Mobility Scraper support recurring monitoring?

Yes. Enable incremental mode to only receive new or changed listings on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.

Can I integrate Finn.no Mobility Scraper with other apps?

Yes. Finn.no Mobility Scraper works with Apify's integrations to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.

Can I use Finn.no Mobility Scraper with the Apify API?

Yes. You can start runs, manage inputs, and retrieve results programmatically through the Apify API. Client libraries are available for JavaScript, Python, and other languages.

Can I use Finn.no Mobility Scraper through an MCP Server?

Yes. Apify provides an MCP Server that lets AI assistants and agents call this actor directly. Use compact mode and descriptionMaxLength to keep payloads manageable for LLM context windows.

This actor extracts publicly available data from finn.no. Web scraping of public information is generally considered legal, but you should always review the target site's terms of service and ensure your use case complies with applicable laws and regulations, including GDPR where relevant.

Your feedback

If you have questions, need a feature, or found a bug, please open an issue on the actor's page in Apify Console. Your feedback helps us improve.

You might also like