BIZTRAC BETA
Rental and operating of own or leased real estate

LAOS HOLDING AS

Org. no. 929639049 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −17,000
Equity NOK 2.2m
Incorporated 2022
Share capital NOK 630,000

Signals

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

LAOS HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929639049. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 630,000, divided into 3000 shares. The company's stated purpose is: “Deltakelse i andre selskaper, samt eiendomsforvaltning for drift av næringsvirksomhet og kjøp og salg av eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 2.2m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns LAOS HOLDING AS?

KROGS SNEKKERVERKSTED AS
LAOS HOLDING AS
NOK 0 rev. · NOK −17,000 profit

LAOS HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LAOS HOLDING AS own?

LAOS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LAOS HOLDING AS

Who owns LAOS HOLDING AS?

KROGS SNEKKERVERKSTED AS is the largest registered owner, with 33.3%.

What is the revenue of LAOS HOLDING AS?

LAOS HOLDING AS had revenue of NOK 0 in 2024.

Where is LAOS HOLDING AS based?

LAOS HOLDING 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.