BIZTRAC BETA
Rental and operating of own or leased real estate

LADEHAMMEREN AS

Org. no. 828129392 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 288,000
Operating profit NOK −1.2m
Equity NOK 177.3m
Incorporated 2021
Share capital NOK 435,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,2 mill kr).

LADEHAMMEREN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 828129392. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 435,000, divided into 3000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 288,000 in revenue and NOK −1.2m in operating profit.

Key figures · 2025

Revenue
NOK 288,000
Operating profit
NOK −1.2m
Equity
NOK 177.3m
Est. value
NOK 161.8m

Financial health · 2025

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

Who owns LADEHAMMEREN AS?

HEIMDAL BOLIG AS
LADEHAMMEREN AS
NOK 288,000 rev. · NOK −1.2m profit

LADEHAMMEREN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LADEHAMMEREN AS

Who owns LADEHAMMEREN AS?

HEIMDAL BOLIG AS is the largest registered owner, with 33.3%.

What is the revenue of LADEHAMMEREN AS?

LADEHAMMEREN AS had revenue of NOK 288,000 in 2025.

Who is the general manager of LADEHAMMEREN AS?

Geir Harald Halmøy is registered as general manager of LADEHAMMEREN AS.

Where is LADEHAMMEREN AS based?

LADEHAMMEREN AS has its business address in Trondheim.

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.