BIZTRAC BETA
Rental and operating of own or leased real estate

LADEVEIEN HOLDING AS

Org. no. 812299212 Limited company (AS) Trondheim Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 13.5m
Incorporated 2013
Share capital NOK 8.1m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LADEVEIEN HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 812299212. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 8.1m, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og eiendom samt det som naturlig står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −21,000
Equity
NOK 13.5m
Est. value
NOK 15.7m

Financial health · 2024

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.4%
Satisfactory
Equity as a share of total capital

Who owns LADEVEIEN HOLDING AS?

RYDNING HOLDING AS
LADEVEIEN HOLDING AS
· NOK −21,000 profit

LADEVEIEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LADEVEIEN HOLDING AS own?

LADEVEIEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LADEVEIEN HOLDING AS

Who owns LADEVEIEN HOLDING AS?

RYDNING HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of LADEVEIEN HOLDING AS?

Maria Rydning is registered as general manager of LADEVEIEN HOLDING AS.

Where is LADEVEIEN HOLDING AS based?

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