BIZTRAC BETA
Joinery installation

BJUNE BLÅS & BYGG AS

Org. no. 926438603 Limited company (AS) Horten Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK −812,000
Equity NOK −1.9m
Incorporated 2021
Employees 6
Share capital NOK 704,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−812k kr).

BJUNE BLÅS & BYGG AS is registered as a limited company in Horten, Vestfold with organisation number 926438603. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 704,000, divided into 400 shares. The company's stated purpose is: “Innblåsing av isolasjon i gamle og nye boliger. Tømrer tjenester relatert til nye og gamle bygg.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK −812,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK −812,000
Equity
NOK −1.9m

Financial health · 2024

Liquidity
0.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-261.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BJUNE BLÅS & BYGG AS?

Dag Einar Bjune
BJUNE BLÅS & BYGG AS
NOK 4.3m rev. · NOK −812,000 profit

BJUNE BLÅS & BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJUNE BLÅS & BYGG AS

Who owns BJUNE BLÅS & BYGG AS?

Dag Einar Bjune is the largest registered owner, with 100.0%.

What is the revenue of BJUNE BLÅS & BYGG AS?

BJUNE BLÅS & BYGG AS had revenue of NOK 4.3m in 2024.

Where is BJUNE BLÅS & BYGG AS based?

BJUNE BLÅS & BYGG AS has its business address in Åsgårdstrand.

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.