BIZTRAC BETA
Rental and operating of own or leased real estate

SOLSTRANDVEGEN 19 AS

Org. no. 931319620 Limited company (AS) Tromsø Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK 5.5m
Equity NOK 8.4m
Incorporated 2023
Share capital NOK 838,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SOLSTRANDVEGEN 19 AS is registered as a limited company in Tromsø, Troms with organisation number 931319620. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 838,000, divided into 100 shares. The company's stated purpose is: “Å utvikle, eie og drifte fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK 5.5m in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK 5.5m
Equity
NOK 8.4m
Est. value
NOK 16.3m

Financial health · 2024

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

Who owns SOLSTRANDVEGEN 19 AS?

SOLSTRANDVEGEN 25-29 AS
SOLSTRANDVEGEN 19 AS
NOK 7.6m rev. · NOK 5.5m profit

SOLSTRANDVEGEN 19 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLSTRANDVEGEN 19 AS

Who owns SOLSTRANDVEGEN 19 AS?

SOLSTRANDVEGEN 25-29 AS is the largest registered owner, with 100.0%.

What is the revenue of SOLSTRANDVEGEN 19 AS?

SOLSTRANDVEGEN 19 AS had revenue of NOK 7.6m in 2024.

Who is the general manager of SOLSTRANDVEGEN 19 AS?

Tom Andre Hansen is registered as general manager of SOLSTRANDVEGEN 19 AS.

Where is SOLSTRANDVEGEN 19 AS based?

SOLSTRANDVEGEN 19 AS has its business address in Tromsø.

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.