BIZTRAC BETA
COMPANY REGISTER PROFILE
991415912 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

TROSET HOLDING AS

Org. no. 991415912 Limited company (AS) Trondheim Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 151,000
Operating profit NOK 90,000
Equity NOK 469,000
Incorporated 2007
Share capital NOK 101,000

TROSET HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 991415912. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 101,000, divided into 168196000 shares. The company's stated purpose is: “Investering i verdipapirer, eiendom og andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 151,000 in revenue and NOK 90,000 in operating profit.

Key figures · 2024

Revenue
NOK 151,000
Operating profit
NOK 90,000
Equity
NOK 469,000
Est. value
NOK 497,000

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.6%
Good
Equity as a share of total capital

Who owns TROSET HOLDING AS?

TROSET ANDERSEN AS
TROSET HOLDING AS
NOK 151,000 rev. · NOK 90,000 profit

TROSET HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TROSET HOLDING AS

Who owns TROSET HOLDING AS?

TROSET ANDERSEN AS is the largest registered owner, with 67.6%.

What is the revenue of TROSET HOLDING AS?

TROSET HOLDING AS had revenue of NOK 151,000 in 2024.

Who is the general manager of TROSET HOLDING AS?

Johnny Troset Andersen is registered as general manager of TROSET HOLDING AS.

Where is TROSET HOLDING AS based?

TROSET HOLDING AS has its business address in Trondheim.

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.