BIZTRAC BETA
Uoppgitt

BIRKELUND & SOMMERSTAD AS

Org. no. 977514118 Limited company (AS) Sandefjord Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 312,000
Equity NOK 621,000
Incorporated 1997
Share capital NOK 100,000

BIRKELUND & SOMMERSTAD AS is registered as a limited company in Sandefjord, Vestfold with organisation number 977514118. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Drive investering i aksjer i andre selskaper samt hva som hermed står i forbindelse. Selskapet skal også tilby konsulenttjeneste og andre tjenester knyttet til bygg og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 312,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 312,000
Equity
NOK 621,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns BIRKELUND & SOMMERSTAD AS?

TERJE BIRKELUND
BIRKELUND & SOMMERSTAD AS
NOK 1.5m rev. · NOK 312,000 profit

BIRKELUND & SOMMERSTAD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIRKELUND & SOMMERSTAD AS

Who owns BIRKELUND & SOMMERSTAD AS?

TERJE BIRKELUND is the largest registered owner, with 50.0%.

What is the revenue of BIRKELUND & SOMMERSTAD AS?

BIRKELUND & SOMMERSTAD AS had revenue of NOK 1.5m in 2024.

Who is the general manager of BIRKELUND & SOMMERSTAD AS?

Bjarne Sommerstad is registered as general manager of BIRKELUND & SOMMERSTAD AS.

Where is BIRKELUND & SOMMERSTAD AS based?

BIRKELUND & SOMMERSTAD AS has its business address in Stokke.

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.