BIZTRAC BETA
Uoppgitt

LORATO HOLDING AS

Org. no. 922381879 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −27,000
Equity NOK 21.4m
Incorporated 2018
Share capital NOK 140,000

Signals

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

LORATO HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922381879. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 140,000, divided into 100 shares. The company's stated purpose is: “Eie andeler i andre selskaper 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 −27,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −27,000
Equity
NOK 21.4m
Est. value
NOK 23.8m

Financial health · 2024

Liquidity
874.83
Very good
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 LORATO HOLDING AS?

LAILA ANNIE BROSE
LORATO HOLDING AS
NOK 0 rev. · NOK −27,000 profit

LORATO HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LORATO HOLDING AS own?

LORATO HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LORATO HOLDING AS

Who owns LORATO HOLDING AS?

LAILA ANNIE BROSE is the largest registered owner, with 50.0%.

What is the revenue of LORATO HOLDING AS?

LORATO HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of LORATO HOLDING AS?

Per Anton Sæther is registered as general manager of LORATO HOLDING AS.

Where is LORATO HOLDING AS based?

LORATO 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.