BIZTRAC BETA
Construction of residential and non-residential buildings

TØMRER JONNY HOVDAL AS

Org. no. 918009485 Limited company (AS) Frosta Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 161,000
Equity NOK 375,000
Incorporated 2016
Share capital NOK 50,000

TØMRER JONNY HOVDAL AS is registered as a limited company in Frosta, Trøndelag with organisation number 918009485. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Tømrervirksomhet og alt hva dermed står i forbindelse med dette, og aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 161,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 161,000
Equity
NOK 375,000
Est. value
NOK 605,000

Financial health · 2024

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.3%
Good
Equity as a share of total capital

Who owns TØMRER JONNY HOVDAL AS?

JONNY HOVDAL
TØMRER JONNY HOVDAL AS
NOK 4.9m rev. · NOK 161,000 profit

TØMRER JONNY HOVDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØMRER JONNY HOVDAL AS

Who owns TØMRER JONNY HOVDAL AS?

JONNY HOVDAL is the largest registered owner, with 100.0%.

What is the revenue of TØMRER JONNY HOVDAL AS?

TØMRER JONNY HOVDAL AS had revenue of NOK 4.9m in 2024.

Who is the general manager of TØMRER JONNY HOVDAL AS?

Jonny Hovdal is registered as general manager of TØMRER JONNY HOVDAL AS.

Where is TØMRER JONNY HOVDAL AS based?

TØMRER JONNY HOVDAL AS has its business address in Frosta.

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.