biztrac. BETA
COMPANY REGISTER PROFILE
930051683 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

SØRHEIM BYGG AS

Org. no. 930051683 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 22.2m
Operating profit NOK 2.5m
Equity NOK 2.0m
Incorporated 2022
Employees 13
Share capital NOK 30,000

SØRHEIM BYGG AS is registered as a limited company in Kristiansand, Agder with organisation number 930051683. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive byggmesterfirma, herunder delta i andre foretak som selskapsdeltaker eller aksjeeier.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.2m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 22.2m
▲ +8 %
Operating profit
NOK 2.5m
▲ +716 %
Equity
NOK 2.0m
▼ −3 %
Est. value
NOK 6.6m

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
46.8%
Very good
Return on total assets
Solidity
31.2%
Good
Equity as a share of total capital

Who owns SØRHEIM BYGG AS?

SØRHEIM BYGG AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRHEIM BYGG AS

Who owns SØRHEIM BYGG AS?

SØRHEIM EIERSELSKAP AS is the largest registered owner, with 73.5%.

What is the revenue of SØRHEIM BYGG AS?

SØRHEIM BYGG AS had revenue of NOK 22.2m in 2025.

Who is the general manager of SØRHEIM BYGG AS?

Jens-Kristian Karlsen is registered as general manager of SØRHEIM BYGG AS.

Where is SØRHEIM BYGG AS based?

SØRHEIM BYGG AS has its business address in Kristiansand S.

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.