BIZTRAC BETA
Joinery installation

BYGGEPARTNER AS

Org. no. 914100623 Limited company (AS) Engerdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 9.3m
Operating profit NOK 363,000
Equity NOK 2.3m
Incorporated 2014
Employees 10
Share capital NOK 30,000

BYGGEPARTNER AS is registered as a limited company in Engerdal, Innlandet with organisation number 914100623. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2014 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Snekkervirksomhet og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.3m in revenue and NOK 363,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.3m
Operating profit
NOK 363,000
Equity
NOK 2.3m
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns BYGGEPARTNER AS?

PER MORTEN JAKOBSSON SJØVOLD
BYGGEPARTNER AS
NOK 9.3m rev. · NOK 363,000 profit

BYGGEPARTNER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGGEPARTNER AS

Who owns BYGGEPARTNER AS?

PER MORTEN JAKOBSSON SJØVOLD is the largest registered owner, with 50.0%.

What is the revenue of BYGGEPARTNER AS?

BYGGEPARTNER AS had revenue of NOK 9.3m in 2024.

Who is the general manager of BYGGEPARTNER AS?

Kjetil Skogheim is registered as general manager of BYGGEPARTNER AS.

Where is BYGGEPARTNER AS based?

BYGGEPARTNER AS has its business address in Engerdal.

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.