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

SANNUM EIENDOM AS

Org. no. 987015888 Limited company (AS) Trondheim Incorporated 2004 Active
Revenue 2025 NOK 1.3m
Operating profit NOK 629,000
Equity NOK 8.8m
Incorporated 2004
Share capital NOK 100,000

SANNUM EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 987015888. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift og utleie av fast eiendom og dertil hørende virksomeht, samt deltakelse som eier i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 629,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▲ +2 %
Operating profit
NOK 629,000
▲ +17 %
Equity
NOK 8.8m
▼ −2 %
Est. value
NOK 7.7m

Financial health · 2025

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

Who owns SANNUM EIENDOM AS?

SANNUM EIENDOM AS
NOK 1.3m rev. · NOK 629,000 profit

SANNUM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANNUM EIENDOM AS

Who owns SANNUM EIENDOM AS?

SANNUM HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SANNUM EIENDOM AS?

SANNUM EIENDOM AS had revenue of NOK 1.3m in 2025.

Who is the general manager of SANNUM EIENDOM AS?

Rune Sannum is registered as general manager of SANNUM EIENDOM AS.

Where is SANNUM EIENDOM AS based?

SANNUM EIENDOM 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.