biztrac. BETA
COMPANY REGISTER PROFILE
936048323 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

HOLSJØ AS

Org. no. 936048323 Limited company (AS) Tromsø Incorporated 2025 Active
Revenue 2025 NOK 466,000
Operating profit NOK −108,000
Equity NOK −84,000
Incorporated 2025
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−84k kr).

HOLSJØ AS is registered as a limited company in Tromsø, Troms with organisation number 936048323. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bygg & anlegg, eiendom og renovering.”. The most recent filed accounts, for the 2025 financial year, show NOK 466,000 in revenue and NOK −108,000 in operating profit.

Key figures · 2025

Revenue
NOK 466,000
Operating profit
NOK −108,000
Equity
NOK −84,000

Financial health · 2025

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

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

Who owns HOLSJØ AS?

HOLSJØ AS
NOK 466,000 rev. · NOK −108,000 profit

HOLSJØ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOLSJØ AS

Who owns HOLSJØ AS?

Henrik Holand is the largest registered owner, with 50.0%.

What is the revenue of HOLSJØ AS?

HOLSJØ AS had revenue of NOK 466,000 in 2025.

Who is the general manager of HOLSJØ AS?

Henrik Holand is registered as general manager of HOLSJØ AS.

Where is HOLSJØ AS based?

HOLSJØ AS has its business address in Tromsø.

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

Report a problem

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