BIZTRAC BETA
Construction of residential and non-residential buildings

VEBJØRN STRØMSNES AS

Org. no. 991429689 Limited company (AS) Sande Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK 556,000
Equity NOK 1.4m
Incorporated 2007
Employees 9
Share capital NOK 1.0m

VEBJØRN STRØMSNES AS is registered as a limited company in Sande, Møre og Romsdal with organisation number 991429689. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2007 and has 9 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Byggevirksomhet, snekring, salg av varer relatert til slik virksomhet, investere i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK 556,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK 556,000
Equity
NOK 1.4m
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns VEBJØRN STRØMSNES AS?

VEBJØRN STRØMSNES
VEBJØRN STRØMSNES AS
NOK 6.6m rev. · NOK 556,000 profit

VEBJØRN STRØMSNES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEBJØRN STRØMSNES AS

Who owns VEBJØRN STRØMSNES AS?

VEBJØRN STRØMSNES is the largest registered owner, with 75.0%.

What is the revenue of VEBJØRN STRØMSNES AS?

VEBJØRN STRØMSNES AS had revenue of NOK 6.6m in 2024.

Who is the general manager of VEBJØRN STRØMSNES AS?

Vebjørn Strømsnes is registered as general manager of VEBJØRN STRØMSNES AS.

Where is VEBJØRN STRØMSNES AS based?

VEBJØRN STRØMSNES AS has its business address in Sandshamn.

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.