BIZTRAC BETA
Development of building projects

HELGELAND BOLIG BYGG AS

Org. no. 985873526 Limited company (AS) Vefsn Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −81,000
Equity NOK 2.5m
Incorporated 2003
Share capital NOK 770,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−81k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HELGELAND BOLIG BYGG AS is registered as a limited company in Vefsn, Nordland with organisation number 985873526. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2003. Registered share capital is NOK 770,000, divided into 700 shares. The company's stated purpose is: “Kjøp og salg av tomter, eiendomsutvikling, salg av hus og alt som står i forbindelse med slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −81,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −81,000
Equity
NOK 2.5m
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
1.70
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.1%
Very good
Equity as a share of total capital

Who owns HELGELAND BOLIG BYGG AS?

SN GRUPPEN AS
HELGELAND BOLIG BYGG AS
NOK 0 rev. · NOK −81,000 profit

HELGELAND BOLIG BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELGELAND BOLIG BYGG AS

Who owns HELGELAND BOLIG BYGG AS?

SN GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of HELGELAND BOLIG BYGG AS?

HELGELAND BOLIG BYGG AS had revenue of NOK 0 in 2024.

Where is HELGELAND BOLIG BYGG AS based?

HELGELAND BOLIG BYGG AS has its business address in Mosjøen.

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.