BIZTRAC BETA
Construction of residential and non-residential buildings

JAR BYGG AS

Org. no. 998052327 Limited company (AS) Bærum Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 54.5m
Operating profit NOK 1.5m
Equity NOK 1.8m
Incorporated 2012
Employees 27
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-05 Adresseendring registrert 2026-02-05.

JAR BYGG AS is registered as a limited company in Bærum, Akershus with organisation number 998052327. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012 and has 27 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bygg og anleggsarbeider herunder snekkerarbeider.”. The most recent filed accounts, for the 2024 financial year, show NOK 54.5m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 54.5m
Operating profit
NOK 1.5m
Equity
NOK 1.8m
Est. value
NOK 6.0m

Financial health · 2024

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.5%
Weak
Equity as a share of total capital

Who owns JAR BYGG AS?

MARTIN MYKLEBUST
JAR BYGG AS
NOK 54.5m rev. · NOK 1.5m profit

JAR BYGG AS has 3 registered shareholders:

All shareholders and roles →

Which companies does JAR BYGG AS own?

JAR BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JAR BYGG AS

Who owns JAR BYGG AS?

MARTIN MYKLEBUST is the largest registered owner, with 60.0%.

What is the revenue of JAR BYGG AS?

JAR BYGG AS had revenue of NOK 54.5m in 2024.

Who is the general manager of JAR BYGG AS?

Martin Myklebust is registered as general manager of JAR BYGG AS.

Where is JAR BYGG AS based?

JAR BYGG AS has its business address in Bekkestua.

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.