BIZTRAC BETA
Uoppgitt

LILL ODDLAUG HOLDING AS

Org. no. 933331016 Limited company (AS) Tromsø Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 29.9m
Incorporated 2023
Share capital NOK 30,000

Signals

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

LILL ODDLAUG HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 933331016. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper og øvrige finansielle investeringer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 29.9m
Est. value
NOK 15.8m

Financial health · 2024

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

Who owns LILL ODDLAUG HOLDING AS?

LILL ODDLAUG HANSEN
LILL ODDLAUG HOLDING AS
NOK 0 rev. · NOK −6,000 profit

LILL ODDLAUG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LILL ODDLAUG HOLDING AS own?

LILL ODDLAUG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LILL ODDLAUG HOLDING AS

Who owns LILL ODDLAUG HOLDING AS?

LILL ODDLAUG HANSEN is the largest registered owner, with 100.0%.

What is the revenue of LILL ODDLAUG HOLDING AS?

LILL ODDLAUG HOLDING AS had revenue of NOK 0 in 2024.

Where is LILL ODDLAUG HOLDING AS based?

LILL ODDLAUG HOLDING AS has its business address in Tomasjord.

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.