BIZTRAC BETA
Construction of residential and non-residential buildings

HA 1 BOLIG AS

Org. no. 932165074 Limited company (AS) Sør-Varanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 16.1m
Operating profit NOK 125,000
Equity NOK −88,000
Incorporated 2023
Employees 11
Share capital NOK 30,000

Signals

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

HA 1 BOLIG AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 932165074. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bygg og anleggsvirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.1m in revenue and NOK 125,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.1m
Operating profit
NOK 125,000
Equity
NOK −88,000
Est. value
NOK 844,000

Financial health · 2024

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

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

Who owns HA 1 BOLIG AS?

HA 1 INVEST AS
HA 1 BOLIG AS
NOK 16.1m rev. · NOK 125,000 profit

HA 1 BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HA 1 BOLIG AS er morselskap for 3 datterselskaper:

Frequently asked questions about HA 1 BOLIG AS

Who owns HA 1 BOLIG AS?

HA 1 INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of HA 1 BOLIG AS?

HA 1 BOLIG AS had revenue of NOK 16.1m in 2024.

Where is HA 1 BOLIG AS based?

HA 1 BOLIG AS has its business address in Hesseng.

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.