biztrac. BETA
COMPANY REGISTER PROFILE
992887761 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HANESETH HARSTAD EIENDOM AS

Org. no. 992887761 Limited company (AS) Bodø Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −67,000
Equity NOK 821,000
Incorporated 2008
Share capital NOK 800,000

Signals

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

HANESETH HARSTAD EIENDOM AS is registered as a limited company in Bodø, Nordland with organisation number 992887761. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 800,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av eiendommer, herunder drift og utleie av eiendommer, og det som naturlig hører her under. Videre kan selskapet investere i andre selskaper med relatert virksomhet.”.

Key figures · 2025

Operating profit
NOK −67,000
▼ −103 %
Equity
NOK 821,000
▼ −76 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
2.93
Very good
Current assets ÷ current liabilities
Profitability
-0.9%
Not satisfactory
Return on total assets
Solidity
65.8%
Very good
Equity as a share of total capital

Who owns HANESETH HARSTAD EIENDOM AS?

HANESETH HARSTAD EIENDOM AS
· NOK −67,000 profit

HANESETH HARSTAD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HANESETH HARSTAD EIENDOM AS

Who owns HANESETH HARSTAD EIENDOM AS?

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

Where is HANESETH HARSTAD EIENDOM AS based?

HANESETH HARSTAD EIENDOM AS has its business address in Bodø.

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.