BIZTRAC BETA
Activities of adventure companies

HIMMELBLÅ BRYGGE AS

Org. no. 920940307 Limited company (AS) Vega Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −261,000
Equity NOK −962,000
Incorporated 2018
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−962k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−261k kr).

HIMMELBLÅ BRYGGE AS is registered as a limited company in Vega, Nordland with organisation number 920940307. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tilbyder og arrangør av opplevelser, aktiviteter, overnatting, mat, arrangementer, havnetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −261,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −261,000
Equity
NOK −962,000

Financial health · 2025

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

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

Who owns HIMMELBLÅ BRYGGE AS?

HIMMELBLÅ UTVIKLING AS
HIMMELBLÅ BRYGGE AS
NOK 1.1m rev. · NOK −261,000 profit

HIMMELBLÅ BRYGGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HIMMELBLÅ BRYGGE AS

Who owns HIMMELBLÅ BRYGGE AS?

HIMMELBLÅ UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of HIMMELBLÅ BRYGGE AS?

HIMMELBLÅ BRYGGE AS had revenue of NOK 1.1m in 2025.

Where is HIMMELBLÅ BRYGGE AS based?

HIMMELBLÅ BRYGGE AS has its business address in Ylvingen.

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.