BIZTRAC BETA
Development of building projects

TROLLTJERNSTULEN UTVIKLING AS

Org. no. 918505652 Limited company (AS) Nore Og Uvdal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 53,000
Equity NOK 7.6m
Incorporated 2016
Share capital NOK 250,000

TROLLTJERNSTULEN UTVIKLING AS is registered as a limited company in Nore Og Uvdal, Buskerud with organisation number 918505652. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 250,000, divided into 400 shares. The company's stated purpose is: “Fremtidsrettet reiselivsutvikling i Uvdal. Selskapet kan delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 53,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 53,000
Equity
NOK 7.6m
Est. value
NOK 5.4m

Financial health · 2025

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

Who owns TROLLTJERNSTULEN UTVIKLING AS?

KVETA EIENDOM AS
TROLLTJERNSTULEN UTVIKLING AS
NOK 4.4m rev. · NOK 53,000 profit

TROLLTJERNSTULEN UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TROLLTJERNSTULEN UTVIKLING AS own?

TROLLTJERNSTULEN UTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TROLLTJERNSTULEN UTVIKLING AS

Who owns TROLLTJERNSTULEN UTVIKLING AS?

KVETA EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of TROLLTJERNSTULEN UTVIKLING AS?

TROLLTJERNSTULEN UTVIKLING AS had revenue of NOK 4.4m in 2025.

Where is TROLLTJERNSTULEN UTVIKLING AS based?

TROLLTJERNSTULEN UTVIKLING AS has its business address in Uvdal.

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.