Denmark Job Market Stats – Jobindex job counts by region avatar

Denmark Job Market Stats – Jobindex job counts by region

Pricing

from $1.50 / 1,000 listing analyzeds

Go to Apify Store
Denmark Job Market Stats – Jobindex job counts by region

Denmark Job Market Stats – Jobindex job counts by region

Counts of Danish job postings on Jobindex.dk by region (the 5 regioner) and job category, read from the site's region pages and 30 occupation searches. Aggregates only, no postings or names. Read live from list pages on each run.

Pricing

from $1.50 / 1,000 listing analyzeds

Rating

0.0

(0)

Developer

Yusuke Suda

Yusuke Suda

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

How many jobs are advertised on Jobindex.dk in each of Denmark's five regions (Hovedstaden, Sjælland, Syddanmark, Midtjylland, Nordjylland) and in 13 job categories. Counts only: Jobindex.dk shows no pay on its list pages. A sample, not the whole market: see How the counts are made.

Example

SiteRegionPostingsWith payMedian pay (lower bound)
jobindex.dkHovedstaden2230–
jobindex.dkMidtjylland1300–
jobindex.dkSyddanmark1030–

Default input, run on 22 October 2026: 182 listings read in 1.9 minutes, 59 aggregate rows; at $1.50 per 1,000 listings read the run cost $0.27.

What you get, and what you don't

  • Counts, not listings. The run returns aggregate rows only: no titles, no advertisers, no addresses, no texts, no links, no contact details, no person's name. Nothing about an individual listing leaves the run.
  • List pages only. The run reads the site's public search-result pages, paced as the site's own Actor in this catalogue is (one request every 2 seconds), and never opens a listing's own page.
  • A sample of the newest listings. The site lists newest first; the run counts up to maxListings of them. The summary row says how many were read and, where the site shows it, the site's own total.
  • Medians need 5 values. A median is shown only where at least 5 postings have the value; otherwise it is empty.
  • The last row of every run is a summary per site: postings read, the site's own total where shown, whether the run stopped at maxListings, and any warning (an unknown place, a blocked page).

Input

FieldWhat it does
maxListingsPostings to read and count at most (default 1,000, up to 10,000).
regionOne region only (see below). Empty: the whole country.
categoryOne job category only: it, finance_admin_hr, sales_customer, production, engineering_technical, transport_logistics, construction, health_care, education, hospitality_food, cleaning_security, management, other.
keywordCount only the postings the site finds for this word.
occupationSearchesOff (default): the site's 10 region pages only, about 200 postings in about 2 minutes. On: also 30 occupation searches, about 800 postings at most in all, several minutes more.

Example: {"region": "Midtjylland", "category": "health_care"}. An input the run cannot use (an unknown region, a keyword with no result) ends SUCCEEDED with no rows and the reason in the status message and the run report (RUN_REPORT).

Output

FieldMeaning
levelregion (one row per region), region_category (per region and job category) or summary.
dateDay of the run (UTC).
sourceThe site counted.
regionRegion, abroad or unmapped.
categoryJob category (all on region rows).
postingsPostings read in this group.
postings_with_payOf them, postings that state pay.
pay_unit, currencyThe pay period and currency of this row's median. A group with several units has one row per unit.
postings_with_this_unitPostings with pay in this unit and currency.
median_pay_lowerMedian of the lower bound of the advertised pay; empty below 5 postings.

How the counts are made

Jobindex.dk's robots.txt lets a reader see the first 20 postings of a search and no second page, so the run reads the site's 10 region pages (about 200 postings) and, with occupationSearches on, 30 occupation searches as well: about 800 postings at most, of the roughly 19,000 the site held on 15 October 2026. The summary row says so. The place each posting shows is put in its region with a table of about 300 Danish towns; a place not in the table stays unmapped (13 % in the example run). With region set, the same searches are read and only that region is kept; with keyword, the keyword is searched on each of the 10 region pages.

Jobindex.dk shows no pay on its list pages: postings_with_pay is 0 and the pay columns are empty.

Job categories are found from keywords in the job title (English and the site's language), first match wins, other when nothing matches: approximate. Share of other in the example run: 12 %.

Pricing

$1.50 per 1,000 postings read (event listing-analyzed), no start fee. The aggregate rows themselves are free: a default run reads up to 1,000 postings and costs at most $1.50. Set a maximum charge per run in the run options to cap it.

Good to know

  • The data is what Jobindex.dk shows on its public list pages on the day of the run.
  • Run it on a schedule (daily or weekly) and keep the datasets for a time series; each row carries its date.
  • Questions or a missing region: open an issue on this Actor.