BIZTRAC BETA
Dental practice care activities

ØGLÆND-NORHEIM AS

Org. no. 990696659 Limited company (AS) Sandnes Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 701,000
Operating profit NOK −2.2m
Equity NOK 35.4m
Incorporated 2006
Share capital NOK 100,000

Signals

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

ØGLÆND-NORHEIM AS is registered as a limited company in Sandnes, Rogaland with organisation number 990696659. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tannlegevirksomhet og tegnekontortjenester med naturlig tilhørende virksomhet. I tillegg til eie og forvalte eiendom samt delta i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 701,000 in revenue and NOK −2.2m in operating profit.

Key figures · 2024

Revenue
NOK 701,000
Operating profit
NOK −2.2m
Equity
NOK 35.4m
Est. value
NOK 47.0m

Financial health · 2024

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

Who owns ØGLÆND-NORHEIM AS?

STÅLE NORHEIM
ØGLÆND-NORHEIM AS
NOK 701,000 rev. · NOK −2.2m profit

ØGLÆND-NORHEIM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØGLÆND-NORHEIM AS

Who owns ØGLÆND-NORHEIM AS?

STÅLE NORHEIM is the largest registered owner, with 50.0%.

What is the revenue of ØGLÆND-NORHEIM AS?

ØGLÆND-NORHEIM AS had revenue of NOK 701,000 in 2024.

Who is the general manager of ØGLÆND-NORHEIM AS?

Lene Øglænd is registered as general manager of ØGLÆND-NORHEIM AS.

Where is ØGLÆND-NORHEIM AS based?

ØGLÆND-NORHEIM AS has its business address in Sandnes.

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.