BIZTRAC BETA
Manufacture of doors and windows of wood

N.TVEIT HOLDING AS

Org. no. 928471209 Limited company (AS) Åseral Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK 154,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

N.TVEIT HOLDING AS is registered as a limited company in Åseral, Agder with organisation number 928471209. The business is classified under manufacture of doors and windows of wood (NACE 16.250). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Holdingselskap for eie og forvaltning av underliggende selskap. Selskapet kan også foreta finansielle investeringer i aksjer og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 154,000
Est. value
NOK 742,000

Financial health · 2024

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

Who owns N.TVEIT HOLDING AS?

NORUNN TVEIT
N.TVEIT HOLDING AS
NOK 0 rev. · NOK −9,000 profit

N.TVEIT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does N.TVEIT HOLDING AS own?

N.TVEIT HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about N.TVEIT HOLDING AS

Who owns N.TVEIT HOLDING AS?

NORUNN TVEIT is the largest registered owner, with 100.0%.

What is the revenue of N.TVEIT HOLDING AS?

N.TVEIT HOLDING AS had revenue of NOK 0 in 2024.

Where is N.TVEIT HOLDING AS based?

N.TVEIT HOLDING AS has its business address in Fossdal.

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.