BIZTRAC BETA
Buying and selling of own real estate

LUND FORVALTNING AS

Org. no. 990189234 Limited company (AS) Trondheim Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 12.3m
Operating profit NOK 2.3m
Equity NOK 162.0m
Incorporated 2006
Share capital NOK 200,000

LUND FORVALTNING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 990189234. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2006. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Erverve, eie og forvalte aksjer, eiendom og virksomhet forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.3m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 12.3m
Operating profit
NOK 2.3m
Equity
NOK 162.0m
Est. value
NOK 123.9m

Financial health · 2024

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

Who owns LUND FORVALTNING AS?

KARL MARTIN LUND
LUND FORVALTNING AS
NOK 12.3m rev. · NOK 2.3m profit

LUND FORVALTNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUND FORVALTNING AS own?

LUND FORVALTNING AS holds stakes in 14 companies:

See the full ownership structure →

Frequently asked questions about LUND FORVALTNING AS

Who owns LUND FORVALTNING AS?

KARL MARTIN LUND is the largest registered owner, with 100.0%.

What is the revenue of LUND FORVALTNING AS?

LUND FORVALTNING AS had revenue of NOK 12.3m in 2024.

Who is the general manager of LUND FORVALTNING AS?

Karl Martin Lund is registered as general manager of LUND FORVALTNING AS.

Where is LUND FORVALTNING AS based?

LUND FORVALTNING 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.