BIZTRAC BETA
Civil engineering activities

SVEINUNG LUNDE PROSJEKT AS

Org. no. 931186019 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 653,000
Equity NOK 78,000
Incorporated 2023
Share capital NOK 30,000

SVEINUNG LUNDE PROSJEKT AS is registered as a limited company in Stavanger, Rogaland with organisation number 931186019. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Prosjektadministrasjon, prosjektledelse, prosjektutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 653,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 653,000
Equity
NOK 78,000
Est. value
NOK 2.0m

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SVEINUNG LUNDE PROSJEKT AS?

SVEINUNG LUNDE
SVEINUNG LUNDE PROSJEKT AS
NOK 1.1m rev. · NOK 653,000 profit

SVEINUNG LUNDE PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVEINUNG LUNDE PROSJEKT AS

Who owns SVEINUNG LUNDE PROSJEKT AS?

SVEINUNG LUNDE is the largest registered owner, with 100.0%.

What is the revenue of SVEINUNG LUNDE PROSJEKT AS?

SVEINUNG LUNDE PROSJEKT AS had revenue of NOK 1.1m in 2025.

Who is the general manager of SVEINUNG LUNDE PROSJEKT AS?

Sveinung Lunde is registered as general manager of SVEINUNG LUNDE PROSJEKT AS.

Where is SVEINUNG LUNDE PROSJEKT AS based?

SVEINUNG LUNDE PROSJEKT AS has its business address in Hundvåg.

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.