BIZTRAC BETA
Construction of residential and non-residential buildings

TOVDAL FJELLHYTTER AS

Org. no. 998040973 Limited company (AS) Åmli Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 269,000
Operating profit NOK 73,000
Equity NOK 669,000
Incorporated 2012
Share capital NOK 30,000

TOVDAL FJELLHYTTER AS is registered as a limited company in Åmli, Agder with organisation number 998040973. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av hytter mv. I tillegg alt hva styret måtte finne formålstjenlig, herunder kjøp og salg av eiendeler, aksjer, mv. i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 269,000 in revenue and NOK 73,000 in operating profit.

Key figures · 2024

Revenue
NOK 269,000
Operating profit
NOK 73,000
Equity
NOK 669,000
Est. value
NOK 537,000

Financial health · 2024

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

Who owns TOVDAL FJELLHYTTER AS?

TERJE RAMSE
TOVDAL FJELLHYTTER AS
NOK 269,000 rev. · NOK 73,000 profit

TOVDAL FJELLHYTTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOVDAL FJELLHYTTER AS

Who owns TOVDAL FJELLHYTTER AS?

TERJE RAMSE is the largest registered owner, with 100.0%.

What is the revenue of TOVDAL FJELLHYTTER AS?

TOVDAL FJELLHYTTER AS had revenue of NOK 269,000 in 2024.

Who is the general manager of TOVDAL FJELLHYTTER AS?

Terje Ramse is registered as general manager of TOVDAL FJELLHYTTER AS.

Where is TOVDAL FJELLHYTTER AS based?

TOVDAL FJELLHYTTER AS has its business address in Dølemo.

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.