BIZTRAC BETA
Buying and selling of own real estate

OTIUMPLUSS LYNGEN OMSORG AS

Org. no. 932976366 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −74,000
Equity NOK 130,000
Incorporated 2024
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−74k kr).

OTIUMPLUSS LYNGEN OMSORG AS is registered as a limited company in Oslo, Oslo with organisation number 932976366. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Investering, utvikling, bygging og salg av fast eiendom, direkte eller indirekte, samt det som naturlig står iforbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −74,000
Equity
NOK 130,000
Est. value
NOK 119,000

Financial health · 2024

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

Who owns OTIUMPLUSS LYNGEN OMSORG AS?

ALLSTAD EIENDOMSUTVIKLING AS
OTIUMPLUSS LYNGEN OMSORG AS
· NOK −74,000 profit

OTIUMPLUSS LYNGEN OMSORG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OTIUMPLUSS LYNGEN OMSORG AS own?

OTIUMPLUSS LYNGEN OMSORG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OTIUMPLUSS LYNGEN OMSORG AS

Who owns OTIUMPLUSS LYNGEN OMSORG AS?

ALLSTAD EIENDOMSUTVIKLING AS is the largest registered owner, with 50.0%.

Who is the general manager of OTIUMPLUSS LYNGEN OMSORG AS?

Ragnhild Raaum Wettestad is registered as general manager of OTIUMPLUSS LYNGEN OMSORG AS.

Where is OTIUMPLUSS LYNGEN OMSORG AS based?

OTIUMPLUSS LYNGEN OMSORG AS has its business address in Oslo.

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.