BIZTRAC BETA
Development of building projects

LAUVÅSEN EIENDOM AS

Org. no. 989049658 Limited company (AS) Sør-Fron Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 1.3m
Equity NOK 10.2m
Incorporated 2005
Share capital NOK 250,000

LAUVÅSEN EIENDOM AS is registered as a limited company in Sør-Fron, Innlandet with organisation number 989049658. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Investeringsvirksomhet, samt hva herved står i forbindelse, herunder delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 1.3m
Equity
NOK 10.2m
Est. value
NOK 10.7m

Financial health · 2024

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

Who owns LAUVÅSEN EIENDOM AS?

TORE STRAND
LAUVÅSEN EIENDOM AS
NOK 3.1m rev. · NOK 1.3m profit

LAUVÅSEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAUVÅSEN EIENDOM AS own?

LAUVÅSEN EIENDOM AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about LAUVÅSEN EIENDOM AS

Who owns LAUVÅSEN EIENDOM AS?

TORE STRAND is the largest registered owner, with 100.0%.

What is the revenue of LAUVÅSEN EIENDOM AS?

LAUVÅSEN EIENDOM AS had revenue of NOK 3.1m in 2024.

Who is the general manager of LAUVÅSEN EIENDOM AS?

Tore Strand is registered as general manager of LAUVÅSEN EIENDOM AS.

Where is LAUVÅSEN EIENDOM AS based?

LAUVÅSEN EIENDOM AS has its business address in Sør-Fron.

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.