BIZTRAC BETA
Civil engineering activities

SIV ING BRAATHEN-SØMME AS

Org. no. 913316576 Limited company (AS) Drammen Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 5.2m
Operating profit NOK 816,000
Equity NOK 38,000
Incorporated 2014
Share capital NOK 30,000

SIV ING BRAATHEN-SØMME AS is registered as a limited company in Drammen, Buskerud with organisation number 913316576. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rådgivende ingeniør, samt deltagelse i andre selskaper og konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK 816,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
Operating profit
NOK 816,000
Equity
NOK 38,000
Est. value
NOK 4.0m

Financial health · 2025

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

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

Who owns SIV ING BRAATHEN-SØMME AS?

CBSL HOLDING AS
SIV ING BRAATHEN-SØMME AS
NOK 5.2m rev. · NOK 816,000 profit

SIV ING BRAATHEN-SØMME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIV ING BRAATHEN-SØMME AS

Who owns SIV ING BRAATHEN-SØMME AS?

CBSL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SIV ING BRAATHEN-SØMME AS?

SIV ING BRAATHEN-SØMME AS had revenue of NOK 5.2m in 2025.

Who is the general manager of SIV ING BRAATHEN-SØMME AS?

Christian Braathen-Sømme is registered as general manager of SIV ING BRAATHEN-SØMME AS.

Where is SIV ING BRAATHEN-SØMME AS based?

SIV ING BRAATHEN-SØMME AS has its business address in Drammen.

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.