BIZTRAC BETA
Rental and operating of own or leased real estate

SVEIN HAMMER EIENDOM AS

Org. no. 989729012 Limited company (AS) Tana Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 693,000
Equity NOK 1.0m
Incorporated 2006
Share capital NOK 300,000

SVEIN HAMMER EIENDOM AS is registered as a limited company in Tana, Finnmark with organisation number 989729012. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “I tillegg til å være et morselskap i konsern, eie fast eiendom med inventar og løsøre, aksjer og kjøretøy, samt forvaltning av disse eiendelene.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 693,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 693,000
Equity
NOK 1.0m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns SVEIN HAMMER EIENDOM AS?

TORBJØRN HAMMER
SVEIN HAMMER EIENDOM AS
NOK 2.1m rev. · NOK 693,000 profit

SVEIN HAMMER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SVEIN HAMMER EIENDOM AS own?

SVEIN HAMMER EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVEIN HAMMER EIENDOM AS

Who owns SVEIN HAMMER EIENDOM AS?

TORBJØRN HAMMER is the largest registered owner, with 100.0%.

What is the revenue of SVEIN HAMMER EIENDOM AS?

SVEIN HAMMER EIENDOM AS had revenue of NOK 2.1m in 2024.

Where is SVEIN HAMMER EIENDOM AS based?

SVEIN HAMMER EIENDOM AS has its business address in Tana.

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.