BIZTRAC BETA
Other health services

INGRID HARSEM AS

Org. no. 913305116 Limited company (AS) Færder Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 422,000
Operating profit NOK −9,000
Equity NOK 2.3m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

INGRID HARSEM AS is registered as a limited company in Færder, Vestfold with organisation number 913305116. The business is classified under other health services (NACE 86.993). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Medisinske tjenester-, sykepleiertjenester og alt som faller naturlig inn under dette. Deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 422,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 422,000
Operating profit
NOK −9,000
Equity
NOK 2.3m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns INGRID HARSEM AS?

INGRID CHRISTINE ROSENCRANTZ HARSEM
INGRID HARSEM AS
NOK 422,000 rev. · NOK −9,000 profit

INGRID HARSEM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INGRID HARSEM AS

Who owns INGRID HARSEM AS?

INGRID CHRISTINE ROSENCRANTZ HARSEM is the largest registered owner, with 100.0%.

What is the revenue of INGRID HARSEM AS?

INGRID HARSEM AS had revenue of NOK 422,000 in 2025.

Who is the general manager of INGRID HARSEM AS?

Ingrid Christine Rosencrantz Harsem is registered as general manager of INGRID HARSEM AS.

Where is INGRID HARSEM AS based?

INGRID HARSEM AS has its business address in Nøtterøy.

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.