BIZTRAC BETA
Development of building projects

SYNHAUG UTVIKLING AS

Org. no. 989629166 Limited company (AS) Vang Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −55,000
Equity NOK 2.6m
Incorporated 2006
Share capital NOK 1.4m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−55k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SYNHAUG UTVIKLING AS is registered as a limited company in Vang, Innlandet with organisation number 989629166. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2006. Registered share capital is NOK 1.4m, divided into 3900 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −55,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −55,000
Equity
NOK 2.6m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns SYNHAUG UTVIKLING AS?

TYIN FILEFJELL HOLDING AS
SYNHAUG UTVIKLING AS
NOK 0 rev. · NOK −55,000 profit

SYNHAUG UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYNHAUG UTVIKLING AS

Who owns SYNHAUG UTVIKLING AS?

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

What is the revenue of SYNHAUG UTVIKLING AS?

SYNHAUG UTVIKLING AS had revenue of NOK 0 in 2024.

Where is SYNHAUG UTVIKLING AS based?

SYNHAUG UTVIKLING AS has its business address in Tyinkrysset.

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.