BIZTRAC BETA
Rental and operating of own or leased real estate

DALSAUNEVEGEN 5 AS

Org. no. 933673278 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 156,000
Operating profit NOK 96,000
Equity NOK 10,000
Incorporated 2024
Share capital NOK 30,000

DALSAUNEVEGEN 5 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 933673278. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie av fast eiendom og alt som direkte eller indirekte kan settes i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 156,000 in revenue and NOK 96,000 in operating profit.

Key figures · 2025

Revenue
NOK 156,000
Operating profit
NOK 96,000
Equity
NOK 10,000
Est. value
NOK 172,000

Financial health · 2024

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

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

Who owns DALSAUNEVEGEN 5 AS?

TROSET INVEST AS
DALSAUNEVEGEN 5 AS
NOK 156,000 rev. · NOK 96,000 profit

DALSAUNEVEGEN 5 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DALSAUNEVEGEN 5 AS

Who owns DALSAUNEVEGEN 5 AS?

TROSET INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of DALSAUNEVEGEN 5 AS?

DALSAUNEVEGEN 5 AS had revenue of NOK 156,000 in 2025.

Who is the general manager of DALSAUNEVEGEN 5 AS?

Per Arne Troset is registered as general manager of DALSAUNEVEGEN 5 AS.

Where is DALSAUNEVEGEN 5 AS based?

DALSAUNEVEGEN 5 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.