biztrac. BETA
COMPANY REGISTER PROFILE
994164503 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

CARSTEN SØREIDE CONSULTING DA

Org. no. 994164503 General partnership with shared liability (DA) Bergen Incorporated 2009 Active
Revenue 2025 NOK 50,000
Operating profit NOK 50,000
Equity NOK 163,000
Incorporated 2009

CARSTEN SØREIDE CONSULTING DA is registered as a general partnership with shared liability in Bergen, Vestland with organisation number 994164503. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2009. The company's stated purpose is: “Økonomisk rådgivning og management. Selskapet kan også eie andeler og aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 50,000 in revenue and NOK 50,000 in operating profit.

Key figures · 2025

Revenue
NOK 50,000
Operating profit
NOK 50,000
▲ +1 %
Equity
NOK 163,000
▲ +58 %
Est. value
NOK 238,000

Financial health · 2025

Liquidity
2.08
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
10.4%
Satisfactory
Equity as a share of total capital

Who owns CARSTEN SØREIDE CONSULTING DA?

No shareholders are registered for CARSTEN SØREIDE CONSULTING DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does CARSTEN SØREIDE CONSULTING DA own?

CARSTEN SØREIDE CONSULTING DA holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CARSTEN SØREIDE CONSULTING DA

What is the revenue of CARSTEN SØREIDE CONSULTING DA?

CARSTEN SØREIDE CONSULTING DA had revenue of NOK 50,000 in 2025.

Where is CARSTEN SØREIDE CONSULTING DA based?

CARSTEN SØREIDE CONSULTING DA has its business address in Rådal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.