BIZTRAC BETA
Construction of residential and non-residential buildings

SYSTEMBYGG1 AS

Org. no. 926861182 Limited company (AS) Indre Østfold Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 38.9m
Operating profit NOK 3.2m
Equity NOK 4.1m
Incorporated 2021
Employees 20
Share capital NOK 100,000

SYSTEMBYGG1 AS is registered as a limited company in Indre Østfold, Østfold with organisation number 926861182. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021 and has 20 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Tømrerarbeider og håndverkstjenester, samt arbeid knyttet til rehabilitering og støydemping av næringslokaler, kjøp og salg av produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 38.9m in revenue and NOK 3.2m in operating profit.

Key figures · 2025

Revenue
NOK 38.9m
Operating profit
NOK 3.2m
Equity
NOK 4.1m
Est. value
NOK 12.5m

Financial health · 2025

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.9%
Good
Equity as a share of total capital

Who owns SYSTEMBYGG1 AS?

HHH HOLDING AS
SYSTEMBYGG1 AS
NOK 38.9m rev. · NOK 3.2m profit

SYSTEMBYGG1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYSTEMBYGG1 AS

Who owns SYSTEMBYGG1 AS?

HHH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SYSTEMBYGG1 AS?

SYSTEMBYGG1 AS had revenue of NOK 38.9m in 2025.

Who is the general manager of SYSTEMBYGG1 AS?

Per Håkon Jacobsen is registered as general manager of SYSTEMBYGG1 AS.

Where is SYSTEMBYGG1 AS based?

SYSTEMBYGG1 AS has its business address in Mysen.

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.