BIZTRAC BETA
Construction of residential and non-residential buildings

KARLSØEN BYGG AS

Org. no. 995601214 Limited company (AS) Fredrikstad Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 9.0m
Operating profit NOK 645,000
Equity NOK 3.0m
Incorporated 2010
Share capital NOK 100,000

KARLSØEN BYGG AS is registered as a limited company in Fredrikstad, Østfold with organisation number 995601214. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Bygg- og snekkervirksomhet, oppføring og salg av boliger og forretningsbygg, samt kjøp, salg og forvaltning av fast eiendom herunder tomter for bebyggelse. Herunder å delta i andre selskap med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.0m in revenue and NOK 645,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.0m
Operating profit
NOK 645,000
Equity
NOK 3.0m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns KARLSØEN BYGG AS?

OLE ALEXANDER MØRCH KARLSØEN
KARLSØEN BYGG AS
NOK 9.0m rev. · NOK 645,000 profit

KARLSØEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KARLSØEN BYGG AS

Who owns KARLSØEN BYGG AS?

OLE ALEXANDER MØRCH KARLSØEN is the largest registered owner, with 100.0%.

What is the revenue of KARLSØEN BYGG AS?

KARLSØEN BYGG AS had revenue of NOK 9.0m in 2024.

Where is KARLSØEN BYGG AS based?

KARLSØEN BYGG AS has its business address in Engelsviken.

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.