BIZTRAC BETA
Construction of residential and non-residential buildings

SK BAKKEN BYGG AS

Org. no. 985416044 Limited company (AS) Ringsaker Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK −138,000
Equity NOK 3.1m
Incorporated 2003
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−138k kr).
  • Nylig endring 2026-07-15 Avregistrert registrert 2026-07-15.

SK BAKKEN BYGG AS is registered as a limited company in Ringsaker, Innlandet with organisation number 985416044. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenør innen bygg og anlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK −138,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK −138,000
Equity
NOK 3.1m
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
0.67
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
68.8%
Very good
Equity as a share of total capital

Who owns SK BAKKEN BYGG AS?

SVEIN KÅRE BAKKEN
SK BAKKEN BYGG AS
NOK 2.8m rev. · NOK −138,000 profit

SK BAKKEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SK BAKKEN BYGG AS own?

SK BAKKEN BYGG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SK BAKKEN BYGG AS

Who owns SK BAKKEN BYGG AS?

SVEIN KÅRE BAKKEN is the largest registered owner, with 100.0%.

What is the revenue of SK BAKKEN BYGG AS?

SK BAKKEN BYGG AS had revenue of NOK 2.8m in 2025.

Where is SK BAKKEN BYGG AS based?

SK BAKKEN BYGG AS has its business address in Moelv.

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.