BIZTRAC BETA
Rental and operating of own or leased real estate

SANGERHEIMEN AS

Org. no. 933412725 Limited company (AS) Notodden Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 136,000
Operating profit NOK −55,000
Equity NOK −436,000
Incorporated 2024
Share capital NOK 31,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−436k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−55k kr).

SANGERHEIMEN AS is registered as a limited company in Notodden, Telemark with organisation number 933412725. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 31,000, divided into 30800 shares. The company's stated purpose is: “Eie, utvikle og leie ut eiendom, samt arrangere selskaper og eventer i tillegg til cateringvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 136,000 in revenue and NOK −55,000 in operating profit.

Key figures · 2025

Revenue
NOK 136,000
Operating profit
NOK −55,000
Equity
NOK −436,000

Financial health · 2025

Liquidity
3.94
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-22.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SANGERHEIMEN AS?

TOM PETTER EKORNES KIVLE
SANGERHEIMEN AS
NOK 136,000 rev. · NOK −55,000 profit

SANGERHEIMEN AS has 20 registered shareholders:

All shareholders and roles →

Frequently asked questions about SANGERHEIMEN AS

Who owns SANGERHEIMEN AS?

TOM PETTER EKORNES KIVLE is the largest registered owner, with 5.0%.

What is the revenue of SANGERHEIMEN AS?

SANGERHEIMEN AS had revenue of NOK 136,000 in 2025.

Where is SANGERHEIMEN AS based?

SANGERHEIMEN AS has its business address in Notodden.

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.