BIZTRAC BETA
COMPANY REGISTER PROFILE
923012044 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Computer programming activities

HUUBRO AS

Org. no. 923012044 Limited company (AS) Harstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −707,000
Equity NOK −342,000
Incorporated 2019
Share capital NOK 35,000

Signals

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

HUUBRO AS is registered as a limited company in Harstad, Troms with organisation number 923012044. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2019. Registered share capital is NOK 35,000, divided into 353 shares. The company's stated purpose is: “Utvikling av helseprogramvare og andre tjenester som naturlig tilhører dette. Herunder å delta i andre selskaper med lignende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −707,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▲ +21 %
Operating profit
NOK −707,000
▼ −159 %
Equity
NOK −342,000
▼ −202 %

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
-42.2%
Not satisfactory
Return on total assets
Solidity
-15.2%
Weak
Equity as a share of total capital

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

Who owns HUUBRO AS?

HUUBRO AS
NOK 2.7m rev. · NOK −707,000 profit

HUUBRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HUUBRO AS

Who owns HUUBRO AS?

HUUBRO HOLDING AS is the largest registered owner, with 85.0%.

What is the revenue of HUUBRO AS?

HUUBRO AS had revenue of NOK 2.7m in 2025.

Where is HUUBRO AS based?

HUUBRO AS has its business address in Harstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.