BIZTRAC BETA
Refrigeration installation, heat pump installation and installation of fireplaces

SAK-CON AS

Org. no. 929611047 Limited company (AS) Vevelstad Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 215,000
Equity NOK 120,000
Incorporated 2022
Share capital NOK 30,000

SAK-CON AS is registered as a limited company in Vevelstad, Nordland with organisation number 929611047. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen ingeniørtjenester, byggesakstjenester, taksering og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 215,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 215,000
Equity
NOK 120,000
Est. value
NOK 661,000

Financial health · 2025

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

Who owns SAK-CON AS?

BJØRN KARSTEIN SKAR
SAK-CON AS
NOK 1.3m rev. · NOK 215,000 profit

SAK-CON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAK-CON AS

Who owns SAK-CON AS?

BJØRN KARSTEIN SKAR is the largest registered owner, with 100.0%.

What is the revenue of SAK-CON AS?

SAK-CON AS had revenue of NOK 1.3m in 2025.

Who is the general manager of SAK-CON AS?

Bjørn Karstein Skar is registered as general manager of SAK-CON AS.

Where is SAK-CON AS based?

SAK-CON AS has its business address in Vevelstad.

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.