BIZTRAC BETA
Rental and operating of own or leased real estate

TRØNDERHOPP AKTIVITET AS

Org. no. 813297442 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 6,000
Equity NOK 3,000
Incorporated 2014
Share capital NOK 30,000

TRØNDERHOPP AKTIVITET AS is registered as a limited company in Trondheim, Trøndelag with organisation number 813297442. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av egen eller leid fast eiendom; møte- og serveringsvirksomhet”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 6,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 6,000
Equity
NOK 3,000
Est. value
NOK 17,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TRØNDERHOPP AKTIVITET AS?

TRØNDERHOPP
TRØNDERHOPP AKTIVITET AS
NOK 1.6m rev. · NOK 6,000 profit

TRØNDERHOPP AKTIVITET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRØNDERHOPP AKTIVITET AS

Who owns TRØNDERHOPP AKTIVITET AS?

TRØNDERHOPP is the largest registered owner, with 100.0%.

What is the revenue of TRØNDERHOPP AKTIVITET AS?

TRØNDERHOPP AKTIVITET AS had revenue of NOK 1.6m in 2024.

Who is the general manager of TRØNDERHOPP AKTIVITET AS?

Håvard Lie is registered as general manager of TRØNDERHOPP AKTIVITET AS.

Where is TRØNDERHOPP AKTIVITET AS based?

TRØNDERHOPP AKTIVITET 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.