BIZTRAC BETA
Site preparation

TONOVA AS

Org. no. 989278576 Limited company (AS) Lindesnes Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 558,000
Equity NOK 13.1m
Incorporated 2005
Share capital NOK 230,000

TONOVA AS is registered as a limited company in Lindesnes, Agder with organisation number 989278576. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2005. Registered share capital is NOK 230,000, divided into 230 shares. The company's stated purpose is: “Anleggsarbeid, kjøp, salg og utleie av maskiner, konsulentvirksomhet, eiendomsutvikling, anskaffelser og drift av eiendommer, investeringer i aksjer og andeler og andre finansobjekter, deltakelse i andre virksomheter samt alt hva som står i forbindelse med ovennevnte.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 558,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 558,000
Equity
NOK 13.1m
Est. value
NOK 7.3m

Financial health · 2024

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

Who owns TONOVA AS?

GERD TOVE NORUM
TONOVA AS
NOK 2.5m rev. · NOK 558,000 profit

TONOVA AS has 6 registered shareholders:

All shareholders and roles →

Which companies does TONOVA AS own?

TONOVA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TONOVA AS

Who owns TONOVA AS?

GERD TOVE NORUM is the largest registered owner, with 40.9%.

What is the revenue of TONOVA AS?

TONOVA AS had revenue of NOK 2.5m in 2024.

Who is the general manager of TONOVA AS?

John Osmund Norum is registered as general manager of TONOVA AS.

Where is TONOVA AS based?

TONOVA AS has its business address in Lindesnes.

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.