biztrac. BETA
COMPANY REGISTER PROFILE
984802692 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

HAMMERN EIENDOM AS

Org. no. 984802692 Limited company (AS) Bodø Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −599,000
Equity NOK 16.4m
Incorporated 2002
Share capital NOK 2.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−599k kr).
  • Nylig endring 2026-09-18 Adresseendring registrert 2026-09-18.

HAMMERN EIENDOM AS is registered as a limited company in Bodø, Nordland with organisation number 984802692. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2002. Registered share capital is NOK 2.0m, divided into 2040 shares. The company's stated purpose is: “Erverv, eie og utvikle fast eiendom og annen forretningsmessig virksomhet. Selskapet har også til formål å investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −599,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
▼ −80 %
Operating profit
NOK −599,000
▼ −175 %
Equity
NOK 16.4m
▼ −8 %
Est. value
NOK 12.5m

Financial health · 2025

Liquidity
10.58
Very good
Current assets ÷ current liabilities
Profitability
-1.8%
Not satisfactory
Return on total assets
Solidity
51.0%
Very good
Equity as a share of total capital

Who owns HAMMERN EIENDOM AS?

HAMMERN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAMMERN EIENDOM AS

Who owns HAMMERN EIENDOM AS?

JMB INVEST AS is the largest registered owner, with 65.0%.

What is the revenue of HAMMERN EIENDOM AS?

HAMMERN EIENDOM AS had revenue of NOK 2.5m in 2025.

Where is HAMMERN EIENDOM AS based?

HAMMERN 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.