BIZTRAC BETA
Rental and operating of own or leased real estate

TANGEN EIGEDOM AS

Org. no. 971181877 Limited company (AS) Sogndal Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 20.9m
Operating profit NOK 4.7m
Equity NOK 1.7m
Incorporated 1994
Share capital NOK 1.7m

TANGEN EIGEDOM AS is registered as a limited company in Sogndal, Vestland with organisation number 971181877. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1994. Registered share capital is NOK 1.7m. The company's stated purpose is: “Driva oppføring og drift av næringsbygg og det som høyrer inn under dette. Selskapet kan og delta som aksjonær, eller på anna måte ved investering i andre verksemder.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.9m in revenue and NOK 4.7m in operating profit.

Key figures · 2025

Revenue
NOK 20.9m
Operating profit
NOK 4.7m
Equity
NOK 1.7m
Est. value
NOK 12.5m

Financial health · 2025

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

Who owns TANGEN EIGEDOM AS?

TH EIGEDOM AS
TANGEN EIGEDOM AS
NOK 20.9m rev. · NOK 4.7m profit

TANGEN EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TANGEN EIGEDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about TANGEN EIGEDOM AS

Who owns TANGEN EIGEDOM AS?

TH EIGEDOM AS is the largest registered owner, with 100.0%.

What is the revenue of TANGEN EIGEDOM AS?

TANGEN EIGEDOM AS had revenue of NOK 20.9m in 2025.

Who is the general manager of TANGEN EIGEDOM AS?

Stian Hellebust is registered as general manager of TANGEN EIGEDOM AS.

Where is TANGEN EIGEDOM AS based?

TANGEN EIGEDOM AS has its business address in Kaupanger.

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.