BIZTRAC BETA
Rental and operating of own or leased real estate

TRONRUD INVEST AS

Org. no. 923581324 Limited company (AS) Holmestrand Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 333,000
Operating profit NOK 2,000
Equity NOK 16.0m
Incorporated 2019
Share capital NOK 100,000

TRONRUD INVEST AS is registered as a limited company in Holmestrand, Vestfold with organisation number 923581324. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringsselskap, herunder å investere i aksjer, obligasjoner, fast eiendom, andeler i selskap etter selskapsloven og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 333,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2024

Revenue
NOK 333,000
Operating profit
NOK 2,000
Equity
NOK 16.0m
Est. value
NOK 11.2m

Financial health · 2024

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

Who owns TRONRUD INVEST AS?

BÅRD HELGE TRONRUD
TRONRUD INVEST AS
NOK 333,000 rev. · NOK 2,000 profit

TRONRUD INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TRONRUD INVEST AS own?

TRONRUD INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TRONRUD INVEST AS

Who owns TRONRUD INVEST AS?

BÅRD HELGE TRONRUD is the largest registered owner, with 50.0%.

What is the revenue of TRONRUD INVEST AS?

TRONRUD INVEST AS had revenue of NOK 333,000 in 2024.

Where is TRONRUD INVEST AS based?

TRONRUD INVEST AS has its business address in Sande I Vestfold.

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.