BIZTRAC BETA
Rental and operating of own or leased real estate

TOPP HOLDING AS

Org. no. 997420179 Limited company (AS) Lyngen Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 7.0m
Equity NOK 17.0m
Incorporated 2011
Share capital NOK 528,000

TOPP HOLDING AS is registered as a limited company in Lyngen, Troms with organisation number 997420179. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 528,000, divided into 1200 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom og maskiner/utstyr. Selskapet skal også kunne investere i bedrifter, industriprosjekter og andre investeringsprosjekter som styret måtte finne det formålstjenlig at bedrifter deltar i.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 7.0m in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 7.0m
Equity
NOK 17.0m
Est. value
NOK 26.1m

Financial health · 2024

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

Who owns TOPP HOLDING AS?

RAUTUVAARA INVEST AS
TOPP HOLDING AS
NOK 10.1m rev. · NOK 7.0m profit

TOPP HOLDING AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOPP HOLDING AS

Who owns TOPP HOLDING AS?

RAUTUVAARA INVEST AS is the largest registered owner, with 45.8%.

What is the revenue of TOPP HOLDING AS?

TOPP HOLDING AS had revenue of NOK 10.1m in 2024.

Who is the general manager of TOPP HOLDING AS?

Geir Hamnvik is registered as general manager of TOPP HOLDING AS.

Where is TOPP HOLDING AS based?

TOPP HOLDING AS has its business address in Furuflaten.

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.