BIZTRAC BETA
Development of building projects

TYLLDALEN EIENDOM OG UTVIKLING AS

Org. no. 921002858 Limited company (AS) Tynset Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 318,000
Operating profit NOK −503,000
Equity NOK 5.8m
Incorporated 2018
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−503k kr).

TYLLDALEN EIENDOM OG UTVIKLING AS is registered as a limited company in Tynset, Innlandet with organisation number 921002858. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 1.1m, divided into 2219 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 318,000 in revenue and NOK −503,000 in operating profit.

Key figures · 2025

Revenue
NOK 318,000
Operating profit
NOK −503,000
Equity
NOK 5.8m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns TYLLDALEN EIENDOM OG UTVIKLING AS?

HARALD HORTEN
TYLLDALEN EIENDOM OG UTVIKLING AS
NOK 318,000 rev. · NOK −503,000 profit

TYLLDALEN EIENDOM OG UTVIKLING AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about TYLLDALEN EIENDOM OG UTVIKLING AS

Who owns TYLLDALEN EIENDOM OG UTVIKLING AS?

HARALD HORTEN is the largest registered owner, with 3.6%.

What is the revenue of TYLLDALEN EIENDOM OG UTVIKLING AS?

TYLLDALEN EIENDOM OG UTVIKLING AS had revenue of NOK 318,000 in 2025.

Where is TYLLDALEN EIENDOM OG UTVIKLING AS based?

TYLLDALEN EIENDOM OG UTVIKLING AS has its business address in Tylldalen.

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.