BIZTRAC BETA
Refrigeration installation, heat pump installation and installation of fireplaces

BLUEFRONT IV TOPCO AS

Org. no. 929361083 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −46,000
Equity NOK 48.4m
Incorporated 2022
Share capital NOK 39,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-08 Aksjekapital registrert 2026-06-08.

BLUEFRONT IV TOPCO AS is registered as a limited company in Oslo, Oslo with organisation number 929361083. The business is classified under refrigeration installation, heat pump installation and installation of fireplaces (NACE 43.222). The company was incorporated in 2022. Registered share capital is NOK 39,000, divided into 30000 shares. The company's stated purpose is: “Å investere i, eie og utvikle andre selskaper og alt som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −46,000
Equity
NOK 48.4m
Est. value
NOK 49.6m

Financial health · 2024

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

Who owns BLUEFRONT IV TOPCO AS?

BLUEFRONT CAPITAL I AS
BLUEFRONT IV TOPCO AS
· NOK −46,000 profit

BLUEFRONT IV TOPCO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLUEFRONT IV TOPCO AS own?

BLUEFRONT IV TOPCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLUEFRONT IV TOPCO AS

Who owns BLUEFRONT IV TOPCO AS?

BLUEFRONT CAPITAL I AS is the largest registered owner, with 100.0%.

Where is BLUEFRONT IV TOPCO AS based?

BLUEFRONT IV TOPCO AS has its business address in Oslo.

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.