BIZTRAC BETA
Work training and permanently adapted work

HAPRO JOBB OG KARRIERE AS

Org. no. 918665773 Limited company (AS) Gran Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 32.2m
Operating profit NOK −7.8m
Equity NOK 8.4m
Incorporated 2017
Employees 69
Share capital NOK 1.8m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7,8 mill kr).

HAPRO JOBB OG KARRIERE AS is registered as a limited company in Gran, Innlandet with organisation number 918665773. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 2017 and has 69 registered employees. Registered share capital is NOK 1.8m, divided into 30 shares. The company's stated purpose is: “Yrkesmessig attføring og utvikling, samt annen virksomhet som er forenlig med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 32.2m in revenue and NOK −7.8m in operating profit.

Key figures · 2024

Revenue
NOK 32.2m
Operating profit
NOK −7.8m
Equity
NOK 8.4m
Est. value
NOK 31.3m

Financial health · 2024

Liquidity
2.34
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
57.4%
Very good
Equity as a share of total capital

Who owns HAPRO JOBB OG KARRIERE AS?

No shareholders are registered for HAPRO JOBB OG KARRIERE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HAPRO JOBB OG KARRIERE AS

What is the revenue of HAPRO JOBB OG KARRIERE AS?

HAPRO JOBB OG KARRIERE AS had revenue of NOK 32.2m in 2024.

Who is the general manager of HAPRO JOBB OG KARRIERE AS?

Thomas Haugen Skorpen is registered as general manager of HAPRO JOBB OG KARRIERE AS.

Where is HAPRO JOBB OG KARRIERE AS based?

HAPRO JOBB OG KARRIERE AS has its business address in Jaren.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.