BIZTRAC BETA
Buying and selling of own real estate

LAUVSTAD INVEST AS

Org. no. 983361374 Limited company (AS) Seljord Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 8.4m
Operating profit NOK 5.1m
Equity NOK 9.2m
Incorporated 2001
Share capital NOK 127,000

LAUVSTAD INVEST AS is registered as a limited company in Seljord, Telemark with organisation number 983361374. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2001. Registered share capital is NOK 127,000, divided into 115 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av eiendom og aksjer samt annet som naturlig hører med under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.4m in revenue and NOK 5.1m in operating profit.

Key figures · 2025

Revenue
NOK 8.4m
Operating profit
NOK 5.1m
Equity
NOK 9.2m
Est. value
NOK 17.2m

Financial health · 2025

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.3%
Good
Equity as a share of total capital

Who owns LAUVSTAD INVEST AS?

GUNNAR LAUVSTAD
LAUVSTAD INVEST AS
NOK 8.4m rev. · NOK 5.1m profit

LAUVSTAD INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does LAUVSTAD INVEST AS own?

LAUVSTAD INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LAUVSTAD INVEST AS

Who owns LAUVSTAD INVEST AS?

GUNNAR LAUVSTAD is the largest registered owner, with 40.0%.

What is the revenue of LAUVSTAD INVEST AS?

LAUVSTAD INVEST AS had revenue of NOK 8.4m in 2025.

Who is the general manager of LAUVSTAD INVEST AS?

Gunnar Lauvstad is registered as general manager of LAUVSTAD INVEST AS.

Where is LAUVSTAD INVEST AS based?

LAUVSTAD INVEST AS has its business address in Seljord.

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.