BIZTRAC BETA
Civil engineering activities

OLAUSSEN INVEST & CONSULTING AS

Org. no. 924732954 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK 2,000
Incorporated 2020
Share capital NOK 60,000

Signals

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

OLAUSSEN INVEST & CONSULTING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 924732954. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 400 shares. The company's stated purpose is: “Prosjektadministrasjon, byggeledelse, rådgivning innenfor bygg og anlegg, eiendomsutvikling samt alt som naturlig står i forbindelse med dette, herunder investeringer og deltakelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −19,000
Equity
NOK 2,000
Est. value
NOK 3,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OLAUSSEN INVEST & CONSULTING AS?

RONNY OLAUSSEN
OLAUSSEN INVEST & CONSULTING AS
· NOK −19,000 profit

OLAUSSEN INVEST & CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLAUSSEN INVEST & CONSULTING AS own?

OLAUSSEN INVEST & CONSULTING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OLAUSSEN INVEST & CONSULTING AS

Who owns OLAUSSEN INVEST & CONSULTING AS?

RONNY OLAUSSEN is the largest registered owner, with 100.0%.

Where is OLAUSSEN INVEST & CONSULTING AS based?

OLAUSSEN INVEST & CONSULTING AS has its business address in Trondheim.

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.